Kern Sibbald wrote:
> On Tuesday 17 May 2005 11:37, Russell Howe wrote:
>>Removing the key certainly 
>>stops the warning messages being logged when users log in via terminal
>>services.
> 
> Well, this is a big surprise.  If this is all that it takes to correct the 
> problem, first it is easy enough to publish, and second, I'll be very happy 
> to remove the old code.

I think it may well be that easy, yes. That said, this isn't causing any
problems, it just logs a warning message in the logs whenever anyone
logs into a Windows machine via terminal services (i.e. remotely), so it
seems pretty harmless. It's just not Right(tm) though :)

>>* The commandline option parsing sees the following two options as
>>identical:
>>
>>      foo
>>      foobar
> 
> This was on purpose to allow shorter versions of the command line options. 
> Probably it was a bad idea.

I'm not sure that allowing abbreviated commandline options is all that
useful - especially on Windows, where it is rare to be typing them in
manually, and things tend to be scripted someplace.

>>Had the latter not been the case, I suspect bacula-fd.exe would simply
>>have terminated as soon as it had been called with /servicehelper, with
>>an error to the effect that it didn't know what '/servicehelper' meant.
>>Instead, it took it to mean /service and tried to register itself with
>>the service helper (which MS says an application started from the
>>console cannot do).
> 
> Could you explain to me why and when Bacula would be called from that 
> ServiceHelper key?  Also, what is a Service helper?  I don't *really need to 
> know these things, but it might help me feeling a bit more at ease about 
> removing it ...

/servicehelper is the command line option passed to bacula-fd.exe. I
don't know what it was intended for, but it doesn't seem to even be
checked for any more. Due to the above command line parsing behaviour,
/servicehelper is interpreted as /service.

RunServices is the name of the registry key located at:

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\RunServices

It is much like the 'Run' key in the same location, but I think that
programs listed here are started before logon (whereas entries under
'Run' are started at logon time).

On NT-based OSes, I suppose the service controller is the preferred
(only?) way to start service-type applications, so the RunServices key
is only really appropriate for Win95/98/ME.

Please don't trust what I say though, I'm no expert in the Windows
startup process - all the above is based on observation & user-level
experience rather than hard documentation.

-- 
Russell Howe
[EMAIL PROTECTED]

Today's Nemi: http://www.metro.co.uk/img/pix/nemi_may17.jpg


-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to