On Wed, Dec 27, 2023 at 08:53:10AM +, RVP wrote:
> A way to check for a process-name different from the command-name seems
> to be documented in /etc/rc.subr. Does this patch work?
I think that works too, yes.
Thomas
On Fri, 15 Dec 2023, Thomas Klausner wrote:
I'm currently trying out grafana, and I noticed one weirdness after
starting it using the pkgsrc rc.d script.
# /etc/rc.d/grafana status
grafana is not running.
# cat /var/run/grafana.pid
21719# ps -auxwww | grep 21719
root 7846 0.0 0.0 1246
Thanks for the suggestions.
It turns out that starting 'grafana-server ...' ends up starting
'grafana server ...' which made the process name check fail - it
expected arg0 to be grafana-server, not grafana.
I've changed the script to start grafana as 'grafana server' instead
and it works now.
Th
Date:Fri, 15 Dec 2023 18:51:47 +0300
From:Valery Ushakov
Message-ID:
| Can you run the status command with sh -x?
Actually run it with -X instead (the rc stuff fiddles with fd's so
much it is possible it might steal some of the -x output otherwise).
sh -X
On Fri, Dec 15, 2023 at 15:17:57 +0100, Thomas Klausner wrote:
> So grafana saved its PID into /var/run/grafana.pid, which is what's
> configured in the rc.d script as pidfile, but the status command
> thinks it's not running, despite a grafana process with the
> corresponding PID running.
Can yo
Hi!
I'm currently trying out grafana, and I noticed one weirdness after
starting it using the pkgsrc rc.d script.
# /etc/rc.d/grafana status
grafana is not running.
# cat /var/run/grafana.pid
21719# ps -auxwww | grep 21719
root 7846 0.0 0.0 12468 2212 pts/4 O+3:14nachm.0:00.0