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
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
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
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
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
ExecStartPre=/usr/sbin/lighttpd -t -f
I wrote:
Here is what happened when I tried to reload lighttpd while looking
with strace whan systemd is doing:
[ 3639.047649] systemd[1]: Assertion 's-control_command_id ==
SERVICE_EXEC_START' failed at src/service.c:2184, function
service_run_next_main(). Aborting.
[ 3639.052182]
On Mon, Jan 10, 2011 at 13:30, Alexander E. Patrakov patra...@gmail.com wrote:
[ 3639.047649] systemd[1]: Assertion 's-control_command_id ==
SERVICE_EXEC_START' failed at src/service.c:2184, function
service_run_next_main(). Aborting.
#ExecReload=/usr/sbin/lighttpd -t -f
