On Thu, 23.01.14 10:51, Marwan Rabbâa (wagha...@gmail.com) wrote: > [Install] > WantedBy=gitlab.target > ***************** gitlab-unicorn.service ***************** > [Unit] > Description=GitLab Unicorn Server > > [Service] > User=git > WorkingDirectory=/var/www/gitlab > Environment=RAILS_ENV=production > SyslogIdentifier=gitlab-unicorn > PIDFile=/var/run/gitlab-unicorn.pid > > ExecStart=/var/www/gitlab/script/unicorn > ExecStop=/usr/bin/kill -QUIT $MAINPID
This sounds really wrong... SIGQUIT is a signal to ask a process to terminate and core dump. If the app is using this signal to terminate cleanly, then that would be really confused... Note that for most services ExecStop= is actually unnecessary to specify, since systemd sends SIGTERM to them anyway, which is the most common way how sservices are told to terminate anyway... > What is wrong with my conf ? Hmm, check syslog. Note that there's currently a race in the syslog handling between the journal and the clients, so that messages that are logged immediately before a service exits might nor properly be associated with that service. There's a kernel patch pending to allow us to fix that. In the meantime, check the full "journalctl" for those messages... Lennart -- Lennart Poettering, Red Hat _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
