Bug 26636

Summary: If /etc/ttys goes empty, init(8) never rereads it
Product: Base System Reporter: matt <matt>
Component: miscAssignee: freebsd-bugs (Nobody) <bugs>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: 4.2-RELEASE   
Hardware: Any   
OS: Any   
Attachments:
Description Flags
file.diff none

Description matt 2001-04-17 08:10:02 UTC 
If you empty out /etc/ttys, HUP init, and then put something back in /etc/ttys, init will never spawn anything ever again.

Fix: This patch was not made with an understanding of init, so it may well introduce problems.  It merely points the direction to the solution of this problem.
Comment 1 Johan Karlsson freebsd_committer freebsd_triage 2002-06-20 01:20:25 UTC 
State Changed
From-To: open->closed

This is the expected behaviour. 

It is clearly stated in the manpage that one 
have to send a HUP signal to init for it to reread 
the ttys file.
Comment 2 Johan Karlsson freebsd_committer freebsd_triage 2002-07-21 16:51:33 UTC 
On Sat, Jul 13, 2002 at 17:39 (-0700) +0000, Matthew Braithwaite wrote:
> > 	It is clearly stated in the manpage that one
> > 	have to send a HUP signal to init for it to reread
> > 	the ttys file.
> 
> Yes, I know that.  But after /etc/ttys has gone empty, a SIGHUP won't
> make init reread it.  


Ok, so does

1: clear /etc/ttys
2: SIGHUP init
2.5: make sure nothing is started by init
3: restore /etc/ttys
4: SIGHUP init
4.5: make sure the stuff in ttys is started by init

not work as excpected for you?

If not, what happens?

It seems to work for me. Maybe you are doing something different from
me.

/Johan K
-- 
Johan Karlsson		mailto:johan@FreeBSD.org