landscape-client should have a native Upstart job
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Landscape Client |
Invalid
|
Low
|
Unassigned |
Bug Description
I've attached a proposed script. Due to the way Upstart works, I don't think there's a need to manage the PID file. However, I'm a little less sure about whether the just-in-case cleaning of /var/lib/
Also: again, due to Upstart, it makes more sense to run landscape-client in the foreground rather than daemonize. It's simpler that way. The only downside is that it will emit "started landscape-client" as soon as it is executed. In some cases this is a problem. The started event might fire before the daemon has fully initialized or started listening. Since landscape-client does not listen, and as far as I know, has no reverse dependencies, this should be no problem.
Changed in landscape-client: | |
milestone: | none → backlog |
importance: | Undecided → Low |
Looks like landscape-config calls the old init script directly to restart:
"sh: /etc/init. d/landscape- client: not found
Couldn't restart the Landscape client.
This machine will be registered with the provided details when the client runs."