Date: Wed, 28 Nov 2007 14:37:13 -0500 From: John Baldwin <jhb@freebsd.org> To: freebsd-stable@freebsd.org Cc: Andrei Kolu <antik@bsd.ee> Subject: Re: questionable feature- rcvar woes Message-ID: <200711281437.13827.jhb@freebsd.org> In-Reply-To: <200711282116.53008.antik@bsd.ee> References: <200711282116.53008.antik@bsd.ee>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday 28 November 2007 02:16:51 pm Andrei Kolu wrote: > Something is wrong with rcvar or I am just blatant. > > For example: > > 1) Enable powerd in rc.conf > # echo 'enable_powerd="YES"' >> /etc/rc.conf > 2) Launch powerd > # /etc/rc.d/powerd start > Starting powerd. > 3) And stopping it. > # /etc/rc.d/powerd stop > Stopping powerd. > > Everything looks fine, but when I disable powerd in rc.conf then problem > arise. > > 1) Disable powerd in rc.conf- comment it out. > # enable_powerd="YES" > 2) Stop powerd > # /etc/rc.d/powerd stop > ...silence- nothing in logs either. > > What? Not even a warning message and powerd is actually running- why I have to > reboot to disable it? I know that I can stop it by enabling it in rc.conf but > what the point? Same problem when I want to start some service without > appropriate line in rc.conf. I'd prefer to see somekind of warning about > misconfigured rc.conf or at least information about what's going on in > reality. Use forcestart or forcestop to manage services that are not enabled in rc.conf. This is normal. If you got a warning, then on shutdown every rc.d script that is disabled would whine. Simiarly on boot since all rc.d scripts are started on boot. -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200711281437.13827.jhb>