22 Feb
2003
22 Feb
'03
01:53
* PL O'Smith[02-21-03 20:08]: > On Friday 21 February 2003 06:43 pm, zentara wrote: > > On Fri, 21 Feb 2003 16:53:04 -0500 > > > > PL O'Smith wrote: > > >Hi all, > > >I seem to remember several here complaining about their hard drive > > > led blinking about every 5 seconds and seeing a solution to it as > > > well. I don't remember when those mails come out, so don't know > > > which month to look for them in the Archives. > > > > > >Does someone remember the fix, cause, etc., so that I might > > > investigate also. I seem to remember it had something to do with > > > reiserfs and something. I'll try looking at the help files Togan > > > provides us too as it might be listed there. If something comes to > > > mind, please pass it along. ...chop...chop... > > 1. 1 fellow needed to stop the updatedb from running in a manner > > which flushes some buffers every 5 secs. > > 2. one thing was about some glitch in Win4lin, are you running that? > > > > The best thing you can do, is log on as root, with no X running. > > Then look at "top" and "ps auxww" and start eliminating > > apps until the clicking stops. Then that is your app. > > > > Check your logs, one of your apps may be writing something to > > the system logs every 5 secs. > > I did manage to find the previous mails about the 5 second HD blink. > None of what was discussed seem to apply to me though. I don't run > Win4Lin and only have a small partition of reiserfs installed, which > unmounting that didn't make a difference. > > So I started stopping processes to check things. I went to init 3 and > the blinking stopped. I looked at the processes running anyway, then > rebooted. Booted to the login screen and still no HD blinking lite. > Logged into KDE and blinking started again. Run the problem/bug down > to the "kded" process. Stopping that seem to eliminate the problem, > but I am told that is the kde daemon and could/should not be stopped. > > So I am curious, now what is kded and how is it causing minor HD > activity? I do not know the answer to your last question, *but*, cupsd checks for print requests every 5 seconds and loged the request to /var/log/cups/access_log until I updated to cups-1.1.18-0 (was 1.1.16). Could this be the cause?? -- Patrick Shanahan Please avoid TOFU and trim >quotes< http://wahoo.no-ip.org Registered Linux User #207535 icq#173753138 @ http://counter.li.org