You are probably having the problem since you installed from a binary (and this may also explain why you don't have a policy.h file) and didn't compile from source (ftp://alpha.greenie.net/pub/mgetty/source/). In any case, have you tried restarting mgetty and playing with the -x option? This controls the debug level and in turn affects the verbosity of information that is logged. Try restarting it with -x 0 and see if anything changes.
What options is your mgetty currently running with? If it is running with a reasonable debug level then perhaps the problem is mgetty itself since it is reporting errors (maybe you could copy a portion of the file to this thread). -J Quoting "J. Rafael S�nchez" <[EMAIL PROTECTED]>: > I've already looked at the man pages too... I've looked at the site > mentioned on it and still nothing. Am I missing something? They talk about > the 'policy.h' file. I haven't found this file. I installed from binaries > and I'm running mgetty-1.1.28-3. > > Thank you > Rafael > > > J.Rafael.S�nchez > Itres Research Limited > www.itres.com > P.403.250.9944 > F.403.250.9916 > > ----- Original Message ----- > From: "Jacob C" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Wednesday, July 02, 2003 12:23 PM > Subject: Re: (clug-talk) what causes log files to be created with long > strings of numbers? > > > > 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? > > -- Sending all process the TERM signal Vs. Windows is shutting down... Which one sounds smarter?
