Hi people,
I tried to boot up my notebook using its PXE with LTSP on SuSE 9.1. The
notebook boot up ok and I can login and show me the KDE screen. Basically I am
ready to use the notebook as I expect. The booting up is also very fast
Hoever, I have problem with the keyboard that those letter
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
Hi Peter,
that was the solution:
Peter Billson schrieb:
Eilert,
Firewall rules are applied in order. So you need to add a rule
*before* your blocking rule that says:
iptables -A OUTPUT -d 127.0.0.0/24 -J ACCEPT
It is -j instead of -J, but now it's running as expected. Thanks!
Rolf
---
On Wed, 17 Nov 2004, Tom Allison wrote:
> Oh dear...
> They've added so many formats and it's been so many years since I looked
> at this stuff.
>
> I was planning on putting a boot disk onto the /dev/hda device of these
> workstations and leaving it at that. But there seems to be a lot more
You need to Setup NIS,
I was facing the same problem some time ago.
Read the NIS/NIS+ How to..www.linuxdoc.org/HOWTO/NIS-HOWTO.html
and go according. make there are some ssh issues also.
There is a link which will help you to do
that.http://www.ltsp.org/ltsp-4.html#localapps
I also did xhost +
Eilert,
Firewall rules are applied in order. So you need to add a rule
*before* your blocking rule that says:
iptables -A OUTPUT -d 127.0.0.0/24 -J ACCEPT
This will allow all localhost traffic, regardless of the owner.
Pete
--
http://www.elbnet.com
ELB Internet Service, Inc.
Web Design, Compu
On Thursday 18 Nov 2004 11:25 am, Jesus Maria Vicente Saz wrote:
>
> # ssh thinhost2 env DISPLAY=192.168.1.2:0.0 netscape
>
> I connect to the machine but I can't authenticate. It's as if it can't
> find the user and password.
I've just been through the trauma of NIS. My notes may be of some ass
Hi all,
I'm building a network based on LTSP. At the moment, everything works
perfectly, but the large number of Thinstations that there
are (approx. 40), the CPU load on the server is very high.
Because of this I've decided to execute the heavier applications (OpenOffice
and Netscape) directly
On Wed, 17 Nov 2004 [EMAIL PROTECTED] wrote:
> Hi Peter
>
> > So I thought I would get lbe up and running to get the the bottom
> > of the problem and also to try and take some load off the server... Also
> > people don't like the textual boot procedure so I thought I might be able
> > to cu
Moin Anselm,
the situation is worse than that :-(
Anselm Martin Hoffmeister schrieb:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Mittwoch, 17. November 2004 08:32 schrieb Eilert:
There's only one drawback: all students must be logged in when applying
the barrier as for some unknown reason, no
11 matches
Mail list logo
