[users@httpd] Re: Re: Does Apache Support Piped Logs On Windows Platform

[Yoann Roman <yr...@altalang.com>]

William A. Rowe, Jr. wrote:
> Yoann Roman wrote:
> > William A. Rowe, Jr. wrote:
> >>
> >> Then it became 'run this shell command through cmd.exe' - which needed
> >> stdin/out/err all set up right to not-fail running as-a-service.
> >>
> >> Change it back from shellcmd to program and voila, the code works.  We
> >> hacked at various handle codes for stdout/stderr, but nothing except
> >> a legitimate file stream will make cmd.exe happy.
> >>
> >> So Apache just dies with a message that it fails to create the log.
> > 
> > Was this problem ever resolved in 2.2.9?
> 
> Yes, the behavior I describe above, with apr 1.2, should have been
resolved
> with 2.2.9 and apr 1.3.0.

I played with it some more, and I did finally get it to work. I think a
combination of running the service as a restricted user and not restarting
between reinstalls got things out of whack.

> > I'm trying to set up 2.2.9 as a service on an XP SP2 box with either
> > rotatelog or cronolog for main and vhost error/access logs, but I see
> > several cmd.exe processes when starting it up. I have a W2K box with
2.0.63
> > that doesn't have this shell behavior (also a service using cronolog).
> 
> Oh - it still runs cmd.exe.  The difference is - there are the correct
> pipes between apache and that cmd/invoked program/script.

That's what I'm trying to avoid, actually. I have 2 vhosts with this
install, each doing its own error and access logging. With the 2 processes
per log (not sure why that happens, either) plus cmd.exe, that adds up to 20
processes for 5 logs.

Along with resource concerns, I also run Apache as a restricted user, which
doesn't have access to cmd.exe (similarly to how the IIS user doesn't have
access). I'd prefer keeping it that way, but I can't do so if the log piping
requires it.

> > I also skimmed through the SVN logs for log.c and didn't see anything
about
> > fixing this.
> 
> No, these are all subdependencies, you wouldn't note them from log.c

I was actually looking for implementation of the additional piping options
discussed in the dev list exchange I mentioned. I'm basically trying to get
the same behavior with 2.2.9 on XP that I'm seeing on 2.0.63 on W2K (no
cmd.exe).

Thanks,

-- 
Yoann Roman


---------------------------------------------------------------------
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@httpd.apache.org
   "   from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org

Re: [users@httpd] Re: Re: Does Apache Support Piped Logs On Windows Platform

["William A. Rowe, Jr." <wr...@rowe-clan.net>]

Yoann Roman wrote:
> William A. Rowe, Jr. wrote:
>> Oh - it still runs cmd.exe.  The difference is - there are the correct
>> pipes between apache and that cmd/invoked program/script.
> 
> That's what I'm trying to avoid, actually. I have 2 vhosts with this
> install, each doing its own error and access logging. With the 2 processes
> per log (not sure why that happens, either) plus cmd.exe, that adds up to 20
> processes for 5 logs.
> 
> I was actually looking for implementation of the additional piping options
> discussed in the dev list exchange I mentioned. I'm basically trying to get
> the same behavior with 2.2.9 on XP that I'm seeing on 2.0.63 on W2K (no
> cmd.exe).

After this was "broken" across all platforms, I raised on this list a
suggestion for a new syntax; for example "||... would mean a command line
shell environment (really "pipe"), while "|$..." would mean really exec.
That was the idea, anyways, we should be revisiting it.  Realize this isn't
Win32 specific, but it's an issue across platforms.


---------------------------------------------------------------------
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@httpd.apache.org
   "   from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org