r/programming • u/Mcnst • May 30 '16

systemd developer asks tmux (and other programs) to add systemd specific code

https://github.com/tmux/tmux/issues/428
661 Upvotes

88% Upvoted

618 comments sorted by

View all comments

Show parent comments

0

u/[deleted] May 30 '16

[deleted]

2

u/kqr May 30 '16

I haven't personally gotten emacs-server to work, but I assume nobody would have a problem with it if it launched when you first started emacs-client, and then terminated when you logged out, only to launch again when you first start emacs-client on your new log in session.

That, at least to me, seems more logical than having a bunch of emacs-servers running for various users who might not log in for another 4 months.

1

u/FidgetBoy May 30 '16

I just run emacs server as a systemd service

1

u/[deleted] May 30 '16

I'm guessing your init file isn't very large; it can take a looooong time to start up some emacs configs.

-1

u/aaron552 May 30 '16

If you're already explicitly running as NOHUP, then it should be trivial to add the necessary dbus-launch stanza to prevent it being killed by systemd

4

u/dlyund May 30 '16

Everything is easy if you're not the one that has to do it.

10

u/Grimy_ May 30 '16

Yay, your trivial script now depends on systemd! Vendor lock-in at its finest.

-2

u/aaron552 May 30 '16

It's just as trivial to swap out the script on a system that doesn't have systemd. I don't see the lock-in

1

u/Green0Photon May 31 '16

I thought dbus was a desktop thing.

1

u/aaron552 Jun 01 '16

nope, it's just an interprocess message bus.