On Wed, 2004-08-18 at 05:02, garry wrote:
> On Wednesday 18 Aug 2004 03:13, Jim McQuillan wrote:
> > Gary,
> >
> > I think you've got 2 different, unrelated problems:
> >
> > 1) The syslogd error is more of a warning. You need to configure
> >your syslogd to allow remote clients to send their
On Wed, 2004-08-18 at 17:02, garry wrote:
> Thanks I've sorted it now. I thought I could just copy the LTSP tree from one
> server to another and it would work -wrong!
You should be able to, assuming you copy it in a way that preserves
permissions, symlinks, etc. `cp -aR` should do the trick, as
On Wednesday 18 Aug 2004 03:13, Jim McQuillan wrote:
> Gary,
>
> I think you've got 2 different, unrelated problems:
>
> 1) The syslogd error is more of a warning. You need to configure
>your syslogd to allow remote clients to send their log messages.
>There are various ways to do this, de
Gary,
I think you've got 2 different, unrelated problems:
1) The syslogd error is more of a warning. You need to configure
your syslogd to allow remote clients to send their log messages.
There are various ways to do this, depending on your distro.
It's a '-r' option to syslogd that all
I'm sending this again because it did not seem to be delivered earlier, sorry
if anyone gets duplicates.
I am trying to get 4.1 up and running and have run into the following two
error messages on the workstation:
Syslogd cannot write to file handle on 10.35.180.231:514
fatal server error
