🚀 go-pugleaf

Remy Lebeau (TeamB) wrote

> > I have a service which I installed on the real
> > server (NT4). It worked as I expected about 5
> > minutes, till it was stopped suddenly by OS.
>
> When that happened, there should have been entries
> placed into the NT Event Log to explain why the OS
> decided to do that.

I haven't remembered the NT Event Log. I'll check that
at monday. I'll also supply intensive LOG entries from my
code and then I'll check when exactly that happens.

At the first time I installed the service it workd about half an
hour before the OS termination - and it worked well.

As I said, on my XP it worked well.

I guess that some concurent file access must be the reason. I
prevented my code from that by Critical Sections, but still
there are some files which are also accessed by other (not
mine) services, so possibly I should supply some retries.

Is there some benefits of using 'open' insted of 'fopen' for
accessing files for reading?

Is there any particular need to add some try-catch-finally
in the OnExecute() { while (!Terminated){} }loop of the
service?




Best regards,
Vladimir Stefanovic