May 2009 - triage - Fedora Mailing-Lists

[Bug 287411] Kernel loses track of CWD of process

by Red Hat Bugzilla

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=287411 --- Comment #58 from Orion Poplawski <orion(a)cora.nwra.com> 2009-05-28 12:12:51 EDT --- BTW - I can confirm that this bug (restarted autofs) is fixed on F-11. Shall I file a new bug on initscripts? -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

14 years, 11 months

1
0
0 / 0

[Bug 287411] Kernel loses track of CWD of process

by Red Hat Bugzilla

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=287411 --- Comment #57 from Orion Poplawski <orion(a)cora.nwra.com> 2009-05-28 12:03:30 EDT --- Removing 05-netfs does prevent the problem from occurring. /etc/NetworkManager/dispatcher.d/05-netfs is part of initscripts. This approach does make more sense for the laptop case where the machine is likely to be in another location when it wakes up. The better long term solution is probably more graceful handling of the disappearance of NFS servers, but I'm not sure how realistic that is. In the meantime, I'm not sure how you distinguish between the desktop and laptop case. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

14 years, 11 months

1
0
0 / 0

[Bug 136141] syntax errors in syslogd.conf cause lost log messages without warning

by Red Hat Bugzilla

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=136141 --- Comment #24 from Rainer Gerhards <rgerhards(a)hq.adiscon.com> 2009-05-28 12:00:46 EDT --- I have added the exit(1) facility to the code [1], but the question with stderr remains. Feedback appreciated. [1] http://git.adiscon.com/?p=rsyslog.git;a=commitdiff;h=23dac82b684e966490de... -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

14 years, 11 months

1
0
0 / 0

[Bug 136141] syntax errors in syslogd.conf cause lost log messages without warning

by Red Hat Bugzilla

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=136141 --- Comment #23 from Rainer Gerhards <rgerhards(a)hq.adiscon.com> 2009-05-28 10:39:05 EDT --- I have now looked at the code (also, patch is applied). I think it probably is not sufficient to return an exit state. There are some other (exotic) conditions that can stop startup, like not being able to create a queue (for whatever wild reason). In those cases, messages are emitted to stderr, too. So it would probably make more sense to keep stderr open after the fork and continue to emit messages to there. What do you say? -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

14 years, 11 months

1
0
0 / 0

[Bug 136141] syntax errors in syslogd.conf cause lost log messages without warning

by Red Hat Bugzilla

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=136141 --- Comment #22 from Rainer Gerhards <rgerhards(a)hq.adiscon.com> 2009-05-28 09:54:41 EDT --- > By the time rsyslog parses the config file, it is already forked and without > access to stderr. ah, yes, that's right... I just looked, the patch made it to me, but only to the (not visited) spam folder ;) Will apply. The solution sounds reasonable. Will look what it takes to return the error code. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

14 years, 11 months

1
0
0 / 0

[Bug 136141] syntax errors in syslogd.conf cause lost log messages without warning

by Red Hat Bugzilla

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=136141 --- Comment #21 from Tomas Heinrich <theinric(a)redhat.com> 2009-05-28 09:44:32 EDT --- >> I forgot to mention: error messages go to stderr by default. > Doesn't work in Fedora 10. One mistyped selector, and an entire rule is ignore > silently. See comment 14. By the time rsyslog parses the config file, it is already forked and without access to stderr. (Rainer, there's actually a bug in that rsyslog always tries to write to stderr. :) When forked, it accidentally writes to the file opened with fd 2. Hope the patch got to you.) So IMO a reasonable solution is to change the code to return some non-zero value when -N encounters an error, run rsyslog -N first, discard the output as not to spam the screen and if retval != 0, print a warning about config file syntax a then start the daemon. What do you say? -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

14 years, 11 months

1
0
0 / 0

[Bug 136141] syntax errors in syslogd.conf cause lost log messages without warning

by Red Hat Bugzilla

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=136141 --- Comment #20 from Rainer Gerhards <rgerhards(a)hq.adiscon.com> 2009-05-28 09:09:56 EDT --- comment 16 demands that output is written to stderr. I don't know why this is disabled in Fedora, but rsyslog be default does that. But what I was really interested in is what shall happen if there is a problem with the rule? Is it sufficient to just push it to stderr? What to do if -N comes back with an error exit code? This is not really a simple issue, please also have a look at http://blog.gerhards.net/2008/07/rsyslog-error-reporting-how-to-do-it.html Rainer -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

14 years, 11 months

1
0
0 / 0

[Bug 136141] syntax errors in syslogd.conf cause lost log messages without warning

by Red Hat Bugzilla

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=136141 --- Comment #19 from Michael Schwendt <bugs.michael(a)gmx.net> 2009-05-28 09:02:37 EDT --- > What would you consider an appropriate action to be taken > if there is a syntax error? With option -N, to exit with a non-zero return-code. Without option -N, see comment 16. > I forgot to mention: error messages go to stderr by default. Doesn't work in Fedora 10. One mistyped selector, and an entire rule is ignore silently. See comment 14. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

14 years, 11 months

1
0
0 / 0

[Bug 136141] syntax errors in syslogd.conf cause lost log messages without warning

by Red Hat Bugzilla

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=136141 --- Comment #18 from Rainer Gerhards <rgerhards(a)hq.adiscon.com> 2009-05-28 08:46:12 EDT --- I forgot to mention: error messages go to stderr by default. This is disable by specifiying $ErrorMessagesToStderr off [Implemented in 3.21.1+] But if that is not given, all error messages to to stderr. Might it be that nobody takes them from there? -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

14 years, 11 months

1
0
0 / 0

[Bug 136141] syntax errors in syslogd.conf cause lost log messages without warning

by Red Hat Bugzilla

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=136141 Rainer Gerhards <rgerhards(a)hq.adiscon.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rgerhards(a)hq.adiscon.com --- Comment #17 from Rainer Gerhards <rgerhards(a)hq.adiscon.com> 2009-05-28 08:42:24 EDT --- What would you consider an appropriate action to be taken if there is a syntax error? -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

14 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

triage May 2009