Hi Mark,

Mark Oteiza <mvoteiza@udel.edu> writes:

> Matthew Leach <matthew@mattleach.net> writes:
>> Currently, I start emacs --daemon upon login of my user and this can
>> delay the login process by a few seconds as Emacs initialises.  The idea
>> behind socket activation is that, systemd knows about the socket's
>> existence and won't unmount any file-systems where the socket resides
>> until the daemon has shut down, this is causing a race condition on
>> reboot for me.  Also, allows the start of emacs --daemon to be on-demand
>> and so there is less of a delay at login.
>
> Out of curiosity, how are you starting it? I just fork it off with
> `emacs --daemon &' and so don't have this problem.

Attached is my user's emacs.service file and my .kill-emacs.sh.  The sh
file is needed for an unrelated issue, namely that emacsclient exists
before the server is shut down and as far as systemd is concerned, once
ExecStop has completed the daemon should be shut down.  If it is not,
the default behaviour is to send it SIGKILL.

Thanks,
-- 
Matt