systemd-initd confusion

[krichter722]

Packages for Ubuntu 17.04 ship both an initd and a systemd script where the systemd scripts are masked. If only systemd ought to be supported, the initd scripts should be dropped and if both ought to be supported, they should come in separate packages, e.g. coda-server-initd and coda-server-systemd.

Please note that it's still extremely hard to setup coda without an up-to-date documentation (http://www.coda.cs.cmu.edu/ doesn't mention systemd and refers to Windows 95 (I'm not voting to update documentation for it, but rather for Linux systems, but it's a good time reference)).

[jaharkes]

There is no good reason to mention systemd in any documentation yet because as far as I am concerned it is still pretty broken.

Systemd silently kills Coda servers that take too long to start, partly probably because Coda clients and servers are not 'properly' interacting with systemd to indicate their startup status.
Coda's daemons still do their own logging instead of handing that task off to systemd/journald.
When something goes wrong during startup or shutdown it is not gracefully handled, but sometimes leaves the system in a state with a mounted /coda but no userspace cache manager handling it, so systemd things Coda is shut down, but you cannot restart the client because the filesystem is already mounted, etc.

I'm not surprised things are broken when systemd and initd are mixed. Also if you build and package Coda on a system without systemd, it probably won't run right because it is not possible to find where the systemd unit files are supposed to go unless systemd is already available. That is distribution dependent and the information simply is unavailable on the pre-systemd releases of the distribution.

The only somewhat up-to-date documentation is the README.md in the Coda source tree.