This was pulled from the mgetty man file:
/var/log/mgetty.log.ttyxx
Debug log file, see below.
DIAGNOSTICS
If mgetty doesn't work the way it should, the main source of diagnostic
data is the log file. It can be found in "/var/log/mgetty.log.ttyxx"
(for the mgetty process handling "ttyxx"). If it doesn't contain
enough details, enhance the log level with the '-x' option to mgetty,
e.g. "-x 5".
Many of the common problems and solutions are discussed in the mgetty
manual and the FAQ. Please see the WWW page at http://alpha.gree-
nie.net/mgetty/ for both.
Quoting "J. Rafael S�nchez" <[EMAIL PROTECTED]>:
> I have a log file, namely mgetty.log.xxx, that's getting out of hand. I've
> been googling, trying to find the answer to this issue, but nothing yet. I've
> been applying a band-aid solution by running a cron that 'ls' and grep for
> certain strings from /var/log/ and adding a script that deletes those files
> every so often.
>
> I would like to understand what is causing it though. I've checked
> syslog.conf and nothing is obvious there. I've also looked at
> /etc/mgetty+sendfax folder for signs but nothing.
>
> Any thoughts will be appreciated.
>
> Thank you greatly.
>
> Rafael.
>
>
> J.Rafael.S�nchez
> Itres Research Limited
> www.itres.com
> P.403.250.9944
> F.403.250.9916
>
--
Sending all process the TERM signal
Vs.
Windows is shutting down...
Which one sounds smarter?
