Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 19 Jun 2013 15:16:51 +0000
From:      "Teske, Devin" <>
To:        Dan Nelson <>, takCoder <>
Cc:        "" <>
Subject:   RE: apply /etc/ttys changes on system
Message-ID:  <13CA24D6AB415D428143D44749F57D7201F971CF@ltcfiswmsgmb21>
In-Reply-To: <>
References:  <>, <>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help

> ________________________________________
> From: [owner-freebsd-questions@freebs=] on behalf of Dan Nelson []
> Sent: Wednesday, June 19, 2013 7:54 AM
> To: takCoder
> Cc:
> Subject: Re: apply /etc/ttys changes on system
> In the last episode (Jun 19), takCoder said:
> > Is there any way to apply /etc/ttys changes on system, except for
> > *restarting system* and *running kill -HUP 1* command ?
> >
> > Due some reasons, i need to change tc value of some of my ttys,
> > periodically. I'm looking for a safer way than *kill -HUP 1* command. S=
> > as this command is not a good one to be used often, any ideas are really
> > appreciated. I couldn't find any other one so far..
> Why is "kill -HUP 1" unsafe?  It's documented in init's 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.

Or "init q"

The information contained in this message is proprietary and/or confidentia=
l. If you are not the intended recipient, please: (i) delete the message an=
d all copies; (ii) do not disclose, distribute or use the message in any ma=
nner; and (iii) notify the sender immediately. In addition, please be aware=
 that any message addressed to our domain is subject to archiving and revie=
w by persons other than the intended recipient. Thank you.

Want to link to this message? Use this URL: <>