Date: Sun, 22 Jan 2023 17:05:21 +0000
From: bugzilla-noreply@freebsd.org
To: bugs@FreeBSD.org
Subject: [Bug 269098] 'service {name} stop' works even without {name}_enable=YES in /etc/rc.conf
Message-ID: <bug-269098-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D269098 Bug ID: 269098 Summary: 'service {name} stop' works even without {name}_enable=3DYES in /etc/rc.conf Product: Base System Version: 13.1-STABLE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: misc Assignee: bugs@FreeBSD.org Reporter: yuri@freebsd.org Testcase: www/adguardhome. The log below shows how 'service {name} start' doesn't work without {name}_enable=3DYES in /etc/rc.conf, but 'service {name} stop' does work wi= thout {name}_enable=3DYES. [yuri@yv /usr/ports/www/adguardhome]$ sudo service adguardhome start Cannot 'start' adguardhome. Set adguardhome_enable to YES in /etc/rc.conf or use 'onestart' instead of 'start'. [yuri@yv /usr/ports/www/adguardhome]$ sudo service adguardhome onestart Starting adguardhome. [yuri@yv /usr/ports/www/adguardhome]$ ps ax | grep adg 88374 - Ss 0:00.00 daemon: adguardhome[88375] (daemon) 88375 - S 0:00.34 /usr/local/bin/adguardhome 88378 12 S+ 0:00.00 grep adg [yuri@yv /usr/ports/www/adguardhome]$ sudo service adguardhome stop Stopping adguardhome. Waiting for PIDS: 88375. [yuri@yv /usr/ports/www/adguardhome]$ ps ax | grep adg 88389 12 S+ 0:00.00 grep adg $ uname -a FreeBSD xx.xx.xx 13.1-STABLE FreeBSD 13.1-STABLE #0 stable/13-n253229-dd7b7807c32a: Mon Dec 5 05:36:40 PST 2022=20=20=20=20 unknown@nohost.com:/usr/obj/usr/freebsd-src/amd64.amd64/sys/GENERIC amd64 --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-269098-227>