Ticket #30 (closed enhancement: wontfix)

Opened 3 years ago

Last modified 2 years ago

Running several nutcpc having different hostname

Reported by: dboucard Owned by: eric
Priority: minor Milestone: NuFW2.4
Component: nufw Version:
Keywords: nutcpc hostname Cc:

Description

For the moment, nutcpc checks that only one nutcpc is running at a time for a given HOME directory.

I propose that condition to be extended to a given HOME directory and a given nuauth hostname.

I think it is legitime to run several nutcpc if they are connected to different nuauth servers and we should not have to run the second one with "-l" option (not clean to manage).

Several nuauth server can be needed if these servers do not have access to the same user directory database (for example, a local nuauth system-based and a global nuauth ldap-based).

Change History

Changed 3 years ago by eric

  • owner changed from regit to eric
  • status changed from new to assigned
  • milestone set to NuFW2.4

I don't want to get rid of -l because it is difficult to distinguish between

nutcpc -H localhost

and

nutcpc -H 127.0.0.1

But improvement could also be done by providing a clean web to kill a selected instance of nutcpc. Like it is implemented in screen software.

Changed 3 years ago by eric

Another solution could be to implement nuauth public key storage (like on ssh client) to be able to distinguish different nuauth by their key.

Changed 2 years ago by haypo

  • status changed from assigned to closed
  • resolution set to wontfix
Note: See TracTickets for help on using tickets.