woehlkmp
Posts: 102
Status: offline
|
Except for syslogd (which, it turns out, was not running - and sshd doesn't seem to care), so far there aren't really any daemons I care about... and 'man syslogd' says "-s Run as a service", which to me implies that it was intended to work as a Windows service (does it need to be run as Administrator, I wonder, or is LocalSystem OK?).
Because it shouldn't hurt anything, I changed the dependencies to sshd:>syslogd:>"User Name Mapping" to (hopefully!) make sure things start in the correct order.
I'd love to know why init.d is broken, but honestly I have no idea where to start investigating. As for sshd, however, I'd prefer it to run as a service anyway, so as long as it keeps working, I'm happy .
|