On Redhat (most versions) its:
/etc/sysconfig/syslog. You've got to add the -r to SYSLOGD_OPTIONS
SYSLOGD_OPTIONS="-r -m 0"
hth
Greg
Anselm Martin Hoffmeister schreef op 15-12-04 14:06:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Mittwoch, 15. Dezember 2004 14:43 schrieb Maxim
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Mittwoch, 15. Dezember 2004 14:43 schrieb Maximilian Ebert:
> hi list,
>
> what das this means:
>
> Syslogd: cannot write to remote file handle on192.168.0.254:514
You need to configure syslog to allow messages from other hosts to appear in
your s
hi list,
what das this means:
Syslogd: cannot write to remote file handle on192.168.0.254:514
thx max
---
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which prod
Am Mittwoch, 23. Juni 2004 01:27 schrieb Abraham Pearson:
> > Hi Abraham,
> >
> > thanks for your answer!
> >
> > >This means that your syslog server is not listening. Tell
> >
> > it to listen.
> >
> >
> > How can I tell the syslog server to listen?
>
> I don't remember off the top of my head. I
> Hi Abraham,
>
> thanks for your answer!
>
> >This means that your syslog server is not listening. Tell
> it to listen.
> >
> >
> How can I tell the syslog server to listen?
I don't remember off the top of my head. If I remember I will tell you. Maybe
someone else can help here.
> >It t
> Hi folks,
>
> I've just installed LTSP 4.0 and everything seems to work fine.
> Now I'm tuning the client but I got an error I can't solve:
> When I delete in the lts.conf file the line:
> SCREEN_01 = startx
> "syslogd: cannot write to remote file handle on192.168.83.201:514"
>
This means that
Hi folks,
I've just installed LTSP 4.0 and everything seems to work fine.
Now I'm tuning the client but I got an error I can't solve:
When I delete in the lts.conf file the line:
SCREEN_01 = startx
during the boot the client hangs on the error:
"syslogd: cannot write to remote file handle on192.168
On Fri, 18 Jul 2003, Kurt Neufeld wrote:
>
> This may be old news but since I couldn't find while googling I figured I'd
> mention it just in case.
>
> First time out of the gate ltsp hung on when trying to load syslogd. On
> your host/server you have to run syslogd with the -r option to allow
This may be old news but since I couldn't find while googling I figured I'd
mention it just in case.
First time out of the gate ltsp hung on when trying to load syslogd. On
your host/server you have to run syslogd with the -r option to allow remote
machines to log locally.
Or remove -R {SYSLOG
