Re: [systemd-devel] At wits end... need to execute a script prior to anything getting killed/changed on reboot/shutdown

2019-01-16 Thread Reindl Harald
Am 17.01.19 um 06:04 schrieb Jonathon Kowalski: > On Thu, Jan 17, 2019 at 4:49 AM Christopher Cox wrote: >> Adding some extra systemd clarification. Saying do this After or Before >> other >> service doesn't mean the start/stop completes before moving on. It may >> execute >> asynchronously

Re: [systemd-devel] At wits end... need to execute a script prior to anything getting killed/changed on reboot/shutdown

2019-01-16 Thread Jonathon Kowalski
On Thu, Jan 17, 2019 at 4:49 AM Christopher Cox wrote: > > On 01/16/2019 10:44 PM, Christopher Cox wrote: > > On 01/16/2019 12:51 PM, Filipe Brandenburger wrote: > >> If you want to run it early in the shutdown process, then keep > >> DefaultDependencies=yes, in which case it will run before the

Re: [systemd-devel] At wits end... need to execute a script prior to anything getting killed/changed on reboot/shutdown

2019-01-16 Thread Christopher Cox
On 01/16/2019 10:44 PM, Christopher Cox wrote: On 01/16/2019 12:51 PM, Filipe Brandenburger wrote: If you want to run it early in the shutdown process, then keep DefaultDependencies=yes, in which case it will run before the base dependencies start to get stopped. If you need some other

Re: [systemd-devel] At wits end... need to execute a script prior to anything getting killed/changed on reboot/shutdown

2019-01-16 Thread Christopher Cox
On 01/16/2019 12:51 PM, Filipe Brandenburger wrote: If you want to run it early in the shutdown process, then keep DefaultDependencies=yes, in which case it will run before the base dependencies start to get stopped. If you need some other resources to be up, for instance network, then add

Re: [systemd-devel] Bugfix release(s)

2019-01-16 Thread Amish
On 16/01/19 11:52 pm, Lennart Poettering wrote: On Mi, 16.01.19 09:46, Colin Guthrie (gm...@colin.guthr.ie) wrote: Jérémy ROSEN wrote on 16/01/2019 08:24: yes... adding a "this is the start of the freeze" tag sounds like a low hanging fruit... it's almost no work for the core team to do, and

Re: [systemd-devel] Bugfix release(s)

2019-01-16 Thread Ryan Gonzalez
All that sounds great! I'll get to work ASAP. On Wed, Jan 16, 2019 at 12:46 PM Lennart Poettering wrote: > On Mi, 16.01.19 12:30, Ryan Gonzalez (rym...@gmail.com) wrote: > > > I'd love to do this! > > That'd be excellent! Thank you! > > > To be clear, it'd basically automatically send out a

Re: [systemd-devel] systemd-nspawn: access to disk devices does not work on centos 7/systemd 219

2019-01-16 Thread Mailing List SVR
Il 16/01/19 19:24, Lennart Poettering ha scritto: On Mi, 16.01.19 09:20, Mailing List SVR (li...@svrinformatica.it) wrote: Well, this command will make the sd devices readable inside the container on centos 7 too echo 'b 8:* rw' >

Re: [systemd-devel] At wits end... need to execute a script prior to anything getting killed/changed on reboot/shutdown

2019-01-16 Thread Filipe Brandenburger
If you want to run it early in the shutdown process, then keep DefaultDependencies=yes, in which case it will run before the base dependencies start to get stopped. If you need some other resources to be up, for instance network, then add After=network.target, etc. Remember that when shutting

[systemd-devel] At wits end... need to execute a script prior to anything getting killed/changed on reboot/shutdown

2019-01-16 Thread Christopher Cox
I need to be able to execute a script before anything gets shutdown. That is, when somebody does a "reboot", "shutdown" or "poweroff", I need this script to run first, and for it to finish before everything gets whacked. I know the following isn't "right"... I've tried so many different

Re: [systemd-devel] Bugfix release(s)

2019-01-16 Thread Lennart Poettering
On Mi, 16.01.19 12:30, Ryan Gonzalez (rym...@gmail.com) wrote: > I'd love to do this! That'd be excellent! Thank you! > To be clear, it'd basically automatically send out a message on new > "freeze" tags and release? I think it could be as simple as just sending out a mail to the mailing list

Re: [systemd-devel] Bugfix release(s)

2019-01-16 Thread Ryan Gonzalez
I'd love to do this! To be clear, it'd basically automatically send out a message on new "freeze" tags and release? -- Ryan (ライアン) Yoko Shimomura, ryo (supercell/EGOIST), Hiroyuki Sawano >> everyone else https://refi64.com/ On Wed, Jan 16, 2019, 12:22 PM Lennart Poettering On Mi, 16.01.19

Re: [systemd-devel] RFC: idea for a pstore systemd service

2019-01-16 Thread Lennart Poettering
On Di, 15.01.19 23:39, Jóhann B. Guðmundsson (johan...@gmail.com) wrote: > > [Service] > ExecStart=/bin/bash -c '/usr/bin/mv -t /var/lib/pstore /sys/fs/pstore/*' > Restart=on-success While this would certainly work, I think I'd prefer a version in C and not depend on an installed shell for this.

Re: [systemd-devel] systemd-nspawn: access to disk devices does not work on centos 7/systemd 219

2019-01-16 Thread Lennart Poettering
On Mi, 16.01.19 09:20, Mailing List SVR (li...@svrinformatica.it) wrote: > Well, this command will make the sd devices readable inside the container on > centos 7 too > > echo 'b 8:* rw' > > /sys/fs/cgroup/devices/machine.slice/machine-bionic\\x2druntime.scope/devices.allow > > now I'll will

Re: [systemd-devel] Bugfix release(s)

2019-01-16 Thread Lennart Poettering
On Mi, 16.01.19 09:46, Colin Guthrie (gm...@colin.guthr.ie) wrote: > Jérémy ROSEN wrote on 16/01/2019 08:24: > > yes... adding a "this is the start of the freeze" tag sounds like a low > > hanging fruit... it's almost no work for the core team to do, and it > > would be a clear signal that the

Re: [systemd-devel] Bugfix release(s)

2019-01-16 Thread Lennart Poettering
On Mi, 16.01.19 01:06, Christian Hesse (l...@eworm.de) wrote: > Lennart Poettering on Tue, 2019/01/15 20:00: > > Note that we don't branch releases right now. Instead when we are > > getting closer to a release we simply don't merge PRs we don't > > consider appropriate for the release anymore

Re: [systemd-devel] Bugfix release(s)

2019-01-16 Thread František Šumšal
On 1/14/19 4:36 PM, Lennart Poettering wrote: > On Mo, 14.01.19 10:59, Jan Synacek (jsyna...@redhat.com) wrote: > > I'd love to see some more CI hookup with Arch and Debian for example > (right now there is zero) or even just a git preview package set or so > that interested people can test.

Re: [systemd-devel] Bugfix release(s)

2019-01-16 Thread Colin Guthrie
Jérémy ROSEN wrote on 16/01/2019 08:24: > yes... adding a "this is the start of the freeze" tag sounds like a low > hanging fruit... it's almost no work for the core team to do, and it > would be a clear signal that the freeze period is starting... And automated mails to the list when this happens

Re: [systemd-devel] Bugfix release(s)

2019-01-16 Thread Jérémy ROSEN
yes... adding a "this is the start of the freeze" tag sounds like a low hanging fruit... it's almost no work for the core team to do, and it would be a clear signal that the freeze period is starting... Le mer. 16 janv. 2019 à 01:14, Christian Hesse a écrit : > Lennart Poettering on Tue,

Re: [systemd-devel] systemd-nspawn: access to disk devices does not work on centos 7/systemd 219

2019-01-16 Thread Mailing List SVR
Well, this command will make the sd devices readable inside the container on centos 7 too echo 'b 8:* rw' > /sys/fs/cgroup/devices/machine.slice/machine-bionic\\x2druntime.scope/devices.allow now I'll will search how to pass to systemd-nspawn using a command line argument Il 16/01/19