la, 2009-08-29 kello 12:19 +0200, Xavier Brochard kirjoitti:
Le vendredi 28 août 2009 11:06:47, Veli-Matti Lintu a écrit :
After nothing else seemed to work, I started debugging the crashes using
kernel serial console and finally got some results. As this is probably
something that also
ti, 2009-09-01 kello 13:32 -0500, Scott Balneaves kirjoitti:
On Fri, Aug 28, 2009 at 12:06:47PM +0300, Veli-Matti Lintu wrote:
After nothing else seemed to work, I started debugging the crashes using
kernel serial console and finally got some results. As this is probably
something that
- Original Message -
From: Gavin McCullagh gmccull...@gmail.com
To: ltsp-discuss@lists.sourceforge.net
Sent: Tuesday, September 01, 2009 2:18 PM
Subject: Re: [Ltsp-discuss] Problems with a new Dual Core Login
Hi,
On Tue, 01 Sep 2009, Gavin McCullagh wrote:
As a start, I suggest
Hi,
On Wed, 02 Sep 2009, Keith wrote:
Thanks Gavin - I have done what you suggested and below follows the result:
Did you get any clues from the verbose boot screen? Does it stick with a
certain message showing? The tcpdump will be much easier to understand
along with that. In particular,
debian lenny's ltsp server and clients
I defined a screen for rdesktop and one for ldm.
The problem is that when rdesktop timeouts (because the user login at
ldm), it exist and xinit restarts the X server with a new rdesktop, so
the user has to find his workplace (screen) by pressing
Yeah, I have been meaning to get the wrapper into upstream for some time
now. As I am one of the few devs to care for the rdesktop side of the
house, I must say I have not had the chance to push a wrapper upstream.
Personally, instead of calling all the external things like dirname
and basename,
Check the networking in the VM.
For example, change to: SCREEN_07=shell
and make sure that the client can ping the hostname you are trying. If
not, check pinging the IP. A network issue would explain both the
failed login and the rdesktop screen failing to appear.
-Gadi
On Tue, 2009-09-01 at
On Tue, Sep 1, 2009 at 06:42, Keith ke...@gsps.co.za wrote:
Hi there,
We run an Ubuntu 8.10 (kubuntu) - LTSP 5 lab with 26 clients. The Server is
a Geniune server (Intel S5000VSA) with 8GB RAM (we never exceed 4GB). It is
a Quad core machine with 10/100/1000 onboard LAN outlet. The Clients
Bingo. No name resolution from the shell. I used an IP address for the
RDP target and I'm in business.
Not that I need name resolution, since I can do static IPs for my
terminal servers, but why would the tc not get DNS info? My dhcp
server is Win Server 2008 and DNS server are set in option 6.
On Wed, 2009-09-02 at 10:02 -0600, David Burgess wrote:
Bingo. No name resolution from the shell. I used an IP address for the
RDP target and I'm in business.
Not that I need name resolution, since I can do static IPs for my
terminal servers, but why would the tc not get DNS info? My dhcp
Further research has narrowed this 8.04.2 problem down to
hyper-threading combined with NBD_SWAP. Turning off NBD_SWAP for these
clients 'solved' the problem, even when leaving hyper-threading on.
This may sound crazy but try disabling one of the cores if you can. I
ran across a similar
This might seem odd, but try setting:
SOUND=False
in your lts.conf.
By default, LTSP runs pulseaudio on startup, which hogs the audio
device. You either need to add a pkill pulseaudio to the rdesktop
screen script, or make rdesktop use pulseaudio, or, as with SOUND=False,
instruct LTSP not to
No joy. I tried both methods. Although 'ps aux | grep -i pulse'
doesn't show in the shell, still no sound from the rdp session.
Any other ideas?
db
On Wed, Sep 2, 2009 at 3:21 PM, Gideon Romml...@symbio-technologies.com wrote:
This might seem odd, but try setting:
SOUND=False
in your
In the shell, run alsamixer
if it works, turn the volume way up.
if it doesn't, you probably don't have the soundcard driver for the
soundcard. check: lsmod|grep snd
Do you know what soundcard it has?
also, rdesktop should be: -r sound:local
-Gadi
On Wed, 2009-09-02 at 16:09 -0600, David
r...@ltsp371:~# alsamixer
ALSA lib pulse.c:272:(pulse_connect) PulseAudio: Unable to connect:
Connection refused
alsamixer: function snd_ctl_open failed for default: Connection refused
r...@ltsp371:~# ps aux | grep -i pulse
root 8474 0.0 0.2 2076 576 pts/0S+ 16:28 0:00 grep
Is all this with SOUND=False in lts.conf?
The error that you get with alsamixer suggests that the pulse soundcard
is set as the default soundcard- which is odd (and the source of your
problem).
Well, if all else fails, instead of killing pulseaudio, you can work
with it and add:
export
I am trying to write a script that shut down the (given set of) thin
clients (TC). Therefore, I have installed openssh-server in ltsp-chroot,
and I am able to ssh to a TC from the server and shut the TC down.
So, what should such a script look like? Or is there a better, more
appropriate
I tried three things:
1. lts.conf: SOUND=False
2. lts.conf: SOUND=False + screen.d/rdesktop: pkill pulseaudio
3. screen.d/rdesktop: pkill pulseaudio
I got no sound on all three efforts, and pulse didn't show up in ps
-aux on any of those three scenarios. I ran alsamixer and got the
error on the
Oh, and I'll try your other suggestions tomorrow. Thanks for the help.
db
On Wed, Sep 2, 2009 at 5:13 PM, David Burgessapt@gmail.com wrote:
I tried three things:
1. lts.conf: SOUND=False
2. lts.conf: SOUND=False + screen.d/rdesktop: pkill pulseaudio
3. screen.d/rdesktop: pkill pulseaudio
Hi,
I wrote this little howto - hopefully it'll be of some help, though it
doesn't require SSHing into the boxes, rather it shuts systems down at a
certain time via cron:
https://help.ubuntu.com/community/UbuntuLTSP/AutomatedTCShutodwn
A simple for loop would probably do the trick if you have
heh, leave it to me to mess up a simple script ;)
---
#!/bin/bash
HOSTS=123.123.123.123 456.456.456.456 etc. etc.
for i in $HOSTS; do
ssh r...@$i halt
done
---
Jordan Erickson wrote:
Hi,
I wrote this little howto - hopefully it'll be of some help, though it
doesn't require SSHing
On Thu, 2009-09-03 at 00:54 +0200, SZABO Zsolt wrote:
I am trying to write a script that shut down the (given set of) thin
clients (TC). Therefore, I have installed openssh-server in ltsp-chroot,
and I am able to ssh to a TC from the server and shut the TC down.
So, what should such a
Hi,
did you tried to use -r sound ..
RDP_OPTIONS=-dGPRC -z -a24 -P -f -0 -r sound:local -u userid
instead of -rsound
RDP_OPTIONS=-dGPRC -z -a24 -P -f -0 -rsound:local -u userid
cu frank
apt@gmail.com 02.09.2009
Hi, it's me again.
Thanks to good help from the list so far I
23 matches
Mail list logo
