Subject: Re: Another changer, another changer problem
To: NetBSD-current Discussion List <firstname.lastname@example.org>
From: Greg A. Woods <email@example.com>
Date: 10/18/1998 20:42:16
[ On Sun, October 18, 1998 at 02:05:00 (-0700), John Nemeth wrote: ]
> Subject: Re: Another changer, another changer problem
> I thought "sac" was that incredibly excessively complex (which is
> the AT&T style after all) replacement for getty in SVR4? At least
> that is where all my references point. Is there something else?
SAC simply manages "port monitors". The most commonly used port monitor
is ttymon, which is the replacement for getty.
Nothing prevents SAC from being used to control any "Service Access
Facility", be that inetd (aka listen in SysVr4-speak), or individual
TCP/IP port monitors, or anything else that provides a service.
In theory SysVr4 ports should never have come with inetd, but of course
in practice the vendors were swayed by those who wanted a more BSD-like
system, regardless of the fact that the SAC subsystems, including
listen, are generally a more mature design and with a reliable and
simple table-driven parent daemon watching over the flock it's a much
more robust design too.
Greg A. Woods
+1 416 218-0098 VE3TCP <firstname.lastname@example.org> <robohack!woods>
Planix, Inc. <email@example.com>; Secrets of the Weird <firstname.lastname@example.org>