Constantly running out of sessionid's.

[Harald Hannelius]

On Wed, 27 Sep 2006, Andrew Bartlett wrote:

> On Wed, 2006-09-27 at 11:10 -0500, Gerald (Jerry) Carter wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> > 
> > Andrew Bartlett wrote:
> > > On Wed, 2006-09-27 at 08:12 -0500, Gerald (Jerry) Carter wrote:
> > >> -----BEGIN PGP SIGNED MESSAGE-----
> > >> Hash: SHA1
> > >>
> > >> Harald Hannelius wrote:
> > >>
> > >>> Oh yes, but I (and the helldesk in particular) just love to be able to use 
> > >>> last, finger, w, who and friends to find out who has been using what.
> > >>>
> > >>> We are now nearing the limit:
> > >>>
> > >>> # sessionids.sh 
> > >>> tdb> tdb> 3568 records totalling 5537536 bytes
> > >>>
> > >>> (waiting with my fingers in my ears) :)
> > >>>
> > >>> Is there a bug that doesn't free sessionid's, or do we just have too many 
> > >>> users/computers?
> > >> You should be able to set MAX_SESSION_ID to an arbitrary value.
> > >> We should reclaim unused session ids.  So set it to something like
> > >> 10000 or what ever you need.
> > > 
> > > But wouldn't that break what he uses them for, being utmp?
> > 
> > Why?  Is there a limit in utmp ?  Or does this have to do
> > with the pty allocation or something?
> 
> Yeah, utmp requires that the session id be encoded into a limited space
> (2 byte printable character is the current restriction) space.

But why don't the sessionids get freed? Usage is growing all the time:

# sessionids.sh 
tdb> tdb> 4254 records totalling 6602208 bytes
#

Any clues what I could check for? 


-- 
A: Top Posters
Q: What is the most annoying thing on mailing lists?

Harald H Hannelius | harald/a\arcada.fi      | GSM +358 50 594 1020