Re: [systemd-devel] systemd hang on booting after mount

2011-01-18 Thread Lennart Poettering
On Tue, 18.01.11 14:05, Chanwoo Choi (cwcho...@gmail.com) wrote: General Setup -- [*] Control Group support -- [ ] Example debug cgoup subsystem [ ] Namespace cgroup subsystem [ ] Freezer cgroup subsystem [ ] Device controller

Re: [systemd-devel] lighttp unit - graceful reload of configfiles by sending signal to $MAINPID

2011-01-18 Thread Lennart Poettering
On Tue, 18.01.11 16:41, Alexander E. Patrakov (patra...@gmail.com) wrote: How is this implemented in detail? Sending SIGINT is async, so at the time you start the new instance you cannot be sure that the old instance has stopped listening? Indeed, there is a race here. That's why /bin/sleep

Re: [systemd-devel] Assertion failed in systemd v16

2011-01-18 Thread Alexander E. Patrakov
18.01.2011 04:14, Lennart Poettering пишет: On Mon, 10.01.11 15:11, Alexander E. Patrakov (patra...@gmail.com) wrote: [Unit] Description=Lighttpd Web Server After=network.target [Service] Type=forking EnvironmentFile=/etc/conf.d/lighttpd PIDFile=/var/run/lighttpd.pid

Re: [systemd-devel] lighttp unit - graceful reload of configfiles by sending signal to $MAINPID

2011-01-18 Thread Alexander E. Patrakov
18.01.2011 04:48, Lennart Poettering wrote: What systemd currently does is: If the reload fails it shutdowns the service and informs you about the failure. What systemd probably should do (and what is now in the TODO list) is: If the reload fails it should leave the service as

Re: [systemd-devel] Assertion failed in systemd v16

2011-01-18 Thread Marius Tolzmann
hi.. On 01/18/11 13:30, Alexander E. Patrakov wrote: As you noticed, this changes the PID, and systemd currently cannot handle this. We could however reload the PID file after a reload completed I guess. (/me adds this to the todo list) Well, there are cases (live update of nginx, see

Re: [systemd-devel] Assertion failed in systemd v16

2011-01-18 Thread Lennart Poettering
On Tue, 18.01.11 17:30, Alexander E. Patrakov (patra...@gmail.com) wrote: ExecStart=/usr/sbin/lighttpd -f /etc/lighttpd/lighttpd.conf ExecStop=/bin/kill -INT $MAINPID This is asynchronous. The stop operation is supposed to be synchronous however, should not return before it finished. This

Re: [systemd-devel] Assertion failed in systemd v16

2011-01-18 Thread Lennart Poettering
On Tue, 18.01.11 14:04, Marius Tolzmann (tolzm...@molgen.mpg.de) wrote: hi.. On 01/18/11 13:30, Alexander E. Patrakov wrote: As you noticed, this changes the PID, and systemd currently cannot handle this. We could however reload the PID file after a reload completed I guess. (/me

Re: [systemd-devel] lighttp unit - graceful reload of configfiles by sending signal to $MAINPID

2011-01-18 Thread Lennart Poettering
On Tue, 18.01.11 17:56, Alexander E. Patrakov (patra...@gmail.com) wrote: 18.01.2011 16:51, Lennart Poettering пишет: On Tue, 18.01.11 16:41, Alexander E. Patrakov (patra...@gmail.com) wrote: How is this implemented in detail? Sending SIGINT is async, so at the time you start the new

Re: [systemd-devel] lighttp unit - graceful reload of configfiles by sending signal to $MAINPID

2011-01-18 Thread Lennart Poettering
On Tue, 18.01.11 18:00, Alexander E. Patrakov (patra...@gmail.com) wrote: 18.01.2011 04:48, Lennart Poettering wrote: What systemd currently does is: If the reload fails it shutdowns the service and informs you about the failure. What systemd probably should do (and what is

Re: [systemd-devel] miredo unit files

2011-01-18 Thread Lennart Poettering
On Tue, 18.01.11 18:34, Alexander E. Patrakov (patra...@gmail.com) wrote: Hmm, I am not sure how miredo works. Is the client something where you have to run one instance per network iface? Or do you have a global instance for all? If the latter, then why doesn't it watch the network