Re: zillions of mgetty.log.ttyS4.1.1.1.1... messages

[Billy Davis]

Thanks for the reply Eric.  I reviewed the mgetty file and found the astersik, and I see what you have changed.  However, it seems to me that what ever problem caused these 'zillions' of files to be created, will still create them, or am I missing something?  Your change seems to limit new log file creation to those ports that are valid (ie, S0, PS13, PS14 and PS15 in your case).  In my case, since I only have one valid port (S4), then I would be simply changing the line '/var/log/mgetty.log.tty* {' to be '/var/log/mgetty.log.ttyS4 {'  which would still allow error messages to be created for port S4.  But, these are the errors that I was getting.  What I really want to know, is what causes the S4 port to start creating bunches and bunches of empty log files in just a few seconds.  Any idea?   Thanks again, Billy ----- Original Message ----- From: Eric Wood To: [EMAIL PROTECTED] Sent: Wednesday, February 19, 2003 4:00 PM Subject: Re: zillions of mgetty.log.ttyS4.1.1.1.1... messages For some reason, the mgetty guys uses an asterisk in the: /etc/logrotate.d/mgetty file.    Take out that asterisk.   My file looks like this now:       /var/log/mgetty.log.ttyS0 {      nocompress      missingok     }     /var/log/mgetty.log.ttyPS13 {      nocompress      missingok     }     /var/log/mgetty.log.ttyPS14 {      nocompress      missingok     }     /var/log/mgetty.log.ttyPS15 {      nocompress      missingok     } -eric wood ----- Original Message ----- From: Billy Davis To: [EMAIL PROTECTED] Sent: Wednesday, February 19, 2003 3:16 PM Subject: zillions of mgetty.log.ttyS4.1.1.1.1... messages We have a RH7.3 server with an internal modem set up as ttyS4.  The modem works great whenever we need to dial in or out.  However, yesterday, the Server started acting very strangely (spooler quit printing, modem would not answer the phone) and we started getting an error message about 'mgetty trying to respawn to quickly, port locked for 5 minutes'.  While trying to find out what was going on, I happened to notice that there were a 'zillion'  zero byte length messages in /var/log named mgetty.log.ttyS4.1.1.1.1... up thru mgetty.log.ttyS4.4.4.4.4.4...  It took 30 minutes to delete them all (they could not be deleted with a single rm command), but after they were deleted, the system started acting normally again.  Does anybody know what caused this problem and how to prevent it from occurring again?   Thanks, Billy