Re: Apache 2.2, rotatelogs.exe, and Windows

["Mark A. Craig" <mark.a.craig@xxxxxxxxx>]

Philip, do you use a scheduled CMD file to gracefully kill the server, rotate 
the logs, and then restart the server?  Given that rumor has it that piping is 
broken in 2.2.4, it seems something like that is the only way to do it right 
now, eh?  If what you're using contains no trade secrets, I'd be very curious to 
see exactly what you're using, so I can use it as boilerplate for my own 
solution.  I wonder if it could also be accomplished via a WSH file instead, and 
whether that would provide extra flexibility or benefits?

Mark

-------- Original Message  --------
Subject: Re:  Apache 2.2, rotatelogs.exe, and Windows
From: Phillip Hamilton <phillip@xxxxxxxxxxxxx>
To: users@xxxxxxxxxxxxxxxx
Date: Tuesday, September 18, 2007 11:50:08 AM

> I wholeheartedly disagree with this statement:
> Apache holds only a tiny share of 
> Windows servers.
>
> Apache holds a very large share of Windows server market, hence the
> pre-made binary. 
>
> Back on topic, I rotate via a bat file with a quick re-start on my windows
> boxes ;)
>
> -----Original Message-----
> From: Dragon [mailto:dragon@xxxxxxxxxxxxxxxxxx] 
> Sent: Tuesday, September 18, 2007 1:02 PM
> To: users@xxxxxxxxxxxxxxxx
> Subject: Re:  Apache 2.2, rotatelogs.exe, and Windows
>
> Mark A. Craig wrote:
> > So this leads me to ask again, what are all of you successful 2.2.4 
> > admins using to rotate your logs?  If the piping mechanism is 
> > broken, at least in the Windows binary, then what other technique(s) 
> > are people using?  Task Scheduler with a batch or CMD file?
> >
> > So far I've been manually rotating the logs, but I'd understandably 
> > like to automate it.
> ---------------- End original message. ---------------------
>
> I think you will find that the vast majority of people using Apache 
> are not doing so on the Windows platform. Most people who have 
> committed to the Windows platform have also committed to IIS. Apache 
> dominates the Linux environment and is used frequently on BSD and 
> similar Unix-based platforms. Apache holds only a tiny share of 
> Windows servers.
>
> I believe that those few who are using Apache on Windows tend to be 
> hobbyists or developers using it to serve their own stuff or to do 
> development off-line. I am willing to bet there are very few people 
> using it in a production environment under Windows.
>
> So it is entirely possible that there may be nobody on this list who 
> has an answer for you. The set of people using it in the same manner 
> you are is small to begin with and there may not be many of them 
> subscribed to this list.
>
> Repeatedly posting demanding
>
> Dragon
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>   Venimus, Saltavimus, Bibimus (et naribus canium capti sumus)
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
>
> ---------------------------------------------------------------------
> The official User-To-User support forum of the Apache HTTP Server Project.
> See <URL:http://httpd.apache.org/userslist.html> for more info.
> To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
>    "   from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx
> For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
>
>
>
> ---------------------------------------------------------------------
> The official User-To-User support forum of the Apache HTTP Server Project.
> See <URL:http://httpd.apache.org/userslist.html> for more info.
> To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
>    "   from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx
> For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx

---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
  "   from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx