IRC chat logs for #ltsp on irc.freenode.net (webchat)


Channel log from 20 April 2011   (all times are UTC)

00:14gnunux (~emmanuel@194.167.18.244) joined #ltsp.
00:16dobber (~dobber@89.190.197.77) joined #ltsp.
01:15toscalix (~toscalix@77.208.114.137) joined #ltsp.
01:26toscalix (~toscalix@77.208.114.137) left irc: Read error: Connection reset by peer
01:51gentgeen__ (~kevin@c-98-236-71-64.hsd1.pa.comcast.net) left irc: Read error: Operation timed out
02:07wwx (~ww@raamat.polva.ee) left irc: Read error: Connection reset by peer
02:08wwx (~ww@raamat.polva.ee) joined #ltsp.
02:19wwx (~ww@raamat.polva.ee) left irc: Read error: Connection reset by peer
02:20wwx (~ww@raamat.polva.ee) joined #ltsp.
02:49dobber (~dobber@89.190.197.77) left irc: Remote host closed the connection
02:49dobber (~dobber@89.190.197.77) joined #ltsp.
02:51Trixboxer (~Trixboxer@office.supportdepartment.net) joined #ltsp.
04:25dead_root (~dead_root@76.75.3.174) joined #ltsp.
04:54Da-Geek (~Da-Geek@nat/redhat/x-lwtqwduydhcynrrz) joined #ltsp.
05:17gentgeen__ (~kevin@c-98-236-71-64.hsd1.pa.comcast.net) joined #ltsp.
05:20brunolambert (~brunolamb@2001:470:8829:1000:221:6aff:fe94:21d8) joined #ltsp.
05:28
<Hyperbyte>
Ah, es muy bueno!
05:33brunolambert (~brunolamb@2001:470:8829:1000:221:6aff:fe94:21d8) left irc: Quit: brunolambert
05:35brunolambert (~brunolamb@2001:470:8829:1000:221:6aff:fe94:21d8) joined #ltsp.
05:36brunolambert (brunolamb@2001:470:8829:1000:221:6aff:fe94:21d8) left #ltsp.
05:36brunolambert (~brunolamb@2001:470:8829:1000:221:6aff:fe94:21d8) joined #ltsp.
05:36brunolambert (~brunolamb@2001:470:8829:1000:221:6aff:fe94:21d8) left irc: Remote host closed the connection
05:37brunolambert (~brunolamb@2001:470:8829:1000:221:6aff:fe94:21d8) joined #ltsp.
06:26
06:29vmlintu (~vmlintu@nblzone-240-143.nblnetworks.fi) joined #ltsp.
06:31drdata (~drdata@tw2.udallas.edu) joined #ltsp.
06:32GodFather (~rcc@173.10.34.145) joined #ltsp.
06:35drdata (drdata@tw2.udallas.edu) left #ltsp.
06:47gentgeen__ (~kevin@c-98-236-71-64.hsd1.pa.comcast.net) left irc: Ping timeout: 258 seconds
06:54gentgeen__ (~kevin@c-98-236-71-64.hsd1.pa.comcast.net) joined #ltsp.
07:25litlebuda (~litlebuda@144.178.108.93.rev.vodafone.pt) joined #ltsp.
07:38vagrantc (~vagrant@c-24-21-191-93.hsd1.or.comcast.net) joined #ltsp.
07:56patrickmw (~pwright@ip68-231-4-153.ph.ph.cox.net) joined #ltsp.
08:15primeministerp (~ppouliot@64.119.153.82) joined #ltsp.
08:27vmlintu (~vmlintu@nblzone-240-143.nblnetworks.fi) left irc: Remote host closed the connection
08:38Da-Geek (~Da-Geek@nat/redhat/x-lwtqwduydhcynrrz) left irc: Quit: Leaving
08:42chupacabra (~chupacabr@cpe-70-112-10-45.austin.res.rr.com) left irc: Quit: WeeChat 0.3.3
08:42gnunux (~emmanuel@194.167.18.244) left irc: Quit: Ex-Chat
08:53dobber (~dobber@89.190.197.77) left irc: Remote host closed the connection
08:55Roasted (~jason@206.82.22.190) joined #ltsp.
09:03Roasted (~jason@206.82.22.190) left irc: Remote host closed the connection
09:08chupacabra (~chupacabr@cpe-70-112-10-45.austin.res.rr.com) joined #ltsp.
09:14litlebuda (~litlebuda@144.178.108.93.rev.vodafone.pt) left irc: Quit: Saindo
09:15litlebuda (~litlebuda@144.178.108.93.rev.vodafone.pt) joined #ltsp.
09:15litlebuda (~litlebuda@144.178.108.93.rev.vodafone.pt) left irc: Client Quit
09:18GodFather (~rcc@173.10.34.145) left irc: Quit: Ex-Chat
09:29toscalix (~toscalix@77.208.114.137) joined #ltsp.
09:29garymc (~garymc@81.138.225.161) joined #ltsp.
09:30
<garymc>
Hi im looking at thin client manager in my ubuntu Ltsp GUI and it shows no thin clients connected. I know there are several connected. what could be wrong here?
09:30
<vagrantc>
what's wrong is thin client manager is unmaintained and broken for several years
09:31
<garymc>
ahhh ok
09:31
so its not something I have done
09:32
<vagrantc>
at best, it won't break anything, at worst, it can break your LTSP
09:33
<garymc>
i was wondering why my thin clients are really slow at using the intranet on the server?
09:33
i have a web based customer database on the LTSP server and all thin clients seem very slow using it
09:34
but if I use a computer that isnt on the LTSP or isnt a thin client it works fine
09:42mistik1 (mistik1@unaffiliated/mistik1) left irc: Read error: Connection reset by peer
09:42mistik1 (mistik1@unaffiliated/mistik1) joined #ltsp.
09:45irule (~irule@187.139.25.77) joined #ltsp.
09:48zamba (marius@flage.org) left irc: Remote host closed the connection
09:50zamba (marius@flage.org) joined #ltsp.
09:53zamba (marius@flage.org) left irc: Remote host closed the connection
09:55zamba (marius@flage.org) joined #ltsp.
09:57_UsUrPeR_ (~jsass@fw.acurrus.com) left irc: Ping timeout: 264 seconds
09:57dyllan (~dyllan@unaffiliated/kingmilo) joined #ltsp.
09:57
<dyllan>
hi guys
09:57
<abeehc>
hello
09:58
<dyllan>
Does LTSP 5 have trouble displaying high resolution on widescreen monitors? I have a widescreen and the highest resolution is 1024x768, can this be increased? - thakns
09:59
<abeehc>
no it doesn't have trouble.. you can troubleshoot that as if it were simply a ubuntu problem i'd say
10:00litlebuda (~litlebuda@144.178.108.93.rev.vodafone.pt) joined #ltsp.
10:00
<abeehc>
err
10:00
what distro?
10:00
in any case i think your video chipset is one of the most important parts
10:00
oh and the monitor heh
10:00garymc (~garymc@81.138.225.161) left irc: Quit: ChatZilla 0.9.86 [Firefox 3.6.16/20110323162424]
10:00
<dyllan>
ubuntu, using an intel video card
10:01
do I have to configure lts.conf file? i am seeing quite a lot of that when googling for my problem.. .
10:03
<abeehc>
if your video chipset was working perfectly you shouldn't have to tell lts.conf much if anything in my experience
10:03
worth a try though there's a number of things in lts_parameters.txt you should look at
10:04
<dyllan>
thing is, if i install the exact same version of ubuntu onto the "thin client" the resolution works fine, so im a bit stumped
10:04
<abeehc>
ahh interesting i gotcha
10:04
that's a good test
10:04
have you unlocked your thinclient chroot and root account?
10:04
I'd be wondering what video driver the thin client ends up using
10:05
cause you can override that in lts.conf; you should find the driver differs from the local install to what the thinclient boots and uses i guess
10:06
<dyllan>
im not quite sure how to get into the thin client root account, i can switch to the console with F1 but no idea what user/pass to use there. If i am on the server and # chroot /etc/ltsp/i386 then i get / but there are no log files, what am i missing?
10:06
<abeehc>
sec
10:06
<dyllan>
ty
10:06
<abeehc>
https://help.ubuntu.com/community/UbuntuLTSP/UnlockChrootRootAcct
10:07
i personally always also do openssh-server so i don't have to walk so much
10:08
<dyllan>
haha, yes i already have ssh daemon running ill checkout the tut thnx
10:11
<abeehc>
i mean to say i do openssh-server in the chroot so the clients also listen via ssh
10:11
<dyllan>
I should also mention than the server is 64-bit and client i386 to i have to --arch i386
10:12
<abeehc>
yeah you'll want to adjust that tutorial to your needs for sure
10:12
i think that's probly all you have to specify
10:12
with ltsp-update-image part anyway
10:13
<dyllan>
ok so i followed the link, doesnt that mean now i should change to console on the thin client ctrl-alt-f1 then at the prompt root & password?
10:13
i dont think i have quite grasped the whole setup yet!
10:13
<abeehc>
you need to do the two or three steps there; then you need to let ltsp-update-image complete, then you need to reboot the client
10:14
if that helps'?
10:14
<dyllan>
ahh reboot ok
10:14
that's probably what i was missing
10:14
<abeehc>
:>
10:14
<dyllan>
:)
10:14
<abeehc>
if you logout i think ldm will detect you have a new image waiting
10:14
and the client will decide to reboot itself
10:14
<dyllan>
it does, smart :)
10:16
<abeehc>
afkback in a couplefew
10:17
<dyllan>
k ty for ur help
10:17vagrantc (~vagrant@c-24-21-191-93.hsd1.or.comcast.net) left irc: Quit: leaving
10:38litlebuda (~litlebuda@144.178.108.93.rev.vodafone.pt) left irc: Read error: Operation timed out
10:41
<abeehc>
i guess lts_parameters.txt is dead now; man lts.conf is the way to go, once ltsp-docs is installed
10:44
could anyone say if NFS_HOME accepts something like server2:/home or is that non-sensible
10:46
<dyllan>
abeehc, just fyi the problem was that i had a converter from vga to dvi and that was causing the issue.
10:46
Straight DVI cable worked!
10:46
<abeehc>
ah excellent stuff
10:46
<dyllan>
yup im stoked!
10:46
<abeehc>
that makes sense; vga can't carry very high resolutions
10:46vmlintu (~vmlintu@nblzone-240-143.nblnetworks.fi) joined #ltsp.
10:47
<dyllan>
yea. how many users do you think ltsp and my hardware can manage before it gets slugish?
10:47
Im running an IBM x3550 M3 with 8GB at the moment. Option to upgrade to 16GB RAM.
10:48
My thin clients are very powerful for thin clients, 1GB RAM, 1.6 Intel Atom CPU
10:48
<abeehc>
it's of course, always tough to say/estimate but in my experience as just stright thin clients, you could handle like 30 or 40.. at least i have lesser hardware with half that ram that does just fine with 20 clients
10:49
thin clients like that you should be running fat clients i'd say
10:49
<dyllan>
ok, but at least I can get an idea then
10:49
<abeehc>
I'm in the process of getting somewhere near fat clients
10:49
takes much processing off the server
10:49
<dyllan>
abeehc, ya i tried to set up the solution in that way but i just couldnt get it working nicely, spent 3 days on it, and 3 hours on ltsp and got it working A OK
10:50
<abeehc>
well I do mean ltsp fat clients
10:50
i'm not sure if that
10:50
's what you mean
10:50
<dyllan>
hmm, so you mean that with the current configuration I can make a couple changes and have the thin client do some of the work?
10:50
ie. i dont have to do a complete reinstall and setup a completely different solution
10:50
<abeehc>
yeah there's a couple approaches to do so; local apps, or fat clients
10:51
both place processing on client
10:51
a lot of people do local apps for firefox cause flash sucks so much
10:51
<dyllan>
ok nice, yup flash is sux ;)
10:51
ok ill google local apps and see what i can come up with
10:51
<abeehc>
your server likely won't be starved in any case but I'm finding flash lags a bit anyway if it's not local.. i don't mean flash, i mean youtube videos
10:52
i think the only place to be is the ubuntu ltsp page man, https://help.ubuntu.com/community/UbuntuLTSP
10:52
<dyllan>
what i used to do is install a firefox plugin that disables flash by default so there is a PLAY button on the flash content and if you really want to see it then just click lay.
10:52
<abeehc>
fat clients are noted there; i guess this stuff is kinda new compared to local apps
10:52
<dyllan>
play*
10:52
<abeehc>
ah yeah I considered that too, good call;
10:52
<dyllan>
but i must say that flash is running 100% at the moment, but im only 1 user
10:53
<abeehc>
yeah, these options are normally only explored when your server starts complaining
10:53
<dyllan>
exactly
10:53
<abeehc>
but also your clients are so powerful it might also be worth while
10:54
<dyllan>
i agree. Going to start moving as much people as I can across then watch top and see how it handles the load then take it from there, but the users will moan quickly if there is an issue im sure of that ;)
10:55
i love the fact that with ltsp i can plugin a usb devices and it shows up on the desktop and sound works!
10:55
<abeehc>
it is great. lts.conf also offers a lot of flexibiility
10:56
<dyllan>
in what way? Enabling/Disabling devices & sound?
10:56
<abeehc>
if you haven't come across it, you might look at LDM_DIRECTX=True
10:56
yeah enable devices per thin client or allow specific users on specific thinclients or auto-login on a specific thin client
10:56
combined with a flexible dhcp server you can do almost anything i figure
10:56brunolambert (~brunolamb@2001:470:8829:1000:221:6aff:fe94:21d8) left irc: Quit: brunolambert
10:57brunolambert (~brunolamb@2001:470:8829:1000:221:6aff:fe94:21d8) joined #ltsp.
10:57
<dyllan>
nice, so using MAC address ip assign then manage the peripherals via lts.conf
10:57brunolambert (~brunolamb@2001:470:8829:1000:221:6aff:fe94:21d8) left irc: Client Quit
10:57
<dyllan>
a quick google it seems that LDM_DIRECTX provides for a faster user desktop?
10:57
<abeehc>
yeah well actually the only time dhcp comes into play I guess is if your service different images to different clients;
10:58
you can use mac addresses directly in lts.conf instead of setting static ips elsewhere
10:58
yeah, that's right, most people go with LDM_DIRECTX i think; but keep in mind it has security considerations
10:58
<dyllan>
ahh nice, thanks for the tip
10:59
<abeehc>
in that the server no longer encrypts the client traffic, that's where the speed comes from
10:59
so if your network's safe it's not a real worry I beleive
10:59
<dyllan>
Hmm, I think that would suit me!
10:59
excellent tips here, i should visit more often haha
11:02
our current solution is XDMCP with gentoo and kde 4.3, so connection via the XDMCP protocol get your desktop login and voila. But with the hardware much better these days it makes sense to make use of ltsp
11:02brunolambert (~brunolamb@gw-sherb.rlnx.com) joined #ltsp.
11:26toscalix (~toscalix@77.208.114.137) left irc: Read error: Operation timed out
11:27toscalix (~toscalix@77.208.114.137) joined #ltsp.
11:32toscalix (~toscalix@77.208.114.137) left irc: Remote host closed the connection
11:41alkisg (~alkisg@ubuntu/member/alkisg) joined #ltsp.
11:42dyllan (~dyllan@unaffiliated/kingmilo) left irc: Quit: Leaving
11:50
<dberkholz>
eek, xdmcp.
11:51* alkisg likes XDMCP :)
11:51
<highvoltage>
the nice thing about xdmcp was that all the populer display managers knew about it
11:51
*popular
11:52
<alkisg>
And they still do, even lightdm supports it
11:53
<highvoltage>
gdm doesn't
11:53
(well not anymore)
11:53
<alkisg>
Sure does
11:53
In Lucid it had problems connecting 2 times in a row, I filed a bug about it, it was solved, all work fine now
12:12
<highvoltage>
ah, ok
12:19drdata (~drdata@tw2.udallas.edu) joined #ltsp.
12:19drdata (drdata@tw2.udallas.edu) left #ltsp.
12:19Nick change: vvinet -> veloutin
12:28alkisg (~alkisg@ubuntu/member/alkisg) left irc: Quit: Leaving.
12:28Trixboxer (~Trixboxer@office.supportdepartment.net) left irc: Quit: "Achievement is not the end, its the beginning of new journey !!!"
12:34alkisg (~alkisg@ubuntu/member/alkisg) joined #ltsp.
13:00
<highvoltage>
http://www.engadget.com/2011/04/20/chinese-robotic-triceratops-skeleton-packs-linux-no-horns
13:07dead_root (~dead_root@76.75.3.174) left irc: Ping timeout: 252 seconds
13:23Lns (~Lns@pdpc/supporter/professional/lns) joined #ltsp.
13:42chupacabra (~chupacabr@cpe-70-112-10-45.austin.res.rr.com) left irc: Ping timeout: 258 seconds
14:08mgariepy (~mgariepy@ubuntu/member/mgariepy) left irc: Quit: Leaving
14:14
<kusznir>
Hi all: I recently started having a problem on my network such that when my thin clients reboot, they get dhcp and tftp info, and start booting. Then, when ubuntu on the thin clients starts to boot, it ends up scrolling "DHCP NAK" for its IP, which is the same IP it just had for booting.
14:14Roasted (~jason@unaffiliated/roasted) joined #ltsp.
14:15
<kusznir>
My DHCP is served up by pfSense (as it does more than just thin clients). I realize this isn't directly an LTSP problem, but I also have no idea what would cause a DHCP NAK like that on an IP its already received from the DHCP server unless there's some other paramater that is changing. I've reproduced this on two different thin clients.
14:19brunolambert (~brunolamb@gw-sherb.rlnx.com) left irc: Quit: brunolambert
14:27
<alkisg>
kusznir: distro/version?
14:29
Ah you said "ubuntu", is that 10.04 ?
14:32
<kusznir>
alkisg, ltsp server is actually still 9.10
14:33
<alkisg>
kusznir: and the chroot?
14:33
<kusznir>
Working on newer...but that's a back burner project, which I rarely have time to work on.
14:33
Same for chroot.
14:33
<alkisg>
If I remember correctly, karmic uses udhcpc to get a lease by default
14:33
And that udhcpc is 5 years old and has some bugs
14:33
<kusznir>
That's correct, the error messages all said udhcpc
14:34
<alkisg>
One of them is related to the "client identifier"
14:34
<kusznir>
Ok.
14:34
<alkisg>
In short, the PXE dhcp requests sends one client identifier, and then udhcp sends another
14:34
So your router thinks they're 2 different clients, and refuses the second lease
14:35
<kusznir>
Strange thing was that it *did* work before I upgraded pfsense, but I haven't gotten a response from ##pfsense people yet, and investigation of settings and logs don't show anything useful.
14:35
<alkisg>
No need to look there
14:35
<kusznir>
Ok. The logs show only the mac address identifier, and they are identical (nothing appended).
14:35
<alkisg>
The problem exists in cisco routers too, in windows dhcp servers, etc etc
14:35
<kusznir>
Ok. So is there a fix to the chroot that can fix this?
14:35
<alkisg>
Yes
14:35
<kusznir>
cool.'
14:35
how?
14:35Ahmuck (~quietly@p178n22.ruraltel.net) left irc: Ping timeout: 240 seconds
14:36Ahmuck (~quietly@p178n22.ruraltel.net) joined #ltsp.
14:36
<alkisg>
Either get a newer udhcpc version, or modify the script that calls udhcp to not send a client identifier
14:36
The second is probably faster
14:36
https://bugs.launchpad.net/ubuntu/+source/ltsp/+bug/505916
14:37
<kusznir>
Hmm.../scripts/* doesn't exist...
14:37
<alkisg>
/opt/ltsp/i386/usr/share/initramfs-tools/scripts/init-premount/udhcp
14:37
<kusznir>
ahh...ok.
14:37
I take it I need to rebuild the initramfs then too? (I've not done that on ubuntu before)
14:38
<alkisg>
if udhcpc -n -c "$clientid" -s /tmp/dhcp-script.sh -i $i $hostname_param $ip_param >/dev/null 2>&1; then
14:38
==> you need to remove "-c $clientid" there
14:38
See comment #15 on the above bug report
14:39
<kusznir>
Hmm.. I have: if udhcpc -n -c '' -s /tmp/dhcp-script.sh -i $i $clientid_param $hostname_param $ip_param > /dev/null; then
14:39
so its already blank...or is that part of the problem?
14:40
<alkisg>
It is
14:40
Remove the: -c ''
14:40
<kusznir>
Ok. I should keep the $clientied_param before the $hostname_param, right?
14:40
ahh, yeas, I see that on the website, sorry.
14:42
Ok, going to test now :)
14:43
<alkisg>
Notice that there's no need to run ltsp-update-image
14:43
<kusznir>
Yep, thanks! That worked well.
14:44
Speaking of ltsp-update-image, is there any fix for all thin clients crashing after rebooting the ltsp server?
14:45
(even if the image isn't updated)
14:56chupacabra (~chupacabr@cpe-70-112-10-45.austin.res.rr.com) joined #ltsp.
15:05
<alkisg>
kusznir: if the clients are on the login screen, yes. But if they're logged on, then no, their processes die.
15:09
<kusznir>
Yea. The issue is that their clients are on the login screen when I reboot the server (overnight, for example). When they come in and try and log in, the login screen dissappears, and goes to a black screen scrolling buches of I/O errors, block errors,a nd the like. It keeps going until they pull power and restart the thin client.
15:10
<abeehc>
i run into that pretty often as well
15:11
<kusznir>
I fully expect their login sessions to dissapear. And I would be understanding of a thin client crashing if it was doing something when the server went down. But I don't get it if they're idle and the server reboots with no changes to the image, when it comes back up, it should just work again.
15:14gothaggis (~gothaggis@corp.heavyhammer.com) joined #ltsp.
15:14
<kusznir>
they're == the thin clients (with nobody logged in)
15:15
<alkisg>
nbd-client has a --persist option which should make this case work
15:15
I think you'd also have to remove nbd-proxy, if it's there in karmic
15:15
<gothaggis>
hello, I seem to be having a problem setting up a new LTSP server - I'm using Ubuntu 10.04 and a windows server for DHCP. When I power on a new client, it gets an IP address but then says PXE-E11 ARP timeout PXE-E38 TFTP cannot open connection. what am I doing wrong?
15:15
<kusznir>
alkisg, will these problems dissappear when I upgrade to a newer version of ubuntu for the chroot?
15:16
<gothaggis>
I followed the steps setting up this new LTSP server the same way I setup a server running on an older version of Ubuntu (8) - so not sure if something has changed with 10.04 or perhaps I skipped a step
15:16
<alkisg>
kusznir: lucid and maverick use nbd-proxy by default, so no, I don't think so. I think nbd-proxy was disabled by default in Natty, but I haven't tried it yet, and I don't know if -persist was again added to nbd-client.
15:17
gothaggis: if it's a tftp problem, try this first: https://help.ubuntu.com/community/UbuntuLTSP/Troubleshooting/TFTP
15:17
<kusznir>
I was shooting for natty for my rebuild.
15:18
<alkisg>
I think -persist is still missing there
15:19
revno: 879
15:19
branch nick: ltsp-trunk
15:19
timestamp: Sat 2008-10-04 17:21:51 -0400
15:19
message: Start nbd-client with -persist so it reconnects in case of nbd-server crash (needs nbd-client 2.9)
15:19
Later on though it was dropped. Don't know why.
15:19
<kusznir>
Ok. Where does that get added/set?
15:20
<alkisg>
In ltsp_nbd, near the other file you changed
15:20
(a dir up)
15:24
<kusznir>
alkisg, thanks. Updated. We'll see how that goes next time I have a maintenance reboot...
15:25
<alkisg>
kusznir: after that, whatever problems remain are nbd-client problems, to be reported in its bug tracker
15:25
<gothaggis>
alkisg, i followed all the steps on the TFTP troubleshooting page and everything seems ok - but clients still won't boot. the one thing is, I'm using a windows server for DHCP so I don't have the dhcpd.conf file.
15:25
<alkisg>
gothaggis: did you also do the gpxe step?
15:26
(btw, if you need help on configuring your windows server, it's there: https://help.ubuntu.com/community/UbuntuLTSP/LTSPWindowsDHCP)
15:26
<gothaggis>
I think I found the problem, I think the windows DHCP is still pointing to the old server
15:27
<alkisg>
Could be. gPXE is handy in those cases, as you can see from the client side the DHCP parameters.
15:45
<gothaggis>
alkisg, thanks - that was exactly the issue, everything is working great now
15:45
<alkisg>
Nice. Goodnight all.
15:45alkisg (~alkisg@ubuntu/member/alkisg) left irc: Quit: Leaving.
16:12Lumiere (~jstraw@pool-72-83-232-11.washdc.fios.verizon.net) left irc: Ping timeout: 260 seconds
17:30veloutin (~vince@2001:470:8829:1000:227:eff:fe25:ee64) left irc: Read error: Operation timed out
17:30Lumiere (~jstraw@pool-72-83-232-11.washdc.fios.verizon.net) joined #ltsp.
17:39cliebow (~cliebow@66.63.66.218) joined #ltsp.
17:43veloutin (~vvinet@2001:470:8829:1000:227:eff:fe25:ee64) joined #ltsp.
17:56vagrantc (~vagrant@75-150-46-245-Oregon.hfc.comcastbusiness.net) joined #ltsp.
18:03alexqwesa (~alex@alexo-veto.broker.freenet6.net) left irc: Ping timeout: 264 seconds
18:16MorningSon (~MorningSo@cpe-66-25-84-220.satx.res.rr.com) joined #ltsp.
18:21irule (~irule@187.139.25.77) left irc: Ping timeout: 240 seconds
18:57davidj (~david@cpe-069-132-209-125.carolina.res.rr.com) joined #ltsp.
19:29cliebow (~cliebow@66.63.66.218) left irc: Quit: Leaving
19:30davidj (david@cpe-069-132-209-125.carolina.res.rr.com) left #ltsp.
20:09MorningSon (~MorningSo@cpe-66-25-84-220.satx.res.rr.com) left irc: Quit: WeeChat 0.3.0
20:16finn0000 (~finn@184-76-14-103.war.clearwire-wmx.net) joined #ltsp.
20:17Ghidorah (450e640c@gateway/web/freenode/ip.69.14.100.12) left irc: Quit: Page closed
20:19
<finn0000>
Hey I'm trying to set up an LTSP cluster root server, but the machine will only boot from it's hard drive or the network (PXE). I got it to get PXE off my Ubuntu laptop, then there was a problem and I had to start over and now it won't netboot
20:20
I checked netstat on my laptop and nothing related to tftp is open (dnsmasq has DNS open, that's it)
20:21
any ideas?
20:28
oh hold on
20:28
wow i'm stupid
20:28
the server has two network ports, i guess i had it in the wrong one
20:28
works fine now
20:28
I'll be back with more noob questions
20:28
just you wait
20:28finn0000 (finn@184-76-14-103.war.clearwire-wmx.net) left #ltsp ("Leaving").
20:59vagrantc (~vagrant@75-150-46-245-Oregon.hfc.comcastbusiness.net) left irc: Quit: leaving
21:39otavio (~otavio@debian/developer/otavio) left irc: Ping timeout: 276 seconds
21:46dyllan (~rooms@dsl-185-71-241.dynamic.wa.co.za) joined #ltsp.
21:46dyllan (~rooms@dsl-185-71-241.dynamic.wa.co.za) left irc: Changing host
21:46dyllan (~rooms@unaffiliated/kingmilo) joined #ltsp.
21:47
<dyllan>
Hi all
21:48patrickmw (~pwright@ip68-231-4-153.ph.ph.cox.net) left irc: Quit: Ex-Chat
21:49
<dyllan>
Is the best way to lockdown a users desktop, more specifically their wallpaper, still by using Gconf?
21:51cyberorg_ (~cyberorg@opensuse/member/Cyberorg) joined #ltsp.
21:52cyberorg_ (~cyberorg@opensuse/member/Cyberorg) left irc: Remote host closed the connection
21:52cyberorg (~cyberorg@opensuse/member/Cyberorg) left irc: Remote host closed the connection
21:55cyberorg (~cyberorg@opensuse/member/Cyberorg) joined #ltsp.
22:16dyllan (~rooms@unaffiliated/kingmilo) left irc: Quit: Rooms " iPhone IRC Client " http://www.roomsapp.mobi
22:28ball (~ball@c-98-226-194-183.hsd1.il.comcast.net) joined #ltsp.
22:48dyllan (~rooms@dsl-185-71-241.dynamic.wa.co.za) joined #ltsp.
22:48dyllan (~rooms@dsl-185-71-241.dynamic.wa.co.za) left irc: Changing host
22:48dyllan (~rooms@unaffiliated/kingmilo) joined #ltsp.
22:58dyllan (~rooms@unaffiliated/kingmilo) left irc: Quit: Rooms " iPhone IRC Client " http://www.roomsapp.mobi
22:59dyllan (~rooms@dsl-185-71-241.dynamic.wa.co.za) joined #ltsp.
22:59dyllan (~rooms@dsl-185-71-241.dynamic.wa.co.za) left irc: Changing host
22:59dyllan (~rooms@unaffiliated/kingmilo) joined #ltsp.
23:00dyllan (rooms@unaffiliated/kingmilo) left #ltsp.
23:12dyllan (~rooms@dsl-185-71-241.dynamic.wa.co.za) joined #ltsp.
23:12dyllan (~rooms@dsl-185-71-241.dynamic.wa.co.za) left irc: Changing host
23:12dyllan (~rooms@unaffiliated/kingmilo) joined #ltsp.
23:22dyllan (~rooms@unaffiliated/kingmilo) left irc: Quit: Rooms " iPhone IRC Client " http://www.roomsapp.mobi
23:51gnunux (~emmanuel@194.167.18.244) joined #ltsp.
00:00--- Thu Apr 21 2011