mgetty+slack7+hd activity

• Messages sorted by:[ date ][ thread ][ subject ][ author ]

Hi,

On Mon, Nov 29, 1999 at 11:58:21PM +0000, bsjsnake@my-deja.com wrote:
> >Look at the mgetty log file to find out whether it's a dialout or not,
> >and whether it's mgetty that is causing this activity.
> 
> >gert
> 
> hello gert
> 
> with debug=4 -> dialout to my isp (hd lights blink every 10 sec.)

Sure, that's what we keep saying: if you are doing a dialout, mgetty will
check the lock file every 10 seconds, and thus cause disk activity.  No
way around this.

If there's NO dialout, there is nothing mgetty will be doing (except check
the modem once per *hour*, but that can be switched off).

> with debug=5 -> same as above

Sure it's the same behaviour, but now you can see it in the logs just
fine:

> 11/29 21:11:37 yS1   lock file exists (dialout)!
> 11/29 21:11:37 yS1   lockfile found, pid=172

That's where the dialout starts.

> 11/29 21:11:37 yS1   utmp + wtmp entry made
> 11/29 21:11:37 yS1   lockfile found, pid=172
> 11/29 21:11:47 yS1   lockfile found, pid=172
> 11/29 21:11:57 yS1   lockfile found, pid=172

And here you have "every 10 seconds".

But I'm not sure what is your question - this has already been said and
confirmed that *during a dialout* mgetty will cause disk I/O.

gert
-- 
USENET is *not* the non-clickable part of WWW!
                                                           //www.muc.de/~gert/
Gert Doering - Munich, Germany                             gert@greenie.muc.de
fax: +49-89-35655025                        gert.doering@physik.tu-muenchen.de