OK, thank you both!
Am 16.06.2011 14:23, schrieb Michal Schmidt:
On 06/16/2011 01:41 PM, Tomasz Torcz wrote:
> dbmail is doing something confusing systemd.
Yes. Its startup sequence is wrong. It exits the original process
immediately after the first fork(), before it finishes initialization
and before the PID file is written.
Upstream should take a look at "SysV Daemons" in
http://0pointer.de/public/systemd-man/daemon.html
copy to upstream and changed subject
special thanks to Tomasz Torcz (below)
the simple-version with "ExecStart=/usr/sbin/dbmail-imapd -D" seems to work for
now
_______________
BTW:
i am using dbmail-2.2.17-11.fc15.rh.20110614.x86_64
because dbmail is here in production use and no
RCs wanted this time
i hope the fedora-packagers are wakeing up because it is frustrating
to write the startup-items for most used services and seeing
a total mix of systemd / sysvinit on any machine
MISSING:
* sshd
* mysqld
* postfix
* postgrey
* dbmail (all services)
Am 16.06.2011 14:10, schrieb Tomasz Torcz:
On Thu, Jun 16, 2011 at 01:49:32PM +0200, Reindl Harald wrote:
> below my "dbmail-imapd.service"
> i will send a copy to the dbmail-mailing-list
>
> some minutes ago dbmail-imapd <defunct> was in ps aux
> i am not sure what here happens, finally systedm shoots the service down
> PIDFile is given and /etc/init.d-scripts used this too
>
> [root@testserver:/lib/systemd/system]$ cat dbmail-imapd.service
> [Unit]
> Description=DBMail IMAP Server
> After=syslog.target mysqld.service local-fs.target network.target
>
> [Service]
> Type=forking
> PIDFile=/var/run/dbmail-imapd.pid
> ExecStart=/usr/sbin/dbmail-imapd
>
> [Install]
> WantedBy=multi-user.target
>
I succeeded with following:
[Service]
ExecStart=/usr/sbin/dbmail-imapd -D
So, without Type (default to simple), without explicit PIDFile and with
daemon running in foreground