Date: Wed, 27 Jun 2007 15:08:50 +1000 From: Norberto Meijome <freebsd@meijome.net> To: Sereno Ternullo <serenoternullo@virgilio.it> Cc: Eric Crist <mnslinky@gmail.com>, tundra@tundraware.com, Cyrus <skeletonman.bn@gmail.com>, freebsd-questions <freebsd-questions@freebsd.org> Subject: Re: KDM at boot Message-ID: <20070627150850.5a70e8d4@localhost> In-Reply-To: <46817AA9.3020701@virgilio.it> References: <b898119e0706251739w351b29b4r416148f64615128b@mail.gmail.com> <0D7B3EA1-FE81-4429-AA12-47D5A21BD385@gmail.com> <4680656D.7050501@tundraware.com> <46817AA9.3020701@virgilio.it>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 26 Jun 2007 22:44:25 +0200
Sereno Ternullo <serenoternullo@virgilio.it> wrote:
> This is even easier to remember:
>
> # init q
>
> It's the same for 'kill -HUP 1'
well...not really.
"init q" is specific to init.
kill -HUP {pid}
is the standard unix way to tell {pid} to reload its configuration file. Most apps handle the HUP signal specifically.
_________________________
{Beto|Norberto|Numard} Meijome
"He has Van Gogh's ear for music."
Billy Wilder
I speak for myself, not my employer. Contents may be hot. Slippery when wet. Reading disclaimers makes you go blind. Writing them is worse. You have been Warned.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070627150850.5a70e8d4>