scottmaccal has joined IRC (scottmaccal!~scottmacc@pool-71-173-93-142.ptldme.east.myfairpoint.net)

00:18

<markit>

funny, alkis was fighting with a similar bug some year ago

00:18

https://bugs.launchpad.net/ubuntu/+source/ltsp/+bug/173067

00:18

This bug fixed in ubuntu hardy

00:19

or maybe mine is a brand new one, lol

00:19

<bakytn>

markit, I have ubuntu 11.04 64bit

00:19

<markit>

me kubuntu 64 bit, and ltsp chroot at 32 bit

00:22

in chroot /etc/default/keyboard has wrong values

00:22

wondering if I build the chroot before setting locales of the host, but I dubt

00:27

andygraybeals has joined IRC (andygraybeals!~andy@h143.204.213.151.dynamic.ip.windstream.net)

00:29

<bakytn>

still wondering why the clietns are so slooooow within my cluster network. tcpdump is showing that LDM_DIRECTX is set to True and only on login packets are encrypted

00:30

loather-work has joined IRC (loather-work!~khudson@68.25.27.54)

00:33

<markit>

bakytn: do you have a gbit switch and 100mb clients?

00:34

<bakytn>

markit, yes but it works much much faster on a standalone server

00:34

markit, on the same network

00:35

markit, I have virtual machines so I could compare by shutting down one and turning another on etc.

00:35

<markit>

bakytn: can't find my notes about it, but there is a feature in some switch about collisions

00:36

that in some circustamces, like the above, can make it act so dumb that is like a 10MB one

00:36

<bakytn>

markit but 10Mb is still very enough to work smoothly

00:36

markit in a local network

00:37

markit, with only one client.

00:38

<markit>

oh, I see

00:38

<bakytn>

soemthing is wrong with my setup.

00:39

<nroussi>

bakytn: ifconfig on the client show lo and eth0 of the client. the server btw is an ldap client and the home directories are on another nfs server. Ldap login and nfs mounts work on the clients but not internet

00:40

<markit>

bakytn: what about using tshark and check with visual filters for errors like: tcp.analysis.retransmission or tcp.analysis.out_of_order or tcp.analysis.duplicate_ack_frame or tcp.analysis.lost_segment

00:43

<pmatulis>

by default i'm getting extended screen mode with my 2 monitors on my client. how to get mirror mode by default?

computer_freak_8 classic-gnome: To set classic-gnome as the default session instead of Unity in Ubuntu >= 11.04, put LDM_XSESSION="gnome-session --session=classic-gnome" in lts.conf.

03:37

<computer_freak_8>

!classic-gnome

03:37

<ltsp>

computer_freak_8: classic-gnome: To set classic-gnome as the default session instead of Unity in Ubuntu >= 11.04, put LDM_XSESSION="gnome-session --session=classic-gnome" in lts.conf.

03:38

<computer_freak_8>

ha, yeah, I was a bit slow on the re-type

03:38

now I don't have to keep scrolling :)

03:43

So, I'm working on the auto-login, but I noticed something: if I use the remote-login feature (XDMCP), it does the auto-login sequence exactly as I have told it to. However, when the LTSP client boots, it goes to the LTSP login screen.

03:44

I don't know if this is a configuration goof, or if that is normal.

03:45

<alkisg>

computer_freak_8: XDMCP is a protocol to connect to a remote X display server, unrelated to autologin and ltsp

03:45

Autologin in LTSP only works with the LDM display manager

03:46

<computer_freak_8>

Okay.... so maybe I need to transfer that (working) config from my server "main" to my server's chroot?

03:46

<alkisg>

I think you should start with saying what you want to do

03:47

<computer_freak_8>

get the autologin working, but have it be easily configurable.

03:47

<alkisg>

autologin is already working, did you read the lts.conf man page about the configuration variables?

03:47

It just needs 3 lines in lts.conf

03:47

!lts.conf

03:47

<ltsp>

alkisg: lts.conf: http://manpages.ubuntu.com/lts.conf.

03:47

<computer_freak_8>

Yeah, it didn't work.

03:47

<alkisg>

Paste your current lts.conf then

03:47

<computer_freak_8>

let me try again, though

03:48

<alkisg>

LDM_AUTOLOGIN, LDM_USERNAME, LDM_PASSWORDS

03:48

*without the S

03:48

You just need to set those 3 variables

03:50

