[Bug 324271] RFE and Patch: Provide enhanced mod_dav_svn /etc/httpd/conf.d/subversion.conf file.
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=324271
Edwin ten Brink <edwin(a)tenbrink-bekkers.nl> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #220681|0 |1
is obsolete| |
--- Comment #8 from Edwin ten Brink <edwin(a)tenbrink-bekkers.nl> 2009-06-14 16:23:15 EDT ---
Created an attachment (id=347854)
--> (https://bugzilla.redhat.com/attachment.cgi?id=347854)
Updated /etc/httpd/conf.d/subversion.conf replacement
Still present in F-11. Upstream (1.6.2) is still not updated.
I have integrated the comments in the originally posted replacement
/etc/httpd/conf.d/subversion.conf. This file should go into the source location
/subversion-{version}/packages/rpm/redhat-8+/subversion.conf (see attachment).
Since this file is specific to rpm (Fedora) based packages, I find it hard to
believe that this excellently documented file has not yet made it into the
upstream source, if not as a Fedora-specific patch. Setting up subversion for
the first time really is a complex process especially with SELinux on, so our
users deserve this piece of documentation.
Getting this patch accepted upstream is no task the reporter should be
requested to do since it involves more than just filing the bug; this is really
a task for the package maintainer.
--
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.
15 years
[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 #30 from Michael Schwendt <mschwendt(a)gmail.com> 2009-06-14 12:42:03 EDT ---
What else can I do to avoid that we don't talk past eachother, please?
> rsyslog does not discard selectors silently. First of all, it logs them,
It does _not_ log them. At least not in the example I offer in this ticket.
Yes, it's bad luck that an entire rule gets disabled, see comment 14, please.
> It does not make sense to include a facility to output
> to stderr if nobody will ever see stderr.
What sort of messages do you refer to?
If I log in to a machine and run "sudo /sbin/service rsyslog restart", why
would I not see warnings/errors printed to stderr?
--
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.
15 years
[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 #29 from Rainer Gerhards <rgerhards(a)hq.adiscon.com> 2009-06-14 12:14:59 EDT ---
That's at the core of my question: what is "everything possible" - and how to
configure what it should do? And should it do this always, or needs it be
configurable?
And in regard to comment 27: rsyslog does not discard selectors silently. First
of all, it logs them, so whatever action you have configured (provided you did
it right), you will see them on. That was the primary method of configuring
things so that an admin gets the notifications it wants.
Also, messages are intended to be printed on stderr, but there was a bug which
caused them to be not printed if rsyslogd was backgrounded. Based on the
feedback, I am now tempted to change it that way that even then messages are
printed. However, to do so I would like to hear how these stderr messages be
retrieved. It does not make sense to include a facility to output to stderr if
nobody will ever see stderr. So far, there was no convincing argument that it
would help. Please note that I am overlooking something trivial, but if so,
please educate me...
--
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.
15 years
[Bug 335551] abiword wakes up the CPU while doing nothing
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=335551
William Lovaton <walovaton(a)yahoo.com.mx> changed:
What |Removed |Added
----------------------------------------------------------------------------
Version|9 |11
--- Comment #6 from William Lovaton <walovaton(a)yahoo.com.mx> 2009-06-14 09:24:31 EDT ---
Well, I just installed Fedora 11 on my laptop and this is still a problem,
powertop show 2 wps for abiword while unfocused and 3.7 wps when focused.
Abiword version is abiword-2.6.8-2.fc11.i586. Just as a comment, gnumeric do
not generate any wake ups while idle.
The strace log is the following:
08:15:22.467835 restart_syscall(<... resuming interrupted call ...>) = 0
08:15:22.696204 gettimeofday({1244985322, 696314}, NULL) = 0
08:15:22.696467 read(3, 0x8b6b998, 4096) = -1 EAGAIN (Resource temporarily
unavailable)
08:15:22.696676 gettimeofday({1244985322, 696738}, NULL) = 0
08:15:22.696823 poll([{fd=4, events=POLLIN}, {fd=3, events=POLLIN}, {fd=8,
events=POLLIN|POLLPRI}, {fd=12, events=POLLIN|POLLPRI}, {fd=13,
events=POLLIN|POLLPRI}, {fd=14, events=POLLIN|POLLPRI}, {fd=15, events=POLLIN},
{fd=10, events=POLLIN|POLLPRI}], 8, 0) = 0 (Timeout)
08:15:22.697111 read(3, 0x8b6b998, 4096) = -1 EAGAIN (Resource temporarily
unavailable)
08:15:22.697252 gettimeofday({1244985322, 697299}, NULL) = 0
08:15:22.697393 poll([{fd=4, events=POLLIN}, {fd=3, events=POLLIN}, {fd=8,
events=POLLIN|POLLPRI}, {fd=12, events=POLLIN|POLLPRI}, {fd=13,
events=POLLIN|POLLPRI}, {fd=14, events=POLLIN|POLLPRI}, {fd=15, events=POLLIN},
{fd=10, events=POLLIN|POLLPRI}], 8, 500) = 0 (Timeout)
08:15:23.198367 gettimeofday({1244985323, 198472}, NULL) = 0
08:15:23.198650 read(3, 0x8b6b998, 4096) = -1 EAGAIN (Resource temporarily
unavailable)
08:15:23.198830 gettimeofday({1244985323, 198891}, NULL) = 0
08:15:23.198971 poll([{fd=4, events=POLLIN}, {fd=3, events=POLLIN}, {fd=8,
events=POLLIN|POLLPRI}, {fd=12, events=POLLIN|POLLPRI}, {fd=13,
events=POLLIN|POLLPRI}, {fd=14, events=POLLIN|POLLPRI}, {fd=15, events=POLLIN},
{fd=10, events=POLLIN|POLLPRI}], 8, 499) = 0 (Timeout)
08:15:23.700643 gettimeofday({1244985323, 700722}, NULL) = 0
08:15:23.700871 read(3, 0x8b6b998, 4096) = -1 EAGAIN (Resource temporarily
unavailable)
08:15:23.700998 gettimeofday({1244985323, 701044}, NULL) = 0
08:15:23.701115 poll([{fd=4, events=POLLIN}, {fd=3, events=POLLIN}, {fd=8,
events=POLLIN|POLLPRI}, {fd=12, events=POLLIN|POLLPRI}, {fd=13,
events=POLLIN|POLLPRI}, {fd=14, events=POLLIN|POLLPRI}, {fd=15, events=POLLIN},
{fd=10, events=POLLIN|POLLPRI}], 8, 500) = 0 (Timeout)
08:15:24.202053 gettimeofday({1244985324, 202136}, NULL) = 0
08:15:24.202283 read(3, 0x8b6b998, 4096) = -1 EAGAIN (Resource temporarily
unavailable)
08:15:24.202431 gettimeofday({1244985324, 202478}, NULL) = 0
08:15:24.202548 poll([{fd=4, events=POLLIN}, {fd=3, events=POLLIN}, {fd=8,
events=POLLIN|POLLPRI}, {fd=12, events=POLLIN|POLLPRI}, {fd=13,
events=POLLIN|POLLPRI}, {fd=14, events=POLLIN|POLLPRI}, {fd=15, events=POLLIN},
{fd=10, events=POLLIN|POLLPRI}], 8, 499) = 0 (Timeout)
--
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.
15 years
[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 #25 from Michael Schwendt <mschwendt(a)gmail.com> 2009-06-14 05:45:08 EDT ---
Whom is that question directed at? I've answered multiple times before that *I*
would prefer to learn about syntax errors on stderr always, e.g. in comment 16.
Unfortunately, it seems I'm the only one who considers (and considered) the
other behaviour as broken. When I originally learnt about this and reported
this in 2004 (!) about syslogd (prior to syslog-ng and rsyslog), I was in good
hope that I would meet interest in fixing it for Fedora and derived
distributions.
--
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.
15 years