On 2023-06-02 07:47, Paul Neuwirth via openSUSE Users wrote:
ROn Thursday 2023-06-01 21:56, Carlos E. R. wrote:
...
running with -vv I get following line: ipmievd: using pidfile /run/ipmievd.pid0 no matter how much I increase verbosity, nothing is displayed, why the pidfile is named that way, although pidfile is set in the arguments explicitely: ipmievd -vv sel daemon pidfile=/run/ipmievd.pid
manual says pidfile=<filename> Save process ID to this file when in daemon mode. Defaults to /run/ipmievd.pidN (where N is the ipmi device number -- defaults to 0).
so the argument is not used at all. I can set it to whatever, file keeps to be /run/ipmievd.pid0
appears to be a bug in ipmitool ?
The manual says that it will use /run/ipmievd.pid0, it is doing what it says. It wants a number.
I don't see it
pidfile=<filename> Save process ID to this file when in daemon mode. Defaults to /run/ipmievd.pidN (where N is the ipmi device number -- defaults to 0).
that's all it says, not mentioning it requires a number (or N) in argument. also no change in providing an argument like this:
"N is the number". So it will use a number. I don't know how to specify a different file in the command line, maybe that's a bug. It will use "/run/ipmievd.pid0", so you just have to tell systemd about it. The systemd service file is: [Unit] Description=Ipmievd Daemon After=syslog.target After=ipmi.service [Service] EnvironmentFile=-/etc/ipmievd ExecStart=/usr/sbin/ipmievd $IPMIEVD_OPTIONS Type=forking PIDFile=/run/ipmievd.pid [Install] WantedBy=multi-user.target So you have to run in a terminal as root (create an override): # systemctl edit ipmievd.service you will get a commented out copy of the service file for edit in "vi" (you can cheange that). So you write: [Service] PIDFile=/run/ipmievd.pid0 and save it, then try to start the service. If this works, add that information to the bug. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)