Solaris 5.6 init growing...

• Messages sorted by:[ date ][ thread ][ subject ][ author ]

Hi,

On Tue, Jan 19, 1999 at 12:07:09PM -0400, David L. Potter wrote:
> We're running mgetty 1.0.0 on 62 modems with about 2,500 modem connections
> daily. ( We've run newer versions with same result. )

Nice figures :-)

> We're experiencing no noticable problems with modem connections or
> operations... mgetty is handling the connections suitably, 

Good.

> however... the init process is growing at a rather significant rate.

Ugh. Seems to have a memory leak somewhere, concerning "cleanup" after
forked children.

> We've run two tests, disabling dial-in access, and leaving telnet access
> so users can 'exercise' the system. In both cases the size of the init
> process was stable during the test period and then started to grow as soon
> as we re-enable mgetty/modems.

Telnet isn't handled by init - actually, usually nothing but console login
(real console, not X11) and modem/serial terminal logins is done by init.

> The growth of init is quite significant... starting from 680k ...and
> growing to 100mb (plus) in about 5 days. 

This is pretty bad, indeed.

> Anyone else seen this or have any ideas?

I haven't seen this, but I'm afraid there is not anything you can do
(right now) except to talk to SUN about it.  One might consider to write
an "init replacement for mgetty use", but that's seriously ugly, as init 
will do lots of stuff with the utmp/wtmp files that's not very portable
and usually very badly documented.

You might try disabling all mgetty ports, SIGHUPing init, reenable all
ports, and SIGHUP it again - in the hope that it will clean up some
internal tables when doing this, but I'm not very confident that it will
help.

gert
-- 
USENET is *not* the non-clickable part of WWW!
                                                           //www.muc.de/~gert/
Gert Doering - Munich, Germany                             gert@greenie.muc.de
fax: +49-89-35655025                        gert.doering@physik.tu-muenchen.de