Re: Bug#334824: logrotate: Postrotate documentation - Why restart?

2005-10-20 Thread Adam Conrad
Kai Hendry wrote: >I discovered a HUP signal causes Apache just to reload the configs. > > > And crash, in certain interesting and curious corner cases. >Though in Debian Unstable's /etc/logrotate.d/apache2 it actually does a >*restart* not a kill -HUP. > >Which in /etc/init.d/apache2 issues a

Re: Bug#334824: logrotate: Postrotate documentation - Why restart?

2005-10-20 Thread Kai Hendry
On 2005-10-21T00:49+0100 Paul Martin wrote: > On Thu, Oct 20, 2005 at 12:04:24PM +1000, Kai Hendry wrote: > > I don't understand why there is a need to restart the server in a > > postrotate using apache2 as an example. > > Could you or rather docs explain this better? :) > > I noticed this on RH

About php-mysql error

2005-10-20 Thread Nevruz Mesut Sahin
  Hello   Our company is an e-commerce company. The customers enter the web side and and chose products and buy them by credit card.   Tecnical definition:   order.php sends the customer_name amount and credit_cardno ccno  to xbank_xml.php and xbank_xml.php sends to xbank these variables and  wri

Re: conf.d or sites-enabled?

2005-10-20 Thread Adam Conrad
Faheem Mitha wrote: > > I have no current plans to use Virtual Hosts, so I was wondering if > there would be any downside to moving the stuff in > sites-enables/default to conf.d, which seems like the obvious place > for it to go. There's no real downside to moving the file anywhere you want, as

conf.d or sites-enabled?

2005-10-20 Thread Faheem Mitha
Hi, I was configuring apache (which I have little knowledge of) and I noticed some of the basic configuration is in sites-enabled/default. I have no current plans to use Virtual Hosts, so I was wondering if there would be any downside to moving the stuff in sites-enables/default to conf.d, which