[opensuse] Fork Burst Every 5 Minutes
Hi, I've noticed by watching GKrellM that every five minutes there's a brief burst of about 170 forks within a period of a second or so on my openSUSE 11.1 system. I wonder: 1) Does anyone know what this might be? 2) How might I learn what process is performing these forks? Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
* Randall R Schulz <rschulz@sonic.net> [01-19-09 19:47]:
I've noticed by watching GKrellM that every five minutes there's a brief burst of about 170 forks within a period of a second or so on my openSUSE 11.1 system.
I wonder:
1) Does anyone know what this might be?
??
2) How might I learn what process is performing these forks?
you will have to catch it at the right time, and do: ps -e axfj |less will capture a tree view of all processes that you can search. but... you will have to initiate the command at the time the ?forks are running. -- Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://counter.li.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Or you could try something like: top -b -d .01 | tee >> toptest And watch the time when it happens so that you can find the corresponding output. The '-b' is for cleaner output and the '-d .01' specified the time interval between data outputs. - James W. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Monday January 19 2009, Randall R Schulz wrote:
Hi,
I've noticed by watching GKrellM that every five minutes there's a brief burst of about 170 forks within a period of a second or so on my openSUSE 11.1 system.
Another thing I noticed, owing to having a remote GKrellM display for my 10.3 box displayed on my 11.1 box, is that _both_ of these systems exhibit the same phenomenon. Moreover, it is _synchronized_ between the two systems, implying they're both doing this on a wall-clock schedule (both systems use NTP, of course, so they're clocks are at most a small fraction of a second disparate). Does this help suggest a cause? Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Mon, Jan 19, 2009 at 8:46 PM, Randall R Schulz <rschulz@sonic.net> wrote:
On Monday January 19 2009, Randall R Schulz wrote:
Hi,
I've noticed by watching GKrellM that every five minutes there's a brief burst of about 170 forks within a period of a second or so on my openSUSE 11.1 system.
Another thing I noticed, owing to having a remote GKrellM display for my 10.3 box displayed on my 11.1 box, is that _both_ of these systems exhibit the same phenomenon. Moreover, it is _synchronized_ between the two systems, implying they're both doing this on a wall-clock schedule (both systems use NTP, of course, so they're clocks are at most a small fraction of a second disparate).
Does this help suggest a cause?
Randall Schulz --
Maybe shutdown crond for a while as a test? -- ----------JSA--------- Someone stole my tag line, so now I have this rental. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Monday January 19 2009, John Andersen wrote:
On Mon, Jan 19, 2009 at 8:46 PM, Randall R Schulz <rschulz@sonic.net> wrote:
On Monday January 19 2009, Randall R Schulz wrote:
Hi,
I've noticed by watching GKrellM that every five minutes there's a brief burst of about 170 forks within a period of a second or so on my openSUSE 11.1 system.
Another thing I noticed, owing to having a remote GKrellM display for my 10.3 box displayed on my 11.1 box, is that _both_ of these systems exhibit the same phenomenon. Moreover, it is _synchronized_ between the two systems, implying they're both doing this on a wall-clock schedule (both systems use NTP, of course, so they're clocks are at most a small fraction of a second disparate).
Does this help suggest a cause?
Randall Schulz --
Maybe shutdown crond for a while as a test?
I did think of cron. On your suggestion, I ran the test of temporarily shutting it down and indeed, this prevents the fork burst. One thing I don't think I've ever been able to do is _find_ all the crontabs in a SuSE Linux / openSUSE installation.
-- ----------JSA--------- Someone stole my tag line, so now I have this rental.
Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tuesday January 20 2009, Randall R Schulz wrote:
On Monday January 19 2009, John Andersen wrote:
...
Maybe shutdown crond for a while as a test?
I did think of cron. On your suggestion, I ran the test of temporarily shutting it down and indeed, this prevents the fork burst.
One thing I don't think I've ever been able to do is _find_ all the crontabs in a SuSE Linux / openSUSE installation.
OK, so I did some script spelunking and I think I know where the fork burst originates, based on the fact that only one crontab has a 5-minute interval configured: Munin's cron script. Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Randall R Schulz wrote:
I did think of cron. On your suggestion, I ran the test of temporarily shutting it down and indeed, this prevents the fork burst.
One thing I don't think I've ever been able to do is _find_ all the crontabs in a SuSE Linux / openSUSE installation.
I think they are all here: /var/spool/cron/tabs/*, /etc/crontab /etc/cron.d/* How about 'grep cron /var/log/messages'? The regular /usr/lib/cron/run-crons doesn't usually get logged, but anything should. -- /Per Jessen, Zürich -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
* Randall R Schulz <rschulz@sonic.net> [01-20-09 09:03]:
One thing I don't think I've ever been able to do is _find_ all the crontabs in a SuSE Linux / openSUSE installation.
/var/spool/cron/ /etc/cron.d/ /etc/cron.hourly/ /etc/cron.daily/ /etc/cron.weekly/ /etc/cron.monthly/ -- Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://counter.li.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Patrick Shanahan wrote:
* Randall R Schulz <rschulz@sonic.net> [01-20-09 09:03]:
One thing I don't think I've ever been able to do is _find_ all the crontabs in a SuSE Linux / openSUSE installation.
[snip]
/etc/cron.hourly/ /etc/cron.daily/ /etc/cron.weekly/ /etc/cron.monthly/
<nitpicking> And those don't _actually_ contain any crontabs, they're collections of scripts being run by openSUSEs "run-crons". </nitpicking> -- /Per Jessen, Zürich -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tuesday January 20 2009, Patrick Shanahan wrote:
* Randall R Schulz <rschulz@sonic.net> [01-20-09 09:03]:
One thing I don't think I've ever been able to do is _find_ all the crontabs in a SuSE Linux / openSUSE installation.
/var/spool/cron/ /etc/cron.d/ /etc/cron.hourly/ /etc/cron.daily/ /etc/cron.weekly/ /etc/cron.monthly/
Actually, if you look in those directories, you see that they're scripts run on the specified interval by /usr/lib/cron/run-crons (itself run once per minute by the entry in /etc/crontab). The actual crontabs are /etc/crontab and the files in /etc/cron.d/ (and any per-user crontab established via the crontab comman; they're recorded in /var/spool/cron/tabs/).
-- Patrick Shanahan
Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 1/20/2009 at 3:23 PM, Randall R Schulz <rschulz@sonic.net> wrote: Actually, if you look in those directories, you see that they're scripts run on the specified interval by /usr/lib/cron/run-crons (itself run once per minute by the entry in /etc/crontab). The actual crontabs are /etc/crontab and the files in /etc/cron.d/ (and any per-user crontab established via the crontab comman; they're recorded in /var/spool/cron/tabs/).
Are you certain about the fact they run every minute? In my system they appear to run every 15 minutes -*/15 * * * * root test -x /usr/lib/cron/run-crons && /usr/lib/cron/run-crons >/dev/null 2>&1 Which makes perfect sense, as the 'smallest' interval the scripts have is cron.hourly (so every 4 checks). Dominique -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tuesday January 20 2009, Dominique Leuenberger wrote:
On 1/20/2009 at 3:23 PM, Randall R Schulz <rschulz@sonic.net> wrote:
...
Are you certain about the fact they run every minute? In my system they appear to run every 15 minutes -*/15 * * * * root test -x /usr/lib/cron/run-crons && /usr/lib/cron/run-crons >/dev/null 2>&1
Sorry. That's what I meant to say.
Which makes perfect sense, as the 'smallest' interval the scripts have is cron.hourly (so every 4 checks).
Dominique
Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (6)
-
Dominique Leuenberger -
james Wright -
John Andersen -
Patrick Shanahan -
Per Jessen -
Randall R Schulz