On Tuesday 04 May 2004 13:47, Magnus Hagander wrote:
> > I played a bit with that code. According to Microsoft samples
> > for service managers, errors and events should be logged to
> > eventlog. so I added a function (almost copy of sample
> > service code), it's a messy, but it was enough to see
> I played a bit with that code. According to Microsoft samples
> for service managers, errors and events should be logged to
> eventlog. so I added a function (almost copy of sample
> service code), it's a messy, but it was enough to see what is
> happening with the service.
Consider using e
How can we detect this situation and send the postmaster
error string into log ?
Here is changed "main.c" that I played with.
Regards !
- Original Message -
From: "Claudio Natoli" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, May 03, 2004 12:01
> Spoke about this off-list with Magnus; he's strongly for
> stand-alone; I'm fence-sitting. We see that clearly there are
> some niceties to having this in the postmaster (one less exe
> to build/configure; same install set for win/*nix; etc), but
> the downsides include minor impact on the co
[For review only. Not for committing.]
Decided to take a crack at this in the interests of knocking over the
remaining TODO win32 items asap.
Would appreciate any comments on the code, particularly from win32 people.
An obvious missing feature is allowing the service to be registered under a
use
