From owner-freebsd-questions@FreeBSD.ORG Wed Jun 19 16:14:26 2013 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 2FEC0A7A for ; Wed, 19 Jun 2013 16:14:26 +0000 (UTC) (envelope-from talayeh.asadi@gmail.com) Received: from mail-ie0-x22b.google.com (mail-ie0-x22b.google.com [IPv6:2607:f8b0:4001:c03::22b]) by mx1.freebsd.org (Postfix) with ESMTP id 038C21CB3 for ; Wed, 19 Jun 2013 16:14:25 +0000 (UTC) Received: by mail-ie0-f171.google.com with SMTP id qd12so13996889ieb.30 for ; Wed, 19 Jun 2013 09:14:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; bh=Q+TdfkifQGN3FRqNzhl924kBmT+MV6c2fmspuBdhBFc=; b=RU7vr9tsg2xmUv0A1NHaibi04liciqK5WOmGwZXk4hq1NApElQfv8KFMsxAxxYFRvf s1lTOLUZMBf2WPEX7vj9123nRysNlMLG533uJXNk+vdACTfdhkhtuhmpe1y3d70qoBo1 Vgs51GfwWFpSl+bbA0cSxbtk5ldAuL4o8rNaVTESvRPn/Ufw7nPIT6W7++mrhGuPZgqa GSm8a4XS8PW4bAMTHjhlGhe1Ti1/MQXcKou96aw7gfokPSviNnhaoAeTumQpFz8hftUx IQ+x3au9Z7wqWyfLKNux/PXA8LPiLjHcKAiiHosI7zbG9XkX8iTGCSgQinSsab8FlzYi TMDA== X-Received: by 10.50.44.8 with SMTP id a8mr1712969igm.88.1371658465613; Wed, 19 Jun 2013 09:14:25 -0700 (PDT) MIME-Version: 1.0 Sender: talayeh.asadi@gmail.com Received: by 10.42.153.10 with HTTP; Wed, 19 Jun 2013 09:14:05 -0700 (PDT) In-Reply-To: <13CA24D6AB415D428143D44749F57D7201F971CF@ltcfiswmsgmb21> References: <20130619145439.GA48188@dan.emsphone.com> <13CA24D6AB415D428143D44749F57D7201F971CF@ltcfiswmsgmb21> From: takCoder Date: Wed, 19 Jun 2013 20:44:05 +0430 X-Google-Sender-Auth: jBQ6_Hyjc665CUmQAvrX7UIBqaM Message-ID: Subject: Re: apply /etc/ttys changes on system To: "Teske, Devin" Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: Dan Nelson , "freebsd-questions@freebsd.org" X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: tak.official@gmail.com List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Jun 2013 16:14:26 -0000 Thank you all for your replys. :) > 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. > You are right, it is in the man page. I just wanted to preserve my machine from facing possible side-effects this command may cause, which i may not be aware of, if possible.. If one tty's tc has been changed and i run *kill -HUP 1* command, any current session on that tty will be forcibly closed; but not for those with same tty configs as before. At least, i may loose things, according to the loss of open sessions(though not having faced any problems during tests till now). i know i am responsible for the time of running this command, but do all child PIDs exit normally? I have heard of unwanted reactions on other OS es because of this command, but not for FreeBSD (at least till now).. > Or "init q" As i heard, this command is just the same as "kill -HUP 1". Does "init q" have any difference with the other one, in any aspects?? >FWIW, I've used "kill -HUP 1" on FreeBSD for reloading /etc/ttys >since roughly 1997. No repercussions. Ever. Not once. >It wasn't until sometime in the early 2000s that I found init(8) >mentioning you could do "init q" instead, so since then I've done that. That's the experience! good to hear about that.. Anyhow, i think i will try "init q" from now on. At least seems more handy :)