On Mon, Aug 13, 2012 at 5:44 AM, Jan Safranek <jsafr...@redhat.com> wrote:
> Hi,
>
> instead of adding systemd code to ipmitool, I tried to find out what is
> really wrong with impievd so systemd cannot start it. It's quite
> difficult to debug systemd and a daemon together, but finally I got results.
>
> It turns out that the ipmievd does not fork() at all if it is started
> under PID=1. That was the last thing I would expect :), that's why it
> took so much time, I was looking for bugs elsewhere.
>
> Attached you can find another patch, now it's very simple and without
> any copyright notices.
>
> Is there any other init system, which starts service with parent PID=1?
> I.e. does the patch break anything?
I would think that this unbreaks more init systems than breaks
them. Assuming that it needs to be daemonized and then providing a
flag to not daemonize is typical behavior for Unix apps. You can
provide logic to detect whether or not it was started on a terminal
(isatty(fileno(stdout))?), but in general it's best to keep things
simple and not be too clever like that IMO.
Thanks,
-Garrett
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Ipmitool-devel mailing list
Ipmitool-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ipmitool-devel
