[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: why not mingetty??



Hamish Moffatt <hamish@debian.org> wrote:
> On Sat, Apr 25, 1998 at 01:40:32AM -0400, Shaleh wrote:
> > The inittab setup is not different.  However, the only way to switch
> 
> That's not true, it is -- getty requires a speed, even for a virtual
> terminate, while mingetty doesn't support that.

Does this mean that mingetty won't ignore this argument?  That
should be fixed, in my opinion.

> As to the numbers, I just started up a getty on my box here:
> 
> yodeller# ps aux | grep getty
> root       384  0.0  0.0   720     0   2 SW  Feb  9   0:00 (mingetty)
> root       401  0.0  0.0   720     0   1 SW  Feb  9   0:00 (mingetty)
> root     10361  0.5  1.4   868   460   3 S    17:07   0:00 /sbin/getty 38400 tty

This is not a completely reasonable comparison (though it does show
0:00 time used by each getty, which is perhaps significant). 

(a) Some informal testing of my own seems to indicate that the 720 vs
868 k memory may not be significant. In spite of what ldd says, strace
shows:

open("/lib/libnss_db.so.1", O_RDONLY)   = 3
mmap(0, 4096, PROT_READ, MAP_PRIVATE, 3, 0) = 0x400b1000
mmap(0, 20364, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0x400b1000
mmap(0x400b5000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 3, 0x3000) = 0x400b5000
open("/lib/libdb.so.2", O_RDONLY)       = 3
mmap(0, 4096, PROT_READ, MAP_PRIVATE, 3, 0) = 0x400b6000
mmap(0, 57240, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0x400b6000
mmap(0x400c3000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 3, 0xc000) = 0x400c3000
open("/lib/libnss_files.so.1", O_RDONLY) = 3
mmap(0, 4096, PROT_READ, MAP_PRIVATE, 3, 0) = 0x400c4000
mmap(0, 31944, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0x400c4000
mmap(0x400cb000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 3, 0x6000) = 0x400cb000

(b) On the other hand, in my informal testing, I couldn't get mingetty
to run -- apparently, it can't do TIOCSCTTY on my system, so it bails
out.

(c) The distinct gettys should be started at about the same time
for RSS to mean anything.  [I can't test this because I can't get
mingetty to run for longer than a fraction of a second, but I doubt
RSS is going to be a significant issue.]

(d) Technically, you also need to compare console handling to console
handling, not console handling to serial handling.

Also, note that the mingetty feature of clear the screen on logout could
be implemented in agetty (and mgetty). On the other hand, it might be
worthwhile to make it so that mingetty will properly ignore config
arguments intended for agetty or mgetty.

Finally, note that if we get too fancy it will be tough for people who
need to use multiple gettys on the same system (but maybe that's only
important for testing purposes).

-- 
Raul


--
To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org


Reply to: