Re: -HUP 1 command

From: Christian Laursen (xi_at_borderworlds.dk)
Date: 01/15/04

  • Next message: Didier Wiroth: "ERROR: Unable to write data to disk idad1" 
    To: freebsd-questions@freebsd.org
Date: 15 Jan 2004 01:24:32 +0100

    Jez Han*** <jez.han***@munk.nu> writes:

    > On Tue, Jan 13, 2004 at 08:53:44PM -0500, fbsd_user wrote:
    > > After making changes to syslog.conf and newsyslog.conf
    > > what is the command to enable the changes.
    > >
    > > Is it Kill -HUP 1
    > Note that process with PID 1 is usually the init process - sending a HUP
    > signal to it will produce undesirable effects similar to restarting the
    > whole server. Have a go and see what happens if it's not a production
    > server :P

    I usually kill init with a SIGHUP after editing /etc/ttys and it has so
    far never caused me any trouble.

    Actually this is also explained in the init(8) manpage:

         Line status (on, off, secure, getty, or window information) may be
         changed in the ttys(5) file without a reboot by sending the signal SIGHUP
         to init with the command ``kill -HUP 1''. On receipt of this signal,
         init re-reads the ttys(5) file. 

    -- 
Best regards
    Christian Laursen
_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"
  • Next message: Didier Wiroth: "ERROR: Unable to write data to disk idad1"