On Sun, Mar 10, 2019 at 8:07 PM Robert Dinse <[email protected]> wrote:
> > I have guacd installed, built with the --with-systemd flag and it > does > not install a systemd file but an initd file which systemd recognizes and > says it installs however, while systemctl start guacd works fine and > systemctl enable guacd indicates it did the right thing, it does not start > upon boot, I have to manually start it. Because some of the things it uses > are on NFS partitions, I suspect it's trying to start before NFS is up and > failing. > > A couple of notes: - The "--with-systemd" flag is not valid. The flag is "--with-systemd-dir=<directory>", where directory is the location where you'd like the systemd files installed. Can you please verify if that's the flag you're using, and if you're specifying a directory, like /etc/systemd/system or /usr/lib/systemd/system? - Have you tried removing the initd file, reloading systemd (systemctl daemon-reload) and seeing if the systemd unit then references the unit file (assuming it's actually being installed)? - If you have guacd running in a situation where NFS is required for guacd to start you're going to have to make some modifications to either the initd script or the systemd script. It sounds like, in this case, that the issue is not with either the guacd initd or systemd files, but with a customized environment you have. That's fine - we certainly don't expect every environment to follow the ones we're used to; however, you may have to do a little tweaking to the scripts to make them wait for NFS to be up before starting guacd, if guacd is on a NFS share. I would suspect even if you get the systemd script to install that you'll still have the same issue, because the standard systemd unit file we provide does not require NFS to be up. Fortunately, those changes should be relatively trivial to either the initd script or the systemd unit file. -Nick
