Service unbound status

Antibiotic

command from terminal "service unbound status"
return "unbound is not running"

pfSense 24.03
Any1 have the same mystic
???

Gertjan

I see the same thing.

You tried

service unbound rcvar

?

To understand what you are seeing :
Windows is not Linux. Linux is not FreeBSD, and surprisingly, pfSense is not FreeBSD.
I didn't even know the command "service"existed for FreeBSD (I use it all the time with my Debian 11.x as I still can't get my head around systemd).

Check out for yourself : open /usr/local/etc/rc.d/unbound
You'll find :

pidfile=$(/usr/local/sbin/unbound-checkconf -o pidfile ${unbound_config})

and that isn't the reality.
The pid file is here : /var/run/unbound.pid

and just above :

# read settings, set default values
: ${unbound_enable:="NO"}
: ${unbound_config:=/usr/local/etc/unbound/unbound.conf}

So, this unbound service file says : service unbound disabled.
And the place where the unbound config is located is also wrong.
It's here : /var/unbound/

pfSense uses (is based upon) the unbound FreeBSD package.
But pfSense controls most if not all processes with it's own GUI scripts/code, and most of what you can find in /usr/local/etc/rc.d/ or /etc/rc.d/ for that matter isn't used

[24.03-RELEASE][root@pfSense.bhf.tld]/root: ps ax | grep 'unbound'
41201  -  S        0:11.32 /usr/local/sbin/lighttpd_pfb -f /var/unbound/pfb_dnsbl_lighty.conf
86447  -  Ss      43:53.03 /usr/local/sbin/unbound -c /var/unbound/unbound.conf
84118  0  S+       0:00.00 grep unbound
[24.03-RELEASE][root@pfSense.bhf.tld]/root: cat /var/run/unbound.pid
86447

So, unbound runs just fine. The GUI told the truth.

Antibiotic

@Gertjan said in Service unbound status:

Windows is not Linux. Linux is not FreeBSD, and surprisingly, pfSense is not FreeBSD

OS is not a human))