> >>> I thought that output to stderr generally goes into the
> bit bucket
> >>> in Windows.
>
> > It is never ignored. WHen running as a service, you will
> only see it
> > if ou check the box "allow service to interact with
> desktop", and this
> > can only be done on Local System services (thus not
> postgresql) So in
> > this case, the end effect will be that you can't see it.
> But you will
> > most definitly see it when running it from the commandline
> (say, when
> > you are debugging why it won't start..)
>
> I guess the important question is whether it is possible to
> redirect stderr into a file on Windows. If not, I'd say the
> output-to-stderr option is pretty useless on that platform.
> I certainly don't want critical messages sent to stderr with
> no possibility of capture.
It is. From the commandline, not from a service. (You could do it from a
service wrapper, I think, but somebody reported problems with that
earlier)
//Magnus
---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
