Alfredo,
the syslog message is NOT causing the problem.
It's only a warning that it couldn't write to the server syslog.
You can fix that, by modifying the servers syslogd configuration, to
include a '-r' when starting syslog This varies depending on the
distro.
BUT, this is NOT what is causing
Hi:
Using SuSE 8.2 and LTSP 4.1.
My clients get as far as this error:
rc.sysinit completed, switching to multi-session mode
syslogd: cannot write to remote file handle on XX.XX.XX.XX:514
And then it hangs. The docs do not mention this error, and a search in Google
mentions the problem, but off
On Friday 22 March 2002 09:36 pm, Skip Gaede wrote:
> Folks,
>
> I've shot myself in the foot, and am hoping someone knows the remedy. My
> LTSP server is also a router, and I'm running Mandrake 8.2. I ran
> InteractiveBastille to setup security, and it changed the permissions on
> the log files s
Folks,
I've shot myself in the foot, and am hoping someone knows the remedy. My LTSP
server is also a router, and I'm running Mandrake 8.2. I ran
InteractiveBastille to setup security, and it changed the permissions on the
log files so that root is the only one with write access. Now my client
