How is this a serious problem? Fix the problem, or /dev/null the mail. Pete Capelli - NSEC - [EMAIL PROTECTED] "Those who would give up essential liberty for temporary safety deserve neither liberty nor safety" - Benjamin Franklin, 1759 PGP Key ID:3AD72805 > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On > Behalf Of Guido > Germano > Sent: Wednesday, July 07, 1999 6:00 AM > To: [EMAIL PROTECTED]; [EMAIL PROTECTED] > Subject: Serious 2.0.13 problem with chkutent > > > Systems: SGI Origin 2000 IP27 running IRIX64 6.5.3f > SGI Indy IP22 running IRIX 6.5.3f > > Ssh version: 2.0.13 > > Description: since we've been using ssh on our SGIs, root (i.e. me) is > getting a message every night from cron that complains about the > necessity of doing a utmp fix with chkutent on connections done with > ssh. Chkutent is run automatically every night by the default system > crontab. This is a line from a sample message: > > utmpx fix - muataz ttyq6 q6 18386 - see chkutent(1M) > > Any ideas, apart from filtering out this mail (I'm using procmail)? > > Regards > > Guido Germano > > Theoretical Physics, University of Bristol, England > tel. +44-117-928 8755, fax +44-117-9255624 > http://www.phy.bris.ac.uk/staff/germano_g.html >
