Am Mon, 21 Dec 2015 21:43:24 -0500 schrieb Mike Gilbert <flop...@gentoo.org>:
> On Mon, Dec 21, 2015 at 7:36 PM, Kai Krakow <hurikha...@gmail.com> > wrote: > > Am Tue, 8 Dec 2015 01:36:01 +0200 > > schrieb Mantas Mikulėnas <graw...@gmail.com>: > > > >> What uid does "oracle" have – is it within the system account range > >> (usually 1–999) or user account (1000–)? I wonder if it's the > >> latter, which would mean systemd-logind would clean up various > >> things like IPC on logout... (see logind.conf) > > > > Is this hard-coded in systemd (uid 0..999 and 1000+) or is it read > > from login.defs? > > > > Because I cannot find anything related to it in logind.conf which > > leads me to the assumption your reference was about RemoveIPC and > > friends only... > > I rather doubt the numeric value of the oracle UID has anything to do > with the problem you are having. > > With systemd, you really cannot start daemons from an interactive > shell. Rather, you need to define a service unit, and call "systemctl > start" to start long-running daemons. I think we are talking different here. My question is a spin-off of the OP. Mantas actually made the connection between user and system uid range to systemd behavior. I just wondered, if this is: [_] an assumption based on guessing (don't put a cross here) [_] hard-coded which personally I'd find surprising [_] configurable and I didn't find the knob But putting one and one together, your answer means (to the OP): Don't start daemons directly from a shell and exit. Systemd will blast them away. Defined behavior. Yes, it won't work. -- Regards, Kai Replies to list-only preferred. _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
