Hi Jacques,

>(from your description, I assume you are running a redhat system).

Yes, Red Hat 5.2 and linuxconf 1.13 subrev 5.
Sorry I didn't provide that information in earlier message.

>This is all linuxconf knows about apache. It compares the revision date of
>the 3 config files and compares that with the process pointed by the
>/var/run/httpd.pid file. If anyone file is newer, then linuxconf call the
>script with the restart option. Is it possible that one of those file has
>a date in the future ? If this is the case, do a touch on it to set the
>date to "now" and things will be fixed.

I found the problem.  When I compiled Apache 1.3.3 I used the default PID
location in the httpd.conf file, which is /var/log/httpd/httpd.pid;
therefore the file /var/run/httpd.pid did not exist.  I changed the PID
location in the httpd.conf file to /var/run/httpd.pid and rebooted the web
server.  Linuxconf no longer restarts the web server each time I quit.

Unfortunately linuxconf still insists on reloading my network each time I
exit... :)


>> 2. LinuxConf is trying to reload my network but getting the following
errors:
>> 
>> Executing: /etc/rc.d/rc3.d/S10network reload
>>      * eth0:0-: unknown interface
>>      * eth0:1-: unknown interface
>
>This is a bug in ifconfig I think. the command generated to remove an IP
>alias is correct. Further, it works, but ifconfig report those errors. I
>have to find out why it behaves like that (this is new)

Doesn't seem to affect the network functionality... just annoying, and
filling my linuxconf logs with error messages, heh.

>I would call this a cosmetic bug :-)

Good. :)

Also, I've had two server break-in attempts in the past few weeks... both
attempts tried to force a buffer overflow on vpop3d.  Doesn't look like it
was successful though...

Cheers... Dino


-----
   Dino Nardini, BSc, Certified Web Master 
   mailto:[EMAIL PROTECTED]

   Explore Nova Scotia - "Canada's Ocean Playground"
   http://www.explorenovascotia.com


---
You are currently subscribed to linuxconf as: [[email protected]]
To unsubscribe, forward this message to [EMAIL PROTECTED]

Reply via email to