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


Channel log from 24 May 2010   (all times are UTC)

01:32Guerdal82_ has joined #ltsp
01:55rptan has joined #ltsp
02:02
<rptan>
hi, anyone familiar with the "failed to connect to NBD server" error for Ubuntu 10.04?
02:12toscalix has joined #ltsp
02:25
<Appiah>
does it not always say that?
02:27
<alkisg>
rptan: that's usually because dhcp points the client to the wrong server
02:27
(or, more rare, because the client is too fast, e.g. core 2 duo)
02:31
<rptan>
alkisg: hm, what i did is install ltsp on a server using alternate cd on amd64
02:32
<alkisg>
Hmmm maybe inetd.conf isn't pointing to the right file then
02:32
Try this:
02:32
grep nbd /etc/inetd.conf
02:32
<rptan>
alkisg: it was okay when i tested with VMs, but on the physical machines they need i386
02:33
<alkisg>
And see if the image file is actually present on the file system (/opt/ltsp/images/xxx)
02:34
<rptan>
alkisg: so i removed the directory and did a rebuild of the ltsp-client with the arch i386 option
02:34
<alkisg>
If inetd is pointing to and amd64.img and you have an i386.img, then that's your problem...
02:34elias_a has joined #ltsp
02:34
<rptan>
alkisg: ok let me check
02:37
alkisg: wow, ur right on target. do i need to restart anything after editing the conf file?
02:37
<alkisg>
sudo invoke-rc.d openbsd-inetd restart
02:38
<elias_a>
Mikael - are you arond?
02:38
...around?
02:41
<rptan>
alkisg: thanks alot, its working fine now.!
02:41
<alkisg>
np
02:54toscalix has quit IRC
03:32satellit_ has joined #ltsp
03:39bobby_C has joined #ltsp
03:46ogra_ has joined #ltsp
03:47ogra has quit IRC
03:47ogra_ is now known as ogra
03:47ogra has joined #ltsp
03:48ogra_ has joined #ltsp
03:48tlze has joined #ltsp
03:49ogra_ has quit IRC
03:51otavio has quit IRC
04:12bobby_C has quit IRC
04:32rmcgougan has joined #ltsp
04:38otavio has joined #ltsp
04:43
<rmcgougan>
Have been trying to set up a 64 bit alternate cd ltsp using Ubuntu lucid lynx as a ltsp server using one ethernet card to communicate with machines on my schools lan, our lan server is SME Server it allocates the dhcp for the lan. Have got client machines initiating the boot process from the i386 boot image on the ltsp server but I get an error saying nbd failure. Have tried dpkg-reconfigure nbd-server to create a config file in
04:43
/etc/nbd-server followed by sudo ltsp-update-image --arch i386 but still the thin clients cannot reach the log in page.
04:43
<Appiah>
09:32 < alkisg> grep nbd /etc/inetd.conf
04:44
09:33 < alkisg> If inetd is pointing to and amd64.img and you have an i386.img, then that's your problem...
04:44
<alkisg>
Heh, it seems that problem is quite common :)
04:44
<Appiah>
^^
04:46
<rmcgougan>
I thought it was necessary to create an i386 image even though the actual ltsp server is 64 bit because the thin clients are i386 machines is this a foolish mistake on my part?
04:47
<Appiah>
sudo ltsp-build-client --arch=i386
04:47
<alkisg>
rmcgougan: so now you have an i386 image?
04:47
If you do, then you just need to change inetd.conf...
04:50
<rmcgougan>
Thanks Appiah I did use sudo ltsp-build-client --arch=i386 and have created the i386 image, yes my problem is now how to change the inetd.conf I am a teacher just having a go at setting up an ltsp server in my school and do not know how to change inetd.conf to point at the i386.img
04:51
<Appiah>
just open the file with a text editor
04:51
<alkisg>
rmcgougan: sudo gedit /etc/inetd.conf
04:55
<rmcgougan>
I can use the terminal and can edit conf files but need some step by step help to alter /etc/inetd.conf file - do i just change amd64.img to i386.img within the file?
04:55
<alkisg>
Yes
04:56
Then, run this to restart inetd: sudo invoke-rc.d openbsd-inetd restart
04:56
<rmcgougan>
Thanks very much for the help.
05:08
I have already tried using K12Linux Live Server media (and now I'm trying Ubuntu Lucid Lynx ltsp) and ran into problems with screen lock ups on the clients and server using K12Linux Live Server when two or three thin clients were running flash player based websites. I read some tips that indicated you can edit the servers lts.conf file to allocate more ram for some applications such as firefox e.g. instead of 32mb ram per client
05:08
for firefox change the allocation to 128mb ram for that application to help avoid screen lock ups with multiple thin clents on flash player websites.
05:09
Do you think this editing of the lts.conf is a good move for schools where children often are using flash palyer based websites?
05:10
<alkisg>
What are your client specs?
05:11
(CPU/RAM, mostly?)
05:11
*and VGA
05:13
*and network speed, 100 mbps or gigabit?
05:18
<rmcgougan>
The specs vary but the machines generally are old with cpu 433-999, 128-512mb ram, vga -not sure but basic and 6-10 years old, network 100mb lan, ltsp server gigabit network cards x2, tried to use ltsp server with a switch but was only 100mb speed switch no gigabit connections. My current network set up is just using one gigabit ethernet card from ltsp server, with dhcp from our separate lan server pointing to the static ip of ou
05:18
r ltsp server to let the client find the boot image.
05:19rptan has quit IRC
05:20
<alkisg>
" My current network set up is just using one gigabit ethernet card from ltsp server" ==> but that is connected to a 100mbps switch, right?
05:20
That's a little low for LTSP, a gigabit connection from the server to the switch with flow control=off is required for acceptable flash playback
05:21
https://help.ubuntu.com/community/UbuntuLTSP/FlowControl
05:23
<rmcgougan>
Current set up just goes from ltsp server using one Gigabit ethernet connection on ltsp server straight to lan connection which is all 100mb cabling.
05:29
<alkisg>
So it's a 100mbps connection, too low for flash.
05:30tlze has quit IRC
05:33
<alkisg>
The best thing to do is to upgrade your switch, or at least use multiple cards on the server (https://help.ubuntu.com/community/UbuntuLTSP/Trunking)
05:33
<Mava>
shouldn't flash / browser be runned as a local-app ?
05:34
<alkisg>
With 10-year old PCs with 128 RAM? Not a chance... :)
05:34
<Mava>
heh, in that case =)
05:34
new switch would be perfect to be used
05:34
<alkisg>
Yeah, a 16 port switch with 1 gigabit port here costs about 60 €, which isn't much..
05:34
<rmcgougan>
The LTSP server has a gigabit ethernet connection going from it, but our lan is 100mb cabling in our school. So all the client machines are sending data through 100 mb cable.
05:35
<alkisg>
rmcgougan: but is the switch gigabit?
05:35
<Mava>
rmcgougan: the bottleneck link is the one which is between switch and server
05:35
<alkisg>
If it doesn't have a gigabit port, then the connection from the server to the switch is 100 mbps...
05:36
<rmcgougan>
No the switch is not gigabit, sounds like I definately need to use a switch with at least one gigabit port connected directly to the server.
05:36
<Mava>
switch must have at least one gigabit port and the server must be connected to it. in optimal case 10 clients can communicate with 100Mb/s speed with the server
05:37
yah, that is what you want =)
05:41
rmcgougan: as a tip, one good program to monitor current bandwidth usage in linux is bwm-ng. very lightweight and clear software. just shows you how much stuff is going in the network interfaces of the server =)
05:44
<rmcgougan>
Thanks very much your help, that has cleared this up for me. I will invest in a new switch.
05:45
<alkisg>
rmcgougan: make sure to read that page about flow control
05:45
Otherwise you may buy a gigabit switch and STILL have 100mbps bandwidth
05:45
(i.e. you may just waste your money if flow control is on)
05:47
<rmcgougan>
alkisg I appreciate the fine tuning about the flow control I have bookmarked the https://help.ubuntu.com/community/UbuntuLTSP/FlowControl page thanks again you've helped me e a lot:-)
05:55
<Mava>
also if you buy some switch which can be configured, it could be possible to disable flow control in the switch. never done that though, but it could also work
05:59
<rmcgougan>
thanks
05:59
<alkisg>
Yup it works, it's something one needs to check before buying a switch.
06:06
<Mava>
mm.. after a quick check i'm not sure after all is it as effective as disabling flow control as explained in that wiki page
06:07
it would be worth to make an experiment =)
06:07
but 2pm. coffee coffee coffee ->
06:12
<alkisg>
Mava: I've checked both ways (I wrote that page after some discussion in the mailing list), both are effective, but disabling flow control on the server NIC isn't always possible (depends on the NIC) and of course has some additional administrative overhead.
06:12
So the "get a good switch" way is always better, as long as one has the extra money
06:13
(the cheapest configurable switch that I found was 4-5 times more expensive than the unmanaged one)
06:19rmcgougan has left #ltsp
06:31
<Mava>
alkisg: ahaa... feeling kind a confused, so... the client cant process data enough fast and it sends PAUSE to server right ?
06:32
<alkisg>
Right, so the server pauses instead of sending data to another client
06:32
I've benchmarked with flow control off = 990 mbps and with flow control on = 90 mbps with the same switch (by changing flow control on the nic)
06:32
<Mava>
whoa
06:33
and the pause really is tcp connection ?`
06:33
<alkisg>
No, it's an ethernet pause
06:33
<Mava>
sorry, not the pause, but the connection is using tcp protocol ?
06:33
<alkisg>
Yes
06:33
I've tried that with netperf
06:33
<Mava>
layer 2 level pause ?
06:34
<alkisg>
I'm not sure about the level. But there's also flow control in the tcp protocol, and that is NOT a problem
06:34
I.e. if the client has to drop data because it receives it very fast, the sender lowers the rate because of the tcp protocol itself
06:35
<Mava>
ah, now it starts to feel much more understandable.. first i thought it was tcp pause, and tcp congestion control is different =)
06:36
and of course, once there happens this flow controlling in the lower levels it stops or lowers the whole ethernet so it affects also to another client connections
06:37
and now once flow control is disabled the congestion control in tcp protocol looks after the client machine =)
06:38
right ?
06:53pths has quit IRC
06:54pths has joined #ltsp
07:09pmatulis has joined #ltsp
07:16
<alkisg>
Mava, right, exactly
07:16jhutchins_lt has quit IRC
07:16Appiah has quit IRC
07:16morfic has quit IRC
07:16korcan has quit IRC
07:16dba has quit IRC
07:17Faithful has quit IRC
07:18jhutchins_lt has joined #ltsp
07:18Appiah has joined #ltsp
07:18morfic has joined #ltsp
07:18korcan has joined #ltsp
07:18dba has joined #ltsp
07:24ruxpin has joined #ltsp
07:29cliebow has joined #ltsp
07:36otavio has quit IRC
07:47Guerdal82_ has quit IRC
08:08komunista has joined #ltsp
08:23Gadi has joined #ltsp
08:51otavio has joined #ltsp
09:23ogra has quit IRC
09:24ogra has joined #ltsp
09:42Guerdal82_ has joined #ltsp
09:44highvoltage has quit IRC
09:46thunsucker has joined #ltsp
09:49highvoltage has joined #ltsp
09:56evilx has joined #ltsp
10:14pmatulis has quit IRC
10:14staffencasa has joined #ltsp
10:16Barbosa_ has joined #ltsp
10:19Barbosa has quit IRC
10:47pmatulis has joined #ltsp
10:52atkuepker has joined #ltsp
11:05vizz has joined #ltsp
11:06
<vizz>
which components i need, to get sound working at debian ltsp?
11:07japerry has quit IRC
11:07
<thunsucker>
vizz: do your thin clients have sound cards?
11:08
<vizz>
yes
11:09
<thunsucker>
vizz: then sound should work for them
11:09
vizz: does it not?
11:09
<vizz>
it didn't, i have installed pulseaudio on server and client and SOUND=yes in lts.conf
11:10
doesn't
11:10
<thunsucker>
vizz: are you using any screen scripts? like rdp script
11:10
vizz: if you are not using screen script, try leaving sound=yes out of lts.conf
11:13
<vizz>
no screen scripts, i tried without lts.con to
11:14
here are some hacks, i will try that http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=537526
11:16
<thunsucker>
vizz: so you get no sound at all?
11:16
vizz: on the client, did you go into sound settings and look around?
11:17
<vizz>
in the chroot?
11:17
<thunsucker>
on the tc desktop
11:18
vizz: you running squeeze?
11:18
<vizz>
true
11:20
<thunsucker>
vizz: sorry i'm not super familiar with that setup but if that stuff that you linked in that bug report might help
11:21
vizz: of course you could always hang out til vagrantic is here, he wrote that bug report
11:21
<vizz>
ok, thanks
11:21
<thunsucker>
vizz: sorry couldn't help more
11:22
the only other thing i can suggest
11:22
is
11:22
SOUND_DAEMON=PULSE
11:22
might work....dunno
11:29Selveste1 has quit IRC
11:38japerry has joined #ltsp
11:50japerry has quit IRC
12:12komunista has quit IRC
12:41
<atkuepker>
More Fun with Intel Video: Still having problems with Intel Video on our stock Ubuntu 9.10 installs. Switching to Metacity using gconftool didn't fix it. Any further suggestions?
12:41
I did notice that out version of xserver-xorg-video-intel is "2:2.9.0"
13:16alkisg1 has joined #ltsp
13:16alkisg has quit IRC
13:27* _UsUrPeR_ tips his hat
13:27
<_UsUrPeR_>
can anybody tell me how ltsp-remoteapps works, or how it would be used from an ltsp environment?
13:30
gadi: ping?
13:31
<johnny>
the same?
13:32
in client terminal (via ltsp-localapps xterm) ltsp-remoteapp oocalc
13:32* _UsUrPeR_ attempts
13:32
<johnny>
would open up oocalc on the server
13:32
if your distro has it packaged..
13:32
not sure which version of ubuntu includes it.. or if any do
13:33alkisg1 has quit IRC
13:33
<_UsUrPeR_>
hmm. Ok, so base Desktop installation is what I am using
13:33
<johnny>
it does what it says .. run an app remotely
13:33
<_UsUrPeR_>
on the localapps-opened xterm session, remoteapps exists, however when I attempt to run, nothing happens. is there a log file in /var/log on the server/client that reflects any problems?
13:34
<johnny>
i can imagine some useful cases might be, if a local app triggers an app that isn't truly a dep (and thus not installed) you could tell it to handle it on the server
13:34
<_UsUrPeR_>
yeah, such as opening an ooO doc from localapps firefox session
13:35
<johnny>
sure, but it probably only works on things with .desktop files.. or those that handle them
13:35atkuepker has quit IRC
13:35
<johnny>
at least directly, otherwise you'd have to create your own symlinks
13:35
or other aliases
13:35
i don't really know much about it other than that.. never needed it
13:35
_UsUrPeR_, look up who committed it, and ask them
13:35
<_UsUrPeR_>
yeah, definitely special cases for remoteapps
13:36
ok, thanks for your help johnny
13:36akuepker has joined #ltsp
13:39komunista has joined #ltsp
13:43johnny has left #ltsp
13:43mischko has joined #ltsp
13:44johnny has joined #ltsp
14:04vagrantc has joined #ltsp
14:13kusznir has joined #ltsp
14:14
<kusznir>
Hi all: I've got an issue that suddenly started this morning on my terminals. The terminals will netboot just fine, but stop at a console prompt. About 2-5 minutes later, it will load the graphical login, and things appear to progress normally.
14:15
All my DNS and the like seem to be working; no changes were made since last week (when everything worked well), and I've even restarted my dns server.
14:15
Any suggestions? What would cause that delay?
14:15
<vagrantc>
sounds like name resolution issues...
14:15
<kusznir>
I'm not sure where else to look...The server's forward and reverse lookup succeed just fine; the client's doesn't generally look up at all.
14:15
(dynamic IPs)
14:16
<vagrantc>
possibly a stalling ldm/rc.d hook or ltsp/xinitrc.d hook
14:16
<kusznir>
vagrantc: what would not be resolving? The DNS server is definitely working in a general sense; I'm not sure what to check for specifically.
14:17
<vagrantc>
in /opt/ltsp/i386/usr/share
14:17
the clients have access to the DNS server?
14:17
<kusznir>
On the same network as the dns server itself, several other devices are working.
14:17akuepker has quit IRC
14:20Lns has joined #ltsp
14:21
<kusznir>
Hmm...so I logged in as root on the thin client. DNS works fine (can ping google, it resolves it. The host command isn't installed, so its hard to do through testing, but it can get to and resolve the thin client servers)
14:21
dmesg just had some notes about block read errors on the squashfs (which have been there sinc ethe beginning, and others here told me to ignore it)
14:22
There is NOTHING in any of the log files in /var/log
14:22
I don't know where else to look.
14:22
btw: nothing has changed in the ltsp export in months...I haven't even rebuilt the nbd image in over a month.
14:26
<thunsucker>
kusznir: anything else change in the network
14:26
switches, routers, internet anything?
14:33
<komunista>
kusznir: firewall?
14:34
<vagrantc>
kusznir: once the graphical screen comes up, it works fine, though?
14:37
<kusznir>
thunsucker: upstream, not downstream that I'm aware of.
14:38
<thunsucker>
kusznir: more specific please
14:42
<kusznir>
I have my switch that all my stuff is connected to (clients, servers, and routers). I don't control stuff upstream (main university network that my router connects to), and they've been making changes (most of which they don't announce)
14:42
I know they replaced their switches, and I've also been seeing signs of sludgyness in places. However, my setup is supposed to be "self-contained".
14:44bobby_C has joined #ltsp
14:44
<thunsucker>
kusznir: so your servers like dns are on your local switch
14:45
kusznir: what order do the dns servers go in? their dns, your dns?
14:45
<kusznir>
I'm running pfsence for my router, which is plugged into my switch. pfsense handles dns, dhcp, and ip routing.
14:45
<thunsucker>
ok just out of curiousity
14:45
disconnect yourself from them
14:45
so you are 100% truly contained
14:45
<kusznir>
my thin clients are only configured with one DNS server, and that's mine.
14:46
Unfortunately, i can't disconnect myself. This is production network with 20+ people on the clock, and doing that would down them all (no e-mail, web, ssh sessions to off-site, etc).
14:47
<thunsucker>
kusznir: if upstream there is sluggishness
14:47
it's possible that it's effecting your local users
14:47
of coruse do the normal stuff, reboot your server and router and etc.
14:47
<kusznir>
What I don't get is the ONLY place I experience any sluggishness is the starting of the login. Once the login screen comes up, everything else (including full auth/session loading) works fine.
14:48
<thunsucker>
kusznir: yes, and unfortenly i'm not an ubuntu master to know exactly whats it doing
14:48
<kusznir>
I've restarted services on my router. I want to reboot my server, but I've got a bunch of users on it in the middle of work. The sucky part of production systems....
14:48
<thunsucker>
maybe it's looking for something specific on bootup
14:48
kusznir: what distro you running?
14:49
<kusznir>
ubuntu. The server booting my thin clients is 9.04. I also have a 9.10 thin client server, but its not seeing as much use due to stability problems with samba/winbind (that samba is claiming is ubuntu, and ubuntu is just ignoring)
14:49
<thunsucker>
kusznir: reboot everything tonight and see whbat happens
14:49
then try isolating them to see what happens
14:49
<kusznir>
This does lead me to another question: For ease of troubleshooting/maintence, I'd like to create a dedicated vm server that JUST serves up the thin client images. That way I can have a variety of terminal servers for different needs/load balancing, and be able to reboot the terminal servers without "crashing" all the thin clients.
14:49
<thunsucker>
then report back :)
14:50
<kusznir>
(that's the wort part about rebooting...if its what the clients are booting off of, then they all get in a wierd state that my users can't figure out, and I get tons of calls until I go through every single one and power cycle them.
14:50
<thunsucker>
kusznir: ltsp-load balancing :)
14:51
kusznir: in a couple of my setups, i do a weekly snapshop of the ltsp erver
14:51
*server
14:51
<kusznir>
It has to do with the nbd server restarting; aparently that causes the thin clients to crash.
14:51
<thunsucker>
if it freaks out
14:51
i power it off, power on the backup
14:51
and then test the "freaked out one"
14:51
kusznir: just pull the power breakers
14:51
kill everything :)
14:52
kusznir, talk to you later, hopefull you resolve it i'm going home for the night
14:52thunsucker has quit IRC
14:52
<kusznir>
:)
14:52cliebow has quit IRC
14:53
<kusznir>
Thanks (unfortunately, I am not certified nor authorized to reset the 2,000A breaker to the building; and I have stuff spread around....
14:56
<komunista>
kusznir: are you sure that there is not another DHCP server?
14:57
<kusznir>
I'd be very surprised. The initial dhcp goes very quickly, and it reports all the right info. It boots correctly, and comes up with a correct IP in a correct range, and the correct dhcp server.
14:57
and the correct dns server
14:58
And no other devices (personal laptops on same network) are reporting problems.
14:59
<komunista>
the another DHCP don't must give the boot image
15:00
then first boot is OK
15:02
but after boot the thin clients gets IP again, without PXE image, and another DHCP can take place...
15:02
<kusznir>
I log into the thin client's console after it boots to that level and log in; its got all the right IP settings at that point (which is when it should be launching the graphical login, but isn't)
15:05
<komunista>
have you remote syslog enabled? https://help.ubuntu.com/community/UbuntuLTSP/ClientTroubleshooting
15:07
<kusznir>
Nope, I haven't taken any explicit steps to enable remote syslog.
15:08
<_UsUrPeR_>
stgraber: When attempting to run ltsp-remoteapps from an xterm session on an ltsp client, it appears nothing happens. Is there an lts.conf setting required for remoteapps to be enabled?
15:11
<johnny>
lern2grep _UsUrPeR_
15:11
<komunista>
kusznir: try folow https://help.ubuntu.com/community/UbuntuLTSP/TCSyslogToLTSPServer
15:11
<johnny>
just in case
15:11
<_UsUrPeR_>
:<
15:11
<komunista>
kusznir: reboot thin client and while reboot you can see in serrvers syslog...
15:12
*server's syslog :-)
15:16alkisg has joined #ltsp
15:17
<kusznir>
I'm logging into the server looking at the logs (or what I can find of them -- dmesg works fine), but not seeing much of anything helpful.
15:17
How do I manually kick off the graphical login?
15:19
(in my terminal so I can catch any stdout/stderr output)
15:19
<komunista>
killall ldm
15:19japerry has joined #ltsp
15:19
<kusznir>
then just "ldm"?
15:19
<komunista>
but it autostart again :-)
15:20
<kusznir>
The problem I'm having is it doesn't seem to be doing that, or its taking a very long time to do that.
15:20
<komunista>
and here is problem with long time to start login dialog or to login?
15:20
<kusznir>
long time to start login dialog.
15:21
ldm takes a long time to show up; it sits at the text login prompt for several minutes.
15:21
(text login prompt -> the thin client's console login)
15:21
<komunista>
try kill it and see if the long time to start ldm go again
15:25
<alkisg>
How much ram does the client have?
15:37
<kusznir>
I think a gig of ram.
15:39
<alkisg>
You could install bootchart to watch where the delay is...
15:46johnny has left #ltsp
16:07komunista has quit IRC
16:10johnny has joined #ltsp
16:15alkisg has quit IRC
16:20bobby_C has quit IRC
16:20vagrantc has quit IRC
16:24vagrantc has joined #ltsp
16:27
<johnny>
so wha'ts needed to enable the ntp service these days on ubuntu/ltsp?
16:28
just set TIMESERVER in lts.conf and install ntp on the server?
16:31
<vagrantc>
think so
16:32
unless ntpdate isn't installed in the chroot
16:33
<johnny>
it is
16:33
ok.. so now i'll just wait til i reboot em
16:36atkuepker has joined #ltsp
17:00japerry has quit IRC
17:10
<vizz>
~
17:13pmatulis has quit IRC
17:31satellit_ has quit IRC
17:31satellit_ has joined #ltsp
17:46japerry has joined #ltsp
17:58Gadi has left #ltsp
18:00mischko has quit IRC
18:21Selveste1 has joined #ltsp
18:36staffencasa has quit IRC
18:46Barbosa has joined #ltsp
18:47Barbosa_ has quit IRC
18:49Lns has quit IRC
18:59vagrantc has quit IRC
19:53Selveste1 has quit IRC
20:01pmatulis has joined #ltsp
20:10F-GT has quit IRC
20:20F-GT has joined #ltsp
20:46pmatulis has quit IRC
21:04_UsUrPeR_ has quit IRC
21:19lucascoala has joined #ltsp
21:55johnny has left #ltsp
22:18ogra_cmpc has quit IRC
22:31ogra_cmpc has joined #ltsp
22:36johnny has joined #ltsp
23:20rjune has quit IRC
23:26johnny has left #ltsp
23:27johnny has joined #ltsp
23:33abeehc has quit IRC
23:40abeehc has joined #ltsp
23:47abeehc has quit IRC
23:54abeehc has joined #ltsp