[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 #48 from Ian Kent <ikent(a)redhat.com> 2009-05-21 12:20:51 EDT ---
(In reply to comment #47)
> I can reproduce this as well by hibernating/resuming without an autofs restart.
That could only happen if the sleep/wake functionality is doing
something like restarting autofs.
In any case this should be resolved in autofs-5.0.4 and with a
sufficiently recent kernel and F-10 doesn't have such a kernel
F-11 does and its autofs is based on 5.0.4.
Note that this cannot be fixed without a kernel that supports
the ioctl re-implementation that has been done for this and the
changes in autofs to use it.
--
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, 10 months
[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
Orion Poplawski <orion(a)cora.nwra.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |Reopened
Status|CLOSED |ASSIGNED
Version|9 |10
Resolution|WONTFIX |
--- Comment #47 from Orion Poplawski <orion(a)cora.nwra.com> 2009-05-21 10:16:20 EDT ---
I can reproduce this as well by hibernating/resuming without an autofs restart.
--
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, 10 months
[Bug 243172] APIC-Error "timer not connected to IO-APIC
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=243172
Peter Martuccelli <peterm(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |CLOSED
Resolution| |CANTFIX
--- Comment #9 from Peter Martuccelli <peterm(a)redhat.com> 2009-05-21 09:32:05 EDT ---
Closing out due to inactivity. If the reporter is still having a problem in
F11 Beta please update the report with the required information from comment
#7.
--
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, 10 months
[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 #15 from Tomas Heinrich <theinric(a)redhat.com> 2009-05-20 11:41:00 EDT ---
> With DoS I mean that an _entire rule_ is ignored -- silently (!) -- just
> because there's a subtle syntax error in it.
What else would you want to do with a malformed rule?
> silently (!)
If there are other places to log to or rsyslog can write to stderr, it does so.
> Where do you get a warning?
If you run rsyslog in debug mode, it writes to stderr. If there are rules to
log messages with the respective priority, they get logged. Provided you won't
create typos in those specific rules.
What's your opinion on the proposed solution?
--
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, 10 months
[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 #14 from Michael Schwendt <bugs.michael(a)gmx.net> 2009-05-20 10:13:23 EDT ---
With DoS I mean that an _entire rule_ is ignored -- silently (!) -- just
because there's a subtle syntax error in it. Even a ':' instead of ';' as the
separator between the selectors can be used to disable an entire rule. Other
typos disable the rule, too. As a consequence, rsyslog not even logs its
startup status message anymore as the '*.info' selector is among the ones that
are disabled silently. rsyslog doesn't print anything on stderr either. Where
do you get a warning?
> After making changes to the configuration file, you have a way to
> verify they are correct.
At least the software ought to help with verification as it parses the rules
anyway.
--
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, 10 months