Re: [systemd-devel] Hear opinions about changing watchdog timeout value during service running

Hi, No general counter-arguments here, but I would like to strongly suggest that support for this has to be explicitly enabled in the services unit, preferably with required configuration of an upper bound. E.g. [Service] (...) WatchdogSec=2s WatchdogSecAllowChange=true

Re: [systemd-devel] restart vs. stop/start

Hello, Am Montag, 23. Mai 2016, 11:43:13 CEST schrieb Lennart Poettering: > On Sun, 22.05.16 16:18, Christian Boltz wrote: > > I can add my usecase as another reason ;-) > > > > I'm talking about AppArmor, where "stop" means unloading the > > profiles > > from the kernel. The result is that all

Re: [systemd-devel] restart vs. stop/start

Hello, Am Montag, 23. Mai 2016, 11:24:06 CEST schrieb Lennart Poettering: > On Fri, 20.05.16 21:50, Christian Boltz wrote: > > it looks like > > > > systemctl restart foo > > > > is internally mapped to a sequence of > > > > systemctl stop foo; systemctl start foo > > > >

Re: [systemd-devel] Running ldconfig at boot

On 05/23/2016 11:59 AM, Lennart Poettering wrote: On Mon, 23.05.16 11:34, Florian Weimer (fwei...@redhat.com) wrote: On 05/20/2016 04:10 PM, Lennart Poettering wrote: If such systems require specialized unit files, then you can put ldconfig.service there, instead of exposing all systemd

Re: [systemd-devel] Hear opinions about changing watchdog timeout value during service running

2016-05-24 오전 4:23에 David R. Piegdon 이(가) 쓴 글: Hi, No general counter-arguments here, but I would like to strongly suggest that support for this has to be explicitly enabled in the services unit, preferably with required configuration of an upper bound. E.g. [Service] (...) WatchdogSec=2s

Re: [systemd-devel] restart vs. stop/start

Am 23.05.2016 um 23:33 schrieb Michael Biebl: 2016-05-23 22:52 GMT+02:00 Christian Boltz : I'd argue that nobody will complain if "systemctl restart apparmor" does something sane (reloading the profiles) instead of making the system insecure by removing the

Re: [systemd-devel] launching an interactive user session

On 05/23/2016 06:07 AM, Lennart Poettering wrote: On Fri, 20.05.16 20:10, Mike Gulick (mike.gul...@mathworks.com) wrote: Hi systemd-devel, I'm on Debian Jessie running the default systemd-215. I have a daemon (running as root, controlled by systemd), whose job it is to launch on-demand VNC

Re: [systemd-devel] restart vs. stop/start

2016-05-23 22:52 GMT+02:00 Christian Boltz : > I'd argue that nobody will complain if "systemctl restart apparmor" does > something sane (reloading the profiles) instead of making the system > insecure by removing the confinement from all running processes ;-) So, you

Re: [systemd-devel] Fwd: Handling ExecStop failure

Am 23.05.2016 um 10:00 schrieb Ashish Sangwan: My second issue is, on failure of stopping/umounting, no failure message appears on console although I have used StandardError option sadly systemd don't print service outputs to console even something like "systemd-run -t

Re: [systemd-devel] Fwd: Handling ExecStop failure

On Mon, 23.05.16 13:30, Ashish Sangwan (ashishsangw...@gmail.com) wrote: > The first issue is, once the command mentioned in ExecStop failed due > to mountpoint busy, the user comes out of the mountpoint, making it > un-busy and again fires the systemctl stop command, however the status > of the

Re: [systemd-devel] Fwd: Handling ExecStop failure

On Mon, 23.05.16 10:32, Reindl Harald (h.rei...@thelounge.net) wrote: > > > Am 23.05.2016 um 10:00 schrieb Ashish Sangwan: > >My second issue is, on failure of stopping/umounting, no failure > >message appears on console although I have used StandardError option > > sadly systemd don't print

Re: [systemd-devel] Fwd: Handling ExecStop failure

On Mon, 23.05.16 10:56, Reindl Harald (h.rei...@thelounge.net) wrote: > in a shell it works fine Hmm, that's strange... > but i talk about cronjobs like "8,38 * * * * root > /usr/local/bin/spamfilter-fetch-samples" where the shell-script invokes > systemd-run which finally calls a php-script

Re: [systemd-devel] restart vs. stop/start

On Fri, 20.05.16 21:50, Christian Boltz (systemd-de...@cboltz.de) wrote: > Hello, > > it looks like > systemctl restart foo > is internally mapped to a sequence of > systemctl stop foo; systemctl start foo > > Unfortunately, this behaviour causes quite some trouble for me. > > I need a

Re: [systemd-devel] restart vs. stop/start

On Sat, 21.05.16 10:31, Andrei Borzenkov (arvidj...@gmail.com) wrote: > >> I need a way to know if "restart "or "stop" was used because the mapping > >> to stop / start gives my service a completely different behaviour than > >> expected on restart. > >> > >> Is there a way to find out if "stop"

Re: [systemd-devel] restart vs. stop/start

On Sun, 22.05.16 23:19, Christian Boltz (systemd-de...@cboltz.de) wrote: > Hello, > > Am Sonntag, 22. Mai 2016, 21:48:02 CEST schrieb Reindl Harald: > > Am 22.05.2016 um 21:03 schrieb Christian Boltz: > > > I'm already using ExecReload= to reload the profiles (works fine), > > > and hope all

Re: [systemd-devel] Hear opinions about changing watchdog timeout value during service running

On Mon, 23.05.16 11:06, 김민경/주임연구원/SW Platform(연)AOT팀(minkyung88@lge.com) (minkyung88@lge.com) wrote: > Hello. > > Below is usecase from our SW-Engineer. > > What do you think so? OK, makes sense. As mentioned, I#d suggest implementing this via a new parameter to sd_notify() that

Re: [systemd-devel] Shutdown a specific service in systemd shutdown

On Sun, 22.05.16 15:24, Andrei Borzenkov (arvidj...@gmail.com) wrote: > 19.05.2016 11:57, Martin Pitt пишет: > > Hello Bao, > > > > Bao Nguyen [2016-05-19 15:52 +0700]: > >> When the system is shutdown, systemd will terminate all services in > >> parallel manner, could you let me know if there

Re: [systemd-devel] UEFI menu entries wiped from BIOS after power off at dm-crypt boot prompt

On Sat, 21.05.16 21:43, Jamie Kitson (ja...@kitten-x.com) wrote: > Hi, > > if I power off my computer at the dm-crypt boot password prompt my UEFI > menu entries get wiped from the BIOS and reset to the single default > Windows option. > > This is with an Asus UX32VD laptop, Grub UEFI and

Re: [systemd-devel] Fwd: Handling ExecStop failure

Am 23.05.2016 um 10:50 schrieb Lennart Poettering: On Mon, 23.05.16 10:32, Reindl Harald (h.rei...@thelounge.net) wrote: even something like "systemd-run -t --service-type=oneshot --quiet" behaves differently and don't work if you call it via crond to get the typical behavior of cronjobs

[systemd-devel] Fwd: Handling ExecStop failure

We have a user space file system implementation. Lets say the binary name is user_fs Execution/Mounting is done by using "systemctl start user_fs.service" and stop/umounting is done by using "systemctl stop user_fs.service" The service file looks like following: [Service] KillMode=none

Re: [systemd-devel] [ANNOUNCE] systemd v230

On Mon, May 23, 2016 at 01:33:57AM -0400, Dave Reisner wrote: > On Sat, May 21, 2016 at 10:51:13PM +, Zbigniew Jędrzejewski-Szmek wrote: > > Hi, > > > > systemd v230 has been tagged. Enjoy! > > > > CHANGES WITH 230: > > Hi, > > One important change missing from this list is 7163e1ca1108d7

Re: [systemd-devel] restart vs. stop/start

On Mon, 23.05.16 13:11, Andrei Borzenkov (arvidj...@gmail.com) wrote: > On Mon, May 23, 2016 at 12:25 PM, Lennart Poettering > wrote: > > On Sat, 21.05.16 10:31, Andrei Borzenkov (arvidj...@gmail.com) wrote: > > > >> >> I need a way to know if "restart "or "stop" was used

Re: [systemd-devel] Running ldconfig at boot

On Mon, 23.05.16 12:12, Reindl Harald (h.rei...@thelounge.net) wrote: > Am 23.05.2016 um 11:59 schrieb Lennart Poettering: > >On Mon, 23.05.16 11:34, Florian Weimer (fwei...@redhat.com) wrote: > >>I think the trigger is just implemented incorrectly. It should keep track > >>of UUIDs in files

Re: [systemd-devel] Running ldconfig at boot

On Mon, 23.05.16 11:34, Florian Weimer (fwei...@redhat.com) wrote: > On 05/20/2016 04:10 PM, Lennart Poettering wrote: > > >>If such systems require specialized unit files, then you can put > >>ldconfig.service there, instead of exposing all systemd users to the > >>service. > > > >No they

Re: [systemd-devel] Running ldconfig at boot

Am 23.05.2016 um 11:59 schrieb Lennart Poettering: On Mon, 23.05.16 11:34, Florian Weimer (fwei...@redhat.com) wrote: I think the trigger is just implemented incorrectly. It should keep track of UUIDs in files (such as /usr/.change-uuid), rather than looking at mtimes. Then you can just

[systemd-devel] DBus's PropertiesChanged signal is not triggered when an Unit stop successfully

Hello, I'm trying to make a small Python script which send an email when a *Type=oneshot *service ends (either in success or in failure). To do that, I'm using the dbus binding for Python, and connecting to the *PropertiesChanged* signal on the unit I'm monitoring. It works great when the

Re: [systemd-devel] restart vs. stop/start

On Mon, May 23, 2016 at 12:25 PM, Lennart Poettering wrote: > On Sat, 21.05.16 10:31, Andrei Borzenkov (arvidj...@gmail.com) wrote: > >> >> I need a way to know if "restart "or "stop" was used because the mapping >> >> to stop / start gives my service a completely

Re: [systemd-devel] Fwd: Handling ExecStop failure

On Mon, May 23, 2016 at 2:13 PM, Lennart Poettering wrote: > On Mon, 23.05.16 13:30, Ashish Sangwan (ashishsangw...@gmail.com) wrote: > >> The first issue is, once the command mentioned in ExecStop failed due >> to mountpoint busy, the user comes out of the mountpoint,

Re: [systemd-devel] Fwd: Handling ExecStop failure

On Mon, 23.05.16 18:16, Ashish Sangwan (ashishsangw...@gmail.com) wrote: > On Mon, May 23, 2016 at 2:13 PM, Lennart Poettering > wrote: > > On Mon, 23.05.16 13:30, Ashish Sangwan (ashishsangw...@gmail.com) wrote: > > > >> The first issue is, once the command mentioned in