On 12/28/2010 10:49 AM, Frank Cox wrote:
> On Tue, 28 Dec 2010 10:13:45 -0600
> Robert Nichols wrote:
>
>> It might be worthwhile to report a new bug against privoxy since the
>> failure to do a reload after logrotate is a more serious problem than
>> the one reported in #597732.
>
> This is privoxy rpm that I created myself by copying the spec file from
> a Fedora srpm and substituting the latest version (3.0.17) of privoxy.
>
> The logrotate configuration file for privoxy disappeared in the latest version
> so I had to copy it in from an older version and haven't yet gotten around to
> figuring out how to integrate it into the rpm properly.
>
> Since the rpm I'm using isn't "official" but rather is just something I've
> slapped together I don't think a bug report would be particularly useful.
>
> I got tired of privoxy crashing and want to see if a substantially newer
> version will crash less.
>
> The behaviour with system-config-services varies under Centos from what is
> contained in that bug report. Using the init file that came with the source
> tarball I see that system-config-services doesn't even try to report its
> status, but rather simply says "Usage: /etc/init.d/privoxy {start|stop|
> restart}" in the Status window.
That's the problem that was reported in the Fedora bugzilla. What you've
built is an RPM with a logrotate.d file that requests an action ("reload")
that the init.d file does not support. It doesn't work, but the logrotate.d
file is ignoring the error and discarding the error message.
system-config-services is having a problem because the "status" action is
not supported. If you were to substitute the more complete init.d file
that was attached to that bug report, I believe that would take care of
both the logrotate problem and the status report problem.
--
Bob Nichols "NOSPAM" is really part of my email address.
Do NOT delete it.