<computer_freak_8>

Nope, didn't work

03:50

<alkisg>

(06:47:58 πμ) alkisg: Paste your current lts.conf then

03:50

Put xxx in place of the password

03:51

<computer_freak_8>

Eh, I'm just using a test password: http://pastebin.com/8bYn44qV

03:51

that's the actual password for the user "guest", but I'll change it once I get it all working.

03:51

<alkisg>

And if you try to login on LDM with guest/test, it works?

03:52

<computer_freak_8>

username "guest"/password "pass"

03:52

<alkisg>

guest/pass

03:52

<computer_freak_8>

yeah, it logs in

03:52

<alkisg>

OK, once it logs in, run: ltsp-localapps xterm

03:52

Did an xterm open?

03:54

<computer_freak_8>

I hit [Alt]+[F2] to bring up that prompt, but yes, it does.

03:54

<alkisg>

In that xterm, run: getltscfg -a

03:54

<computer_freak_8>

"guest@ltsp196~$"

03:54

<alkisg>

Do you see LDM_USERNAME/LDM_PASSWORD etc in the output?

03:54

<computer_freak_8>

okay, it spit back:

03:54

no, I don't....

03:55

it has two lines:

03:55

<alkisg>

On your server, ls /var/lib/tftpboot/ltsp/i386/lts.conf

03:55

<computer_freak_8>

LTSP_CONFIG=True

03:55

<alkisg>

Ah

03:55

<computer_freak_8>

and export LTSP_CONFIG

03:55

<alkisg>

You're the one that uses debian and switched to nbd by mistake, right?

03:55

<computer_freak_8>

wait, it has double-quotes around the "True"

03:55

yup!

03:55

<alkisg>

Debian uses nfs, and /opt/ltsp/i386/etc/lts.conf by default

03:56

<computer_freak_8>

okay.

03:56

<alkisg>

Since you switched to nbd, you shouldn't use that file

03:56

<computer_freak_8>

Oh!

03:56

<alkisg>

Because every time you change it, you also need to run ltsp-update-image, which takes a lot of time

03:56

<computer_freak_8>

oh....

03:56

<alkisg>

So with nbd, lts.conf was moved to /var/lib/tftpboot/ltsp/i386/lts.conf

03:56

Just copy your lts.conf there

03:56

<computer_freak_8>

is there an easy way to switch back to NFS?

03:57

<alkisg>

Not sure about all that's needed, if you see vagrantc around here ask him

03:57

<computer_freak_8>

Ah, okay.

03:57

<alkisg>

You may have to change a couple of configuration files for bind_mounts etc

03:57

<computer_freak_8>

oh, okay.

03:58

<alkisg>

For now it's not a big deal, just use /var/lib/tftpboot/ltsp/i386/lts.conf

03:58

<computer_freak_8>

Does the /var/lib/tftpboot/ltsp directory basically mirror the /srv/tftp/ltsp directory?

03:58

<alkisg>

You only need one of those, delete the other

03:59

There's a transitional period from /var/lib/tftpboot to /srv/tftp where both of them are supported

03:59

<computer_freak_8>

I only modify the /srv/tftp directory contents, but it auto-propagates to the /var/lib/tftpboot directory (somehow...)

03:59

<alkisg>

No, don't do that

03:59

Just delete one of the 2

03:59

<computer_freak_8>

okay.

04:00

<alkisg>

It makes no sense to have to update both of them

04:00

<computer_freak_8>

I'll delete the /var/lib/tftpboot one then..

04:00

<alkisg>

Yup, completely rm -rf it

04:00

<computer_freak_8>

and put my configuration at /srv/tftp/ltsp/i386/lts.conf, then?

04:00

<alkisg>

Yes

04:00

Also you may need to update your tftp server

04:00

So that it points to /srv/tftp

04:01

Probably /etc/default/tftpd-hpa

04:01

<computer_freak_8>

yeah, it already does

04:02

is NFS or NBD better for low-RAM capacity thin (diskless) clients, or does it matter?

04:03

<alkisg>

The main pros/cons:

04:03

Compressed NBD is maybe 5 times faster. That mostly affects boot time, localapps and fat clients

04:04

<computer_freak_8>

Oh, okay

04:04

<alkisg>

And, with NFS, you don't need to run ltsp-update-image every time you change /opt/ltsp/i386/*

04:04

<computer_freak_8>

which is nice

04:04

<alkisg>

Select which of the above is more significant for you...

04:04

<computer_freak_8>

is one being depreciated? or just newer?

04:04

I prefer NFS in that case

04:04

<alkisg>

None. Debian defaults to NFS, while Ubuntu to NBD, mainly for the boot speed

04:05

<computer_freak_8>

oh, okay

04:05

<alkisg>

E.g. if one only updates his chroot every few months, why not have that extra speed

04:05

<computer_freak_8>

true.

04:05

<alkisg>

But while setting up a chroot, ltsp-update-image is a pain in the *

04:05

<computer_freak_8>

I'm always changing things

04:06

comes in handy to have it ready right away

04:07

wait, is this correct? Or do I need to bump it down a directory, into an "etc" sub-directory? sudo cp -a /opt/ltsp/i386/etc/lts.conf /srv/tftp/ltsp/i38

04:07

6/

04:07

<alkisg>

No etc

04:07

<computer_freak_8>

okay. cool

04:09

Is there an easy way to keep ltsp-update-image from messing up my /srv/tftp/ltsp/i386/pxelinux.cfg/default file?

04:09

Sweet, autologin works - and I didn't even have to run the ltsp-update-image!

04:09

<alkisg>

It shouldn't be touching it unless you specify the --force option

04:09

<computer_freak_8>

Thanks.

04:09

hm, odd.

04:10

<alkisg>

If it does, I'd consider it a bug...

04:10

<computer_freak_8>

each time I have run it so far, it replaces it - and I have to fix it.

04:10

<alkisg>

cat /opt/ltsp/i386/boot/pxelinux.cfg/default

04:10

Maybe it calls ltsp-update-kernels, which copy that file

04:11

In that case, you can either run ltsp-update-image --force, which updates both files, or just edit that file too

04:11

<computer_freak_8>

could be - one has :

04:11

label ltsp

04:11

kernel vmlinuz

04:11

append ro initrd=initrd.img

04:11

and the other:

04:11

label ltsp

04:11

kernel ltsp/i386/vmlinuz

04:11

append ro initrd=ltsp/i386/initrd.img

04:11

(that's not the whole thing - just the changed parts)

04:11

it must think my root is different?

04:13

(the real location is in the "ltsp/i386/" directory - it always strips that part, though)

04:14

But hey, auto-login works, so thanks again - I'm all set until I break it again!

04:14

<alkisg>

:D

04:28

chokesmaster has joined IRC (chokesmaster!~chokesmas@bas5-sherbrooke40-2925525063.dsl.bell.ca)

hi, I have some problem with dhcp in ltsp: this is a mixed network with clients that boot from pxe, the others not. The problem is with these last ones: they could not connect to the internet. Any clue? Please...

08:13

I would like to ensure that the ltsp server become a simple network gateway for the non pxe booters.

alkisg: hi again, I am checking. I found finally on a french forum the steps to configure italc and updated the ubuntu help page too with it.

08:41

<alkisg>

Thanks, I hope people can follow the new page :)

08:43

We should make a bonus system, every person updating a wiki page would be entitled to one good answer in irc :P :D

08:44

<Hyperbyte>

reuss_, the 'other non-pxe clients'... are those Linux machines as well, or Windows?

08:46

<reuss_>

hyperbyte: both

08:46

hyperbyte: for now, it is a linux client

08:46

<Hyperbyte>

Okay

08:46

Run 'ifconfig' and 'ip route show' on the Linux client that can't connect to the internet, and pastebin those

08:46

!pastebin | echo reuss_

08:46

<ltsp>

reuss_ pastebin: the LTSP pastebin is at http://ltsp.pastebin.com. Please paste all text longer than a line or two to the pastebin, as it helps to reduce traffic in the channel. Don't forget to paste the URL of the text here..

08:48

<reuss_>

hyperbyte, ltsp: it would be difficult without a connection, but I am trying to connect it from the server by ssh

08:49

<Hyperbyte>

ifconfig > debuginfo.txt

08:49

ip route show >> debuginfo.txt

08:49

scp debuginfo.txt user@ltspserver

08:49

That'll copy the file to a user's home directory on the LTSp server

08:58

<reuss_>

hyperbyte: I copied it, but I cant see it on the server...

08:58

<Hyperbyte>

Sorry

08:59

You need a colon after that

08:59

scp debuginfo.txt user@ltspserver:

08:59

<reuss_>

hyperbyte: I copied it, but I cant see it on the server...

08:59

<Hyperbyte>

scp debuginfo.txt user@ltspserver: <-- notice the colon, the :

08:59

Without the : it copies the file locally, like 'cp' would.

09:00

<reuss_>

hyperbyte: I got it

09:00

<Hyperbyte>

:)

09:01

<reuss_>

hyperbyte: here is: http://paste.ubuntu.com/673644/

09:01

<Hyperbyte>

And you said your main router is 192.168.1.111 ?

09:02

<reuss_>

hyperbyte: yes, but the ltsp server hides it

09:02

<Hyperbyte>

What is 192.168.0.1 ?

09:02

<reuss_>

hyperbyte: the ltsp server dhcp offers addresses on 192.168.0.0

09:03

hyperbyte: nothing

09:04

<Hyperbyte>

And you are 100% sure your LTSP clients -can- connect to the internet?

09:04

Or do you mean the applications running on the server, displayed on the thin client, can connect to the internet? :-)

09:05

Because if that's the case, your thin clients in fact can not connect to the internet, and you'll need to follow the howto that Alkis posted a bit earlier.

09:06

Thin clients by default run everything on the server. If you start Firefox on a thin client, it doesn't actually run on the client, it runs on the server. So it's the server that's connecting to the internet, not the clients. The clients probably can't access the internet themselves, you'd need to set up NAT for that.

09:07

<reuss_>

hyperbyte: booting as thin client with pxe, I can connect to internet, the chroot environment could too, only this fat client without pxe could not

09:07

<Hyperbyte>

Okay

09:07

<reuss_>

hyperbyte: I am checking the doc and will report its success (if any). thanks

09:07

<Hyperbyte>

Boot a thin client, and start a local xterm

09:07

!localxterm

09:07

<ltsp>

Hyperbyte: localxterm: while sitting on a thin client, open a gnome terminal. In that, run: ltsp-localapps xterm. An xterm will open. That xterm runs locally, so any commands you enter there are executed directly on the client..

400 MB ram isn't a lot, but should be able to handle Firefox. Dunno about Gimp.

11:00

<alkisg>

How is "400 MB RAM" possible? 256+128+16 ?

11:01

<reuss_>

alkisg: 400 something mb, with shared video ram maybe from 512

11:01

<alkisg>

Which graphics card? It matter for youtube etc...

11:01

<reuss_>

alkisg: mostly integrated nvidias from 5 years ago

11:02

<alkisg>

That's pretty good then, if you enable the proprietary driver

11:02

Then yeah, firefox+flash locally would be better than from the server

11:03

<reuss_>

alkisg: thanks, I will implement it then. from the server, it was sometimes quite slow (but a lot better then a non maintened windows xp)

11:04

<alkisg>

You need to install the proprietary driver in the chroot, and enable it on selected clients from lts.conf

11:05

Also enable and increase nbd_swap (or some local swap partition, if your clients have local disks)

11:05

Otherwise you'll probably get firefox crashes, too little ram

11:05

Parker955 is now known as Parker955_Away

11:08

<reuss_>

alkisg: If i have firefox installed both in chroot and server and local_apps_menu enabled on ltsp.conf and I dont want anymore the clients to run from clients, I remove at chroot and that is all?

11:09

s/to run/to run firefox

11:09

alkisg: s/to run/to run firefox

11:09

<alkisg>

You can also just remove it from lts.conf

11:09

But yeah, that's about it

11:10

If you want, it's easy to keep a backup from your whole /opt/ltsp directory...

11:10

sudo rsync -a /opt/ltsp /opt/ltsp-before-trying-localapps

11:11

<reuss_>

alkisg: after every installation, I should run tsp-update-image ?

11:12

<Hyperbyte>

reuss_, modifications to /opt/ltsp/ only apply after running ltsp-update-image

11:12

<alkisg>

!learn ltsp-update-image as If you use NBD (e.g. Ubuntu), every time you change something in your chroot (e.g. /opt/ltsp/i386), you need to run ltsp-update-image and reboot the thin clients for the changes to take effect

11:12

<ltsp>

alkisg: The operation succeeded.

11:13

<Hyperbyte>

!<3

11:13

<ltsp>

Hyperbyte: <3: alkisg.

11:13

<alkisg>

:)

11:13

<reuss_>

alkisg: thanks

11:19

<alkisg>

!echo $NICK

11:19

<ltsp>

alkisg

11:19

<alkisg>

!echo $USER

11:19

<ltsp>

~alkisg

11:19

<alkisg>

Yeah NICK is better

11:19

<Hyperbyte>

!whosyourdaddy

11:19

<ltsp>

Hyperbyte: whosyourdaddy: You are, Hyperbyte.

11:19

<alkisg>

Hmm now we should put it in some factoid to scare users

11:20

<muppis>

:)

11:20

<alkisg>

!forget ltsp-update-image

11:20

<ltsp>

alkisg: The operation succeeded.

11:20

<alkisg>

!learn ltsp-update-image as Dear $NICK, try to understand: if you use NBD (e.g. Ubuntu), every time you change something in your chroot (e.g. /opt/ltsp/i386), you need to run ltsp-update-image and reboot the thin clients for the changes to take effect

11:20

<ltsp>

alkisg: The operation succeeded.

11:20

<alkisg>

!ltsp-update-image

11:20

<ltsp>

alkisg: ltsp-update-image: Dear alkisg, try to understand: if you use NBD (e.g. Ubuntu), every time you change something in your chroot (e.g. /opt/ltsp/i386), you need to run ltsp-update-image and reboot the thin clients for the changes to take effect.

11:20

<Hyperbyte>

You should still hack it to remove the 'nickname:' from that...

11:20

Right now it does $NICK: $key: $value

11:20

<alkisg>

Needs a bit of work, yeah, but it'll prove to be fun :D

11:20

<Hyperbyte>

The $NICK: part should really go...

11:21

<alkisg>

Where is that? In which variable?

11:21

<Hyperbyte>

I have no idea

11:21

<muppis>

alkisg, boring day?

11:21

<Hyperbyte>

I mean in the message

11:21

Haha

11:21

I'm gonna have some lunch.

11:21

<alkisg>

muppis: I'm trying hard to avoid starting to work on my phd :D

11:22

Hyperbyte: I got it, I meant in which bot configuration variable

11:33

<Hyperbyte>

No idea. :)

11:45

GodFather has joined IRC (GodFather!~androirc@223.sub-174-252-246.myvzw.com)

shawnp0wers has joined IRC (shawnp0wers!~Adium@linuxjournal/staff/shawnp0wers)

12:37

[GuS] has joined IRC ([GuS]!~MysT@213-117-16-190.fibertel.com.ar)

12:37

[GuS] has joined IRC ([GuS]!~MysT@unaffiliated/gus/x-663402)

12:42

<mgariepy>

Hyperbyte, i'm sorry to hear that it's not working.

12:47

<Hyperbyte>

:)

12:47

Went to the printing settings and disabled transparency, but still complete freezeup.

12:55

<mgariepy>

when this option is disable here, the memory usage on my thin clients is not moving a bit when printing.

12:55

you checked Reduce transparency and no transparency ?

12:57

<Hyperbyte>

Yep.

12:57

Even tried all the other options as well (reduce dpi, etc)

13:01

Parker955 is now known as Parker955_Away

13:01

<mgariepy>

kk

13:02

Parker955_Away is now known as Parker955

13:19

Parker955 is now known as Parker955_Away

13:26

Parker955_Away is now known as Parker955

13:26

<nroussi>

Hi, I have a problem with my installation. I have a Fat Client image on a server with 2 NICs. The server is an LDAP client and has a folder mounted with NFS for all the users. The clients boot fine, the users log in, the home directory mounts but there is no internet. I followed all NAT guides found on the edubuntu howtos and still nothing.

tl1000s77 has joined IRC (tl1000s77!~tl1000s77@173-13-114-113-NewEngland.hfc.comcastbusiness.net)

14:09

<nroussi>

yes

14:09

Hyperbyte: it is a router only for the LTSP subnet

14:10

<tl1000s77>

Quick question, I'm trying to get sound working on my thin client (Ubuntu 10.04 ) using rdesktop and the -r sound:local command but it's not working. Should I install ltspfs on the thin client or is that only for local devices?

14:12

<Gadi>

tl1000s77: what version of windows

14:12

(and no to the ltspfs question)

14:12

<tl1000s77>

Server 2008 R2

14:12

<Gadi>

and audio mapping is enabled on the server?

14:12

<tl1000s77>

I get sound using rdesktop from my desktop and that's running ubuntu 10.10

14:13

Yes

14:13

<Gadi>

are you running ldm and rdesktop on 2 different screens?

14:13

<tl1000s77>

No

14:13

I'm using the SCREEN_07 = rdesktop

14:14

<Gadi>

try setting SOUND=False in lts.conf - this will, in effect, disable pulseaudio and volume adjustment, but alsa sound will still work

14:14

it could be that sound via pulseaudio on the client is not working

14:15

<tl1000s77>

I have tried that, can I show you my lts.conf file?

14:16

<Hyperbyte>

nroussi, type 'ifconfig' and 'ip route show' on the client, then put the output on pastebin.

14:17

<Gadi>

tl1000s77: sure

14:17

tl1000s77: also, get a shell on another screen (say, screen2)

14:18

that way, you can debug some things on the client

14:23

<tl1000s77>

Gadi: I also wanted to ask you about the XRANDR variable, it doesn't seem to call --addmode anywhere.

14:25

http://pastebin.com/ysG9GPCh

14:27

anivair has joined IRC (anivair!~joe@69.58.115.123)

14:38

<nroussi>

Hyperbyte: this is the output http://pastebin.com/Za3Fx2Hu thanks

14:38

ry has joined IRC (ry!~ry@static-71-183-64-28.nycmny.fios.verizon.net)

14:38

<Hyperbyte>

I assume you trimmed the ifconfig output?

14:39

<Gadi>

tl1000s77: ok, first, I would take out the -u ''

14:39

<tl1000s77>

k

14:39

<shawnp0wers>

Anyone that is using Edubuntu 11.04, how to I get ldm to use the classic gnome desktop and not unity?

Gadi: it made more sense to me this way, I didn't like having to specify half of the command line... either no command line (RDP_OPTIONS, RDP_SERVER etc), or full command line

15:01

And, omitting "-f" and "-u" wasn't anywhere on the docs

15:02

...erm, and rdesktop, RDP_OPTIONS etc too :P

15:02

<Gadi>

nothing but excuses

15:02

:)

15:02

* alkisg admits he only has lame excuses to offer

15:02

<Gadi>

think of all the poor people who just added one or two params

15:02

and upgrade to find that root wants to now login!

15:02

<alkisg>

But I heard that good excuses make up for poor code quality :D

15:03

<Gadi>

you should add -f -u '' to the COMMAND line

15:03

rdesktop will override them with later params

15:03

ie, -u '' -u foo brings up the user foo

15:04

<shawnp0wers>

Gadi: Ok, I haven't shat a brick quite yet, but I'm close. The REMOTE_APPS directive is working for 11.04. However, it doesn't work for .doc attachments. Is there a way to configure mime types for ltsp-open ?

15:04

<alkisg>

Gadi, but why modify the default rdesktop command line anyway?

15:04

<Gadi>

shawnp0wers: ltsp-open calls xdg-open on the server

15:04

so, if you associate it on the server, it should work

15:05

<shawnp0wers>

That's strange, on the server a quick double-click opens them fine...

15:05

<tl1000s77>

I now have a small xterm window

15:05

Parker955 is now known as Parker955_Away

15:05

<tl1000s77>

but it's only a bash

15:05

shell

15:05

<shawnp0wers>

Perhaps I should clarify — firefox doesn't even try to open .doc attachments with ltsp-open

15:05

<Gadi>

tl1000s77: right

15:05

tl1000s77: perfect

15:05

first, try playing a sound with aplay

15:06

(say, some wav file in /usr/share/sounds/)

15:06

<tl1000s77>

I get sound with aplay

15:06

<Gadi>

tl1000s77: ok, now run rdesktop -r sound:local -u '' 10.1.1.10

15:07

<tl1000s77>

no sound :(

15:08

<alkisg>

nroussi: you tell the clients that your gateway is 192.168.0.1 while it's 192.168.0.254. Your server is the gateway to your clients.

shogunx has joined IRC (shogunx!~shogunx@rrcs-67-79-182-235.se.biz.rr.com)

16:44

<tl1000s77>

There's only one card listed, Intel ICH5 with AD1981B at irq 17

16:55

shawnp0wers has joined IRC (shawnp0wers!~Adium@linuxjournal/staff/shawnp0wers)

16:56

<bakytn>

I have cluster environment and LDM_DIRECTX is set to True (tested with tcpdump). But clients are not very responsive! On the same network the clients on a standalone server works faster. WHat could be the reason?