Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug
Bug#: 3434
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Matthew Kennedy (RETIRED) <mkennedy@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: tuxisuau <tuxisuau@7a69ezine.org>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 3434 depends on: Show dependency tree
Bug 3434 blocks: 8607
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug

Description:   Opened: 2002-06-05 23:26 0000 
I did install gentoo a week ago with gcc3.1 and CFLAGS=-march=athlon -O3 -pipe.

I've managed to make everything work ok, but metalog sometimes freezes and i
have to restart it, cause all programs that write things to syslog (like
postfix, login, etc) freeze with it. It occurs two or three times a day.

------- Comment #1 From Matthew Kennedy (RETIRED) 2002-07-16 10:24:02 0000 ------- 
This is not a bug. What you are seeing is the buffering nature of metalog. (see
metalog(1)). You can turn the buffing off at runtime with SIGUSR1 and turn it
back on with SIGUSR2.

Matt

------- Comment #2 From tuxisuau 2002-07-16 10:54:24 0000 ------- 
This IS a bug. Buffering nature of metalog stands for writing the logs in the
hard disk, not from accepting data from servers. &#013;It's serious enough it
makes apps freeze, and yes, it gave the same problem with the buffering
disabled.&#013;Now i'm using syslog-ng.&#013;&#013;Tuxisuau.

------- Comment #3 From Matthew Kennedy (RETIRED) 2002-07-16 18:44:10 0000 ------- 
If you use -march=i686 (instead of athlon) do you get the same problem? 

Never in several months that I have been using metalog w/ gcc3.0.4 and gcc3.1
have I see the behavior you describe.

------- Comment #4 From Matthew Kennedy (RETIRED) 2002-07-29 05:52:55 0000 ------- 
do you get a freeze at all with syslog-ng?

------- Comment #5 From Sascha Silbe 2002-10-08 11:39:33 0000 ------- 
I'm hitting the same bug. Occured during the gcc 2.95.x time and is still
happening. Had buffering turned off (-s) and tried it with buffering this week,
but it seems to only get worse if buffering is turned on (even happened
immediatly after one of the reboots).
See the comments on the other bug for details. As soon as it happens again,
I'll attach gdb to metalog. Perhaps I can get more info that way.
And please reopen the bug again, it does NOT work.

PS: athlon-xp CPU
Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug