Re: [systemd-devel] Question regarding systemd behavior during shutdown

2016-11-03 Thread Lennart Poettering
On Thu, 03.11.16 14:01, svk (shreyas...@gmail.com) wrote: > Hi, > I have a question regarding systemd behavior during shutdown. > > I am using systemd 219 on a Linux 4.1 kernel(custom distribution). When I > issue a "shutdown" command I observe something unusual :- 219 is really old, and the

Re: [systemd-devel] Emergency mode if non-critical /etc/fstab entries are missing

2016-11-03 Thread Lennart Poettering
On Mon, 26.09.16 07:02, Marc Haber (mh+systemd-de...@zugschlus.de) wrote: > On Mon, Sep 26, 2016 at 10:52:50AM +1300, Sergei Franco wrote: > > The emergency mode assumes console access, which requires physical access, > > which is quiet difficult if the machine is remote. > > It does also assume

[systemd-devel] Question regarding systemd behavior during shutdown

2016-11-03 Thread svk
Hi, I have a question regarding systemd behavior during shutdown. I am using systemd 219 on a Linux 4.1 kernel(custom distribution). When I issue a "shutdown" command I observe something unusual :- If a process managed by a systemd unit file with "Restart=always" exits prior to receiving a

Re: [systemd-devel] unsubsribe

2016-11-03 Thread Reindl Harald
Am 03.11.2016 um 21:36 schrieb Douglas R. Reno: On Thu, Nov 3, 2016 at 3:10 PM, Reindl Harald > wrote: Am 03.11.2016 um 20:27 schrieb sp113438: unsubsribe i can' remember that you asked me or other list memeber to

Re: [systemd-devel] unsubsribe

2016-11-03 Thread Douglas R. Reno
On Thu, Nov 3, 2016 at 3:10 PM, Reindl Harald wrote: > > > Am 03.11.2016 um 20:27 schrieb sp113438: > >> unsubsribe >> > > i can' remember that you asked me or other list memeber to subscribe you > so why should we even be able to unsubscribe you? guess what the list >

Re: [systemd-devel] Single Start-job remains listed after startup in state waiting ...

2016-11-03 Thread Lennart Poettering
On Fri, 28.10.16 14:55, Hoyer, Marko (ADITG/SW2) (mho...@de.adit-jv.com) wrote: > Hello, > > we are observing a weird behavior with systemd 211. > > The issue: > > -After the startup is finished (multi-user.target is > -reached), one single job (typ: start, unit: service) > -

[systemd-devel] unsubsribe

2016-11-03 Thread sp113438
unsubsribe ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] automount unit that never fails?

2016-11-03 Thread Lennart Poettering
On Sat, 29.10.16 14:20, Bjørn Forsman (bjorn.fors...@gmail.com) wrote: > On 1 October 2016 at 17:14, Bjørn Forsman wrote: > > On 20 September 2016 at 09:08, Bjørn Forsman > > wrote: > >> I have a question/issue with the behaviour of (auto)mount

Re: [systemd-devel] kexec -p option does not cause a reboot on panic

2016-11-03 Thread Lennart Poettering
On Sat, 29.10.16 00:16, Dey, Megha (megha@intel.com) wrote: > Hi, > > I was testing kexec on systemd (Ubuntu 16.04). Here are the steps I follow: systemd is not involved with crash dumping on kernel crashes. Please contact your distro maintainers or the crash dumping maintainers for help,

Re: [systemd-devel] systemd-nspawn leaves leftovers in /tmp

2016-11-03 Thread Lennart Poettering
On Thu, 03.11.16 11:34, Bill Lipa (d...@masterleep.com) wrote: > Hello, > > I am using systemd-nspawn to run a short lived process in a container. > This is a fairly frequent operation (once every few seconds). Each > time systemd-nspawn runs, it leaves a temporary empty directory like >

Re: [systemd-devel] PAM session hooks for independent session

2016-11-03 Thread Lennart Poettering
On Sat, 29.10.16 18:37, Antoine Martin (anto...@nagafix.co.uk) wrote: > The pam_systemd is much more difficult to figure out, since I am not > aware of any other packages does this at present - maybe there are? > * should we ship a /etc/pam/d/xpra file like this one: > sessionrequired

[systemd-devel] systemd-nspawn leaves leftovers in /tmp

2016-11-03 Thread Bill Lipa
Hello, I am using systemd-nspawn to run a short lived process in a container. This is a fairly frequent operation (once every few seconds). Each time systemd-nspawn runs, it leaves a temporary empty directory like /tmp/nspawn-root-CPeQjR. These directories don't seem to get cleaned up. I'm