diff options
| author | https://me.yahoo.com/a/g3Ccalpj0NhN566pHbUl6i9QF0QEkrhlfPM-#b1c14 <diana@web> | 2015-02-16 20:08:03 +0100 |
|---|---|---|
| committer | GNU Hurd web pages engine <web-hurd@gnu.org> | 2015-02-16 20:08:03 +0100 |
| commit | 95878586ec7611791f4001a4ee17abf943fae3c1 (patch) | |
| tree | 847cf658ab3c3208a296202194b16a6550b243cf /open_issues/bash_busy-loop.mdwn | |
| parent | 8063426bf7848411b0ef3626d57be8cb4826715e (diff) | |
| download | web-95878586ec7611791f4001a4ee17abf943fae3c1.tar.gz web-95878586ec7611791f4001a4ee17abf943fae3c1.tar.bz2 web-95878586ec7611791f4001a4ee17abf943fae3c1.zip | |
rename open_issues.mdwn to service_solahart_jakarta_selatan__082122541663.mdwn
Diffstat (limited to 'open_issues/bash_busy-loop.mdwn')
| -rw-r--r-- | open_issues/bash_busy-loop.mdwn | 33 |
1 files changed, 0 insertions, 33 deletions
diff --git a/open_issues/bash_busy-loop.mdwn b/open_issues/bash_busy-loop.mdwn deleted file mode 100644 index 5228ba33..00000000 --- a/open_issues/bash_busy-loop.mdwn +++ /dev/null @@ -1,33 +0,0 @@ -[[!meta copyright="Copyright © 2010 Free Software Foundation, Inc."]] - -[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable -id="license" text="Permission is granted to copy, distribute and/or modify this -document under the terms of the GNU Free Documentation License, Version 1.2 or -any later version published by the Free Software Foundation; with no Invariant -Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license -is included in the section entitled [[GNU Free Documentation -License|/fdl]]."]]"""]] - -I've first seen this problem after having had the following command line run -for a week, or two, or three: - -Start `screen`. Find PID of pfinet. - - $ while sleep 66; do echo "$(date)" " $(ps --no-header --format=hurd -p [PID])"; done | tee ps-pfinet - -Leave it running, detach from `screen`. - -Eventually, the main `bash` process will go bonkers and eat 100 % CPU time. -Reproduced on four different systems. - -A faster way to reproduce this, again inside `screen`; every three seconds, -write text in 10 MiB bursts to the terminal: - - $ while sleep 3; do date > tmp/tmp && yes "$(date)" | dd bs=1M count=10; done - -This one only needs like ten hours, before `bash` starts its busy-loop, from -which it can only be terminated with `SIGKILL`. At this point, the `term`, -`screen`, `fifo` processes also have used 40, 52, 25 minutes of CPU time, -respectively, but appear to be still working fine. - -I did not yet start debugging this. |