From: "T.V Raman" via "Emacs development discussions." <emacs-devel@gnu.org>
To: mlang@blind.guru
Cc: emacs-devel@gnu.org, raman@google.com
Subject: Re: Emacs Daemon --- Dies silently
Date: Thu, 14 Jan 2021 13:44:26 -0800 [thread overview]
Message-ID: <24576.47930.444167.57563@retriever.mtv.corp.google.com> (raw)
In-Reply-To: <87wnwfb6dc.fsf@blind.guru>
I think this was luser error on my part -- I've always run emacs or
emacs --daemon under screen.
Since I was using the daemon, a few days ago I eliminated screen from
my setup -- and then forgot all about it -- I believe screen is what
was keeping the emacs alive which makes sense. I had somehow
(wrongly?) assumed that if I ran emacs --daemon, it would survive
across sessions with respect to ssh --- I was clearly wrong.
Mario Lang writes:
> "T.V Raman" <raman@google.com> writes:
>
> [...]
>
> > On the other hand emacs --daemon appears to be quitting when I logout
> > from the remote machine.
>
> Shot in the dark, but might systemd have something to do with that?
> IOW, do you run emacs --daemon via a systemd user service?
> If so, see loginctl, in particular:
>
> enable-linger [USER...], disable-linger [USER...]
> Enable/disable user lingering for one or more users.
> If enabled for a specific user, a user manager is spawned
> for the user at boot and kept around after logouts. This allows users who
> are not logged in to run long-running services. Takes one or more
> user names or numeric UIDs as argument. If no argument is specified,
> enables/disables lingering for the user of the session of the caller.
>
> See also KillUserProcesses= setting in logind.conf(5).
>
> --
> CYa,
> ⡍⠁⠗⠊⠕
--
♉Id: kg:/m/0285kf1 🦮♉
--
♉Id: kg:/m/0285kf1 🦮♉
prev parent reply other threads:[~2021-01-14 21:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-13 21:13 Emacs Daemon --- Dies silently T.V Raman
2021-01-13 23:27 ` Daniel Brooks
2021-01-14 3:26 ` Eli Zaretskii
2021-01-14 15:48 ` T.V Raman via Emacs development discussions.
2021-01-14 16:45 ` Eli Zaretskii
2021-01-14 20:01 ` T.V Raman
2021-01-14 20:39 ` Mario Lang
2021-01-14 21:44 ` T.V Raman via Emacs development discussions. [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=24576.47930.444167.57563@retriever.mtv.corp.google.com \
--to=emacs-devel@gnu.org \
--cc=mlang@blind.guru \
--cc=raman@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).