Hi Jens, I have to beg your pardon for so long inactivity. But I'm currently checking outdated bugs so it is a lot of apologizing in general :-/
But about the matter, I wondered about the pidfile as the systemd unit doesn't talk about one. It seems that you can trigger that without any systemd/init at all. Just on a system run (yes two times): $ sudo ipmievd open daemon $ sudo ipmievd open daemon PID file '/var/run/ipmievd.pid0' already exists. Perhaps another instance is already running After that was clear I considered that the pidfile was misleading and that has to be part of the ipmi code itself. And I found it in src/ipmievd.c. Overall it seems that the logic is to call ipmievd_cleanup on a sighandler to clean up. But there seem to be paths (like the double call I have mentioned above) that go by, stop the daemon and leave the pidfile. That said that should be reported upstream. If you'd be so kind to do so and link the bug here to be tracked that would be great. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1618378 Title: ipmievd fails to start when a stray PID file exists To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipmitool/+bug/1618378/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
