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


Channel log from 18 August 2015   (all times are UTC)

00:11diq has joined IRC (diq!519c2e49@gateway/web/freenode/ip.81.156.46.73)
02:22Parker955_Away has left IRC (Parker955_Away!~parker@2001:470:8:a61::8bdc:c4f, Ping timeout: 244 seconds)
02:31Parker955_Away has joined IRC (Parker955_Away!~parker@2001:470:8:a61::8bdc:c4f)
02:39Parker955_Away has left IRC (Parker955_Away!~parker@2001:470:8:a61::8bdc:c4f, Ping timeout: 246 seconds)
02:46Parker955_Away has joined IRC (Parker955_Away!~parker@2001:470:8:a61::8bdc:c4f)
03:10Parker955_Away has left IRC (Parker955_Away!~parker@2001:470:8:a61::8bdc:c4f, Ping timeout: 246 seconds)
03:23Parker955_Away has joined IRC (Parker955_Away!~parker@2001:470:8:a61::8bdc:c4f)
03:32Parker955_Away has left IRC (Parker955_Away!~parker@2001:470:8:a61::8bdc:c4f, Ping timeout: 244 seconds)
03:37Parker955_Away has joined IRC (Parker955_Away!~parker@2001:470:8:a61::8bdc:c4f)
03:44Parker955_Away has left IRC (Parker955_Away!~parker@2001:470:8:a61::8bdc:c4f, Ping timeout: 244 seconds)
03:53Parker955_Away has joined IRC (Parker955_Away!~parker@2001:470:8:a61::8bdc:c4f)
04:09Parker955_Away has left IRC (Parker955_Away!~parker@2001:470:8:a61::8bdc:c4f, Ping timeout: 246 seconds)
04:12Parker955_Away has joined IRC (Parker955_Away!~parker@2001:470:8:a61::8bdc:c4f)
04:21Parker955_Away has left IRC (Parker955_Away!~parker@2001:470:8:a61::8bdc:c4f, Ping timeout: 244 seconds)
04:30Parker955_Away has joined IRC (Parker955_Away!~parker@2001:470:8:a61::8bdc:c4f)
04:34dtcrshr has left IRC (dtcrshr!~datacrush@unaffiliated/datacrusher, Ping timeout: 252 seconds)
04:38dtcrshr has joined IRC (dtcrshr!~datacrush@unaffiliated/datacrusher)
04:40ricotz has joined IRC (ricotz!~rico@ubuntu/member/ricotz)
04:41Parker955_Away has left IRC (Parker955_Away!~parker@2001:470:8:a61::8bdc:c4f, Ping timeout: 244 seconds)
04:41Parker955_Away has joined IRC (Parker955_Away!~parker@2001:470:8:a61::8bdc:c4f)
04:51Parker955_Away has left IRC (Parker955_Away!~parker@2001:470:8:a61::8bdc:c4f, Ping timeout: 244 seconds)
04:55Parker955_Away has joined IRC (Parker955_Away!~parker@2001:470:8:a61::8bdc:c4f)
04:56quinox has left IRC (quinox!~quinox@ghost.qtea.nl, Quit: :wq)
04:57quinox has joined IRC (quinox!~quinox@ghost.qtea.nl)
05:13Parker955_Away has left IRC (Parker955_Away!~parker@2001:470:8:a61::8bdc:c4f, Ping timeout: 246 seconds)
05:20Parker955_Away has joined IRC (Parker955_Away!~parker@2001:470:8:a61::8bdc:c4f)
05:27Parker955_Away has left IRC (Parker955_Away!~parker@2001:470:8:a61::8bdc:c4f, Ping timeout: 244 seconds)
05:27Parker955_Away has joined IRC (Parker955_Away!~parker@2001:470:8:a61::8bdc:c4f)
05:32Parker955_Away has left IRC (Parker955_Away!~parker@2001:470:8:a61::8bdc:c4f, Ping timeout: 244 seconds)
05:37Parker955_Away has joined IRC (Parker955_Away!~parker@2001:470:8:a61::8bdc:c4f)
06:10Parker955_Away has left IRC (Parker955_Away!~parker@2001:470:8:a61::8bdc:c4f, Ping timeout: 244 seconds)
06:11Parker955_Away has joined IRC (Parker955_Away!~parker@2001:470:8:a61::8bdc:c4f)
06:20
<zamba>
vsuojanen: that's what i did.. removed /opt/ltsp/i386 and then ran 'ltsp-build-client'.. same error
06:20
(to new listeners) i'm trying to do ltsp-build-client and getting: error: LTSP client installation ended abnormally
06:20
and that's all
07:05Parker955_Away has left IRC (Parker955_Away!~parker@2001:470:8:a61::8bdc:c4f, Ping timeout: 246 seconds)
07:11Parker955_Away has joined IRC (Parker955_Away!~parker@2001:470:8:a61::8bdc:c4f)
07:22Parker955_Away has left IRC (Parker955_Away!~parker@2001:470:8:a61::8bdc:c4f, Ping timeout: 246 seconds)
07:22vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
07:25work_alkisg is now known as alkisg
07:25* alkisg waves
07:25
<alkisg>
zamba: distro/version/debug output?
07:26
ltsp-build-client --debug
07:27Parker955_Away has joined IRC (Parker955_Away!~parker@2001:470:8:a61::8bdc:c4f)
07:28* vagrantc waves
07:40* muppis yawns
07:40
<muppis>
!raspberry
07:40
<ltsp`>
I do not know about 'raspberry', but I do know about these similar topics: 'raspberrypi'
07:40
<muppis>
!raspberrypi
07:40
<ltsp`>
raspberrypi: (#1) LTSP with raspberry pi: http://cascadia.debian.net/trenza/Documentation/raspberrypi-ltsp-howto/, or (#2) To use a similar environment to LTSP on the raspberry pi http://berryterminal.com/, or (#3) https://github.com/gbaman/RaspberryPi-LTSP, or (#4) https://pi-ltsp.net
07:41
<vagrantc>
so many choices
07:42
<zamba>
alkisg: Ubuntu 12.04.5 LTS
07:42
<muppis>
Yes. Hopefully atleast one works. :D
07:42
<alkisg>
zamba, put the debug output to pastebin
07:43
<zamba>
alkisg: debug output goes to stderr?
07:43
i believe i've already pastebin-ed that.. one sec
07:43
<alkisg>
I believe so (if you do run ltsp-build-client --debug)
07:44
<vagrantc>
zamba: you may need to copy the link to this channel
07:45
<zamba>
vagrantc: sure, i know
07:45
but i see that the previous pastebin was without --debug, so i'm rerunning now
07:47
<alkisg>
Make sure that /opt/ltsp is removed before re-running it
07:55
Hyperbyte: so, being the systemd expert of the channel, would you be able to help to pinpoint where to prevent systemd from deactivating the swap (swap.target) and from doing `ifdown eth0` on shutdown? :)
07:55
Do you think that we just need an ltsp-client.service that depends on those 2 targets, to keep them alive?
07:59
<vagrantc>
alkisg: you're testing with something built from a recent -trunk ?
07:59
<alkisg>
From 4-5 days ago, the last daily build I sent
08:00
vagrantc: I'm thinking of implementing a "ROOT_PASSWD_HASH=xxx" directive in init-ltsp.d, which will sed /etc/passwd and add the root hash, so that users will be able to log in to VTs, it's not a bad idea, is it?
08:00
Or, what's a better name for it?
08:01
<vagrantc>
alkisg: doesn't sound too bad.
08:01
<alkisg>
It should be a bit better than SCREEN_02=shell, i.e. it will need less memory and have a bit more security
08:02
Hrm there's a problem with $ in lts.conf though... they get evaluated as variables
08:03
<zamba>
alkisg: hehe, still running.. will upload as soon as it's done
08:06Parker955_Away has left IRC (Parker955_Away!~parker@2001:470:8:a61::8bdc:c4f, Ping timeout: 244 seconds)
08:09Parker955_Away has joined IRC (Parker955_Away!~parker@2001:470:8:a61::8bdc:c4f)
08:12
<zamba>
alkisg: http://pastebin.com/jCBstQrf
08:14
<alkisg>
zamba, it seems like the problem is in ltsp-update-kernels, can you run this? `sudo -i; ltsp-update-kernels && echo ok`
08:14
Does this print ok?
08:14
<zamba>
alkisg: nope
08:15
<alkisg>
So it's an issue with ltsp-update-kernels, go on with: sh -x /usr/sbin/ltsp-update-kernels 2>/tmp/output
08:15
and pastebin its output
08:16Parker955_Away has left IRC (Parker955_Away!~parker@2001:470:8:a61::8bdc:c4f, Ping timeout: 246 seconds)
08:17Parker955_Away has joined IRC (Parker955_Away!~parker@2001:470:8:a61::8bdc:c4f)
08:18
<zamba>
http://pastebin.com/Up2cq537
08:21
<alkisg>
zamba: always as root, try this: if [ -f /selinux/enforce ] && [ -x /sbin/restorecon ]; then echo ok; fi
08:21
Does it echo ok?
08:24
<zamba>
nope
08:27
<alkisg>
zamba: it needs to be debugged in your environment but I don't have that much time to do it step by step over irc, do you want vnc?
08:27
!vnc
08:27
<ltsp`>
I do not know about 'vnc', but I do know about these similar topics: 'x11vnc', 'kvm-vnc', 'vnc-plinet', 'vnc-alkisg', 'vnc-dide'
08:27
<alkisg>
!vnc-dide
08:27
<ltsp`>
vnc-dide: To share your screen with me, run this: sudo apt-get --yes install x11vnc; x11vnc -connect srv1-dide.ioa.sch.gr - this is a reverse connection, it doesn't need port forwarding etc.
08:29
<zamba>
alkisg: i'm headlessly connected to the server
08:29
alkisg: and i'm afraid i can't share MY screen with you, as i'm currently at work :)
08:29
the server is located somewhere else
08:30
<alkisg>
!socat
08:30
<ltsp`>
socat: One way to share a console with a remote person is: [local pc] forward port 5500; apt-get install socat; socat tcp-listen:5500,keepalive=1 stdio,raw,echo=0 [remote pc] apt-get install socat screen; socat SYSTEM:"sleep 1; exec screen -xRR ra",pty,stderr tcp:REMOTE-IP:5500 & screen -l -S ra
08:30
<alkisg>
There's also this one if you want...
08:31
<zamba>
what do i need to run here?
08:32
<alkisg>
Gimme 1 min...
08:32
<zamba>
sure :)
08:33
<alkisg>
sudo apt-get install screen socat
08:33
socat SYSTEM:"sleep 1; exec screen -xRR ra",pty,stderr tcp:81.186.20.0:5500 & screen -l -S ra
08:33
<zamba>
like that?
08:33
<alkisg>
socat SYSTEM:"sleep 1; exec screen -xRR ra",pty,stderr tcp:81.186.20.0:5499 & screen -l -S ra
08:33
One wrong port, use the last command instead of the previous
08:33
Yes those 2 commands exactly
08:33
that was fast :)
08:35
<zamba>
you look fast too :)
08:35
<alkisg>
Aaaah old code there...
08:37
zamba, the problem was the last line in ltsp-update-kernels, [ -f /selinux/enforce ] && /sbin/restorecon -R $TFTPDIR || true > /dev/null
08:37
Without the || true that I put, it sent the wrong message, that ltsp-update-kernels failed
08:37
That was solved in later versions, i.e. yeeears ago... :)
08:37
<zamba>
ah, ok, when in fact it didn't fail?
08:37
<alkisg>
ltsp-update-kernels didn't fail, but ltsp-build-client though that it did fail, so it stopped
08:37
<zamba>
aha
08:38
so rerun everything
08:38
<alkisg>
So, run ltsp-build-client once more to make sure everything's ok
08:38
Yup
08:38
"exit" to close the connection
08:38
<zamba>
awesome! thanks!
08:38
<alkisg>
np, that was much quicker than chat+pastebin :)
08:38
<zamba>
definitely :)
08:39
this should be the de facto way to support people on freenode ;)
08:39
<alkisg>
Haha, I think it should be pizza or beer driven then :D
08:39
<zamba>
hehe
08:50telex has left IRC (telex!teletype@freeshell.de, Remote host closed the connection)
08:52Grembler has joined IRC (Grembler!~Ben@cpc29-aztw22-2-0-cust128.18-1.cable.virginm.net)
08:52telex has joined IRC (telex!teletype@freeshell.de)
08:53Grembler has left IRC (Grembler!~Ben@cpc29-aztw22-2-0-cust128.18-1.cable.virginm.net, Client Quit)
08:58Phantomas has joined IRC (Phantomas!~ftsamis@ubuntu/member/phantomas)
08:59
<alkisg>
!learn ROOT_PASSWORD_HASH as `to be able to login as root in vt1, put this in lts.conf: INIT_COMMAND_01="sed 's!^roiot:[^:]*:!root:$6$p2LdWE6j$PDd1TUzGvvIkj9SE8wbw1gA/MD66tHHlStqi1.qyv860oK47UnKcafSKqGp7cbgZUPlgyPv6giCVyCSCdJt1b0:!' -i /etc/shadow - the password then is qwer1234`
08:59
<ltsp`>
The operation succeeded.
08:59
<alkisg>
!ROOT_PASSWORD_HASH
08:59
<ltsp`>
ROOT_PASSWORD_HASH: to be able to login as root in vt1, put this in lts.conf: INIT_COMMAND_01="sed 's!^roiot:[^:]*:!root:$6$p2LdWE6j$PDd1TUzGvvIkj9SE8wbw1gA/MD66tHHlStqi1.qyv860oK47UnKcafSKqGp7cbgZUPlgyPv6giCVyCSCdJt1b0:!' -i /etc/shadow - the password then is qwer1234
09:01Parker955_Away has left IRC (Parker955_Away!~parker@2001:470:8:a61::8bdc:c4f, Ping timeout: 244 seconds)
09:02Parker955_Away has joined IRC (Parker955_Away!~parker@2001:470:8:a61::8bdc:c4f)
09:16gbaman has joined IRC (gbaman!~gbaman@104.40.144.249)
09:21gbaman has left IRC (gbaman!~gbaman@104.40.144.249, Ping timeout: 265 seconds)
10:02Parker955_Away has left IRC (Parker955_Away!~parker@2001:470:8:a61::8bdc:c4f, Ping timeout: 244 seconds)
10:02Parker955_Away has joined IRC (Parker955_Away!~parker@2001:470:8:a61::8bdc:c4f)
10:03vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Ping timeout: 240 seconds)
10:17Parker955_Away has left IRC (Parker955_Away!~parker@2001:470:8:a61::8bdc:c4f, Ping timeout: 244 seconds)
10:18Parker955_Away has joined IRC (Parker955_Away!~parker@2001:470:8:a61::8bdc:c4f)
10:23Parker955_Away has left IRC (Parker955_Away!~parker@2001:470:8:a61::8bdc:c4f, Ping timeout: 246 seconds)
10:28Parker955_Away has joined IRC (Parker955_Away!~parker@2001:470:8:a61::8bdc:c4f)
10:36
<fiesh>
does anyone manage to have, in firefox, something besides "WebGL RendererBlocked for your graphics card because of unresolved driver issues."?
10:36
(and likewise "GPU Accelerated Windows0/1 Basic (OMTC) Blocked for your graphics card because of unresolved driver issues.")
10:37
opengl in general works
10:37
(with LIBGL_ALWAYS_INDIRECT being set)
10:37
<alkisg>
fiesh: in thin clients or in fat clients?
10:38
<fiesh>
thin
10:38
I imagine fat clients shouldn't be a problem
10:38
<alkisg>
I don't think 3d works over the network without such issues
10:39
<fiesh>
hmm ok, I was just hoping there might be a chance since quake3 works perfectly, hehe
10:39
<alkisg>
http://www.virtualgl.org/ is one chance
10:39
I'm hearing it sometimes works
10:39
The software rendering is good enough for some things, not good for others
10:39
<fiesh>
yeah but that's for utilizing the server's 3d capabilities on clients, isn't it?
10:40
<alkisg>
Hmm there was one project for transfering 3d over the network
10:42
Why not use localapps instead?
10:46
<fiesh>
because I have no clue what that is ;)
10:47
!localapps
10:47
<ltsp`>
localapps: to access a tutorial on setting up localapps on jaunty, see https://help.ubuntu.com/community/UbuntuLTSP/LTSPLocalAppsJaunty
10:47
<fiesh>
hmm, 404
10:48
<alkisg>
!localxterm
10:48
<ltsp`>
localxterm: Any applications that you launch on a thin client actually runs on the server, not on the client itself. If you want to open a program on the client locally, you can type 'ltsp-localapps <program>' in a run dialog or in a terminal. For example, 'ltsp-localapps xterm' to open a terminal running on the client.
10:48
<alkisg>
!fatclients
10:48
<ltsp`>
fatclients: You may find some info about the Ubuntu/LTSP implementation of fat clients at https://help.ubuntu.com/community/UbuntuLTSP/FatClients
10:48
<alkisg>
!ltsp-pnp
10:48
<ltsp`>
ltsp-pnp: ltsp-pnp is an alternative (upstream) method to maintain LTSP installations for thin and fat clients that doesn't involve chroots: https://help.ubuntu.com/community/UbuntuLTSP/ltsp-pnp
10:48
<alkisg>
local apps is a method to have some applications running locally, with the cpu and ram and gpu of the client
10:49
fat clients is "all apps locally, but still netbooted from the ltsp server, still diskless"
10:49
<fiesh>
hmm I see, yeah I don't want to use fat clients, the disk performance will be much worse and I'd have to set up distcc to compile on the server and so on
10:55
<alkisg>
Fat clients have no disks
10:55
It's no different that your current ltsp setup
10:55
It's just a matter of clients using their own resources
10:55
What are your client specs, cpu/ram?
10:56
fiesh: ^
10:57Parker955_Away has left IRC (Parker955_Away!~parker@2001:470:8:a61::8bdc:c4f, Ping timeout: 244 seconds)
10:58
<fiesh>
alkisg: yes, they use NFS which is quite slow compared to direct disk access
10:59
alkisg: the clients are the newest NUCs but only have 4gb ram because I intended to use them just as thin clients
10:59Parker955_Away has joined IRC (Parker955_Away!~parker@2001:470:8:a61::8bdc:c4f)
10:59
<fiesh>
alkisg: but it's perfectly fine, firefox runs very smoothly even on the 4K displays, I was just wondering about the opengl acceleration
10:59
<alkisg>
Usually, screen updates need 10 times more bandwidth than disk access
10:59
But it depends on what you're doing
10:59
<fiesh>
alkisg: qtcreator, on the other hand, is awfully slow
10:59
bandwidth, yes, but the latency is the issue
11:00
the bandwidth in the gbit network is sufficient
11:01
<alkisg>
!flash
11:01
<ltsp`>
flash: Yes, flash sucks. An HD full screen 30 fps video needs 2.5 Gbps bandwidth (1920×1080×4×30)! Make sure you have LDM_DIRECTX=True in your lts.conf file, or if it's just youtube you're after, try some flash replacing plugin like http://linterna-magica.nongnu.org
11:01
<fiesh>
haha I'm not allowing flash here ;)
11:01
<alkisg>
...2.5 gbps * 10 clients ==> 25 gbps, much more than usual disk access... :)
11:01
Scrolling firefox is the same
11:01
It again produces screen updates
11:02
<fiesh>
it doesn't appear so, inkscape and firefox scroll _extremely_ smoothly, I somehow suspect they do some trickery that does not require screen updates
11:02
but I might be wrong, either way it is imperceptible
11:04Parker955_Away has left IRC (Parker955_Away!~parker@2001:470:8:a61::8bdc:c4f, Ping timeout: 244 seconds)
11:07Parker955_Away has joined IRC (Parker955_Away!~parker@2001:470:8:a61::8bdc:c4f)
11:11Parker955_Away has left IRC (Parker955_Away!~parker@2001:470:8:a61::8bdc:c4f, Ping timeout: 244 seconds)
11:12Parker955_Away has joined IRC (Parker955_Away!~parker@2001:470:8:a61::8bdc:c4f)
11:35vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
11:39PeperPots___ has left IRC (PeperPots___!sid1218@gateway/web/irccloud.com/x-mntrcologovhjxne, Ping timeout: 256 seconds)
11:42Faith has joined IRC (Faith!~paty@unaffiliated/faith)
11:53vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving)
11:55syrius has left IRC (syrius!~syrius@thunder.stormtek.net, Ping timeout: 250 seconds)
11:56alkisg is now known as work_alkisg
12:05syrius has joined IRC (syrius!~syrius@thunder.stormtek.net)
12:26PeperPots___ has joined IRC (PeperPots___!sid1218@gateway/web/irccloud.com/x-toksvemjbgzvddch)
12:47PeperPots___ has left IRC (PeperPots___!sid1218@gateway/web/irccloud.com/x-toksvemjbgzvddch, Ping timeout: 250 seconds)
12:53Faith has left IRC (Faith!~paty@unaffiliated/faith, Ping timeout: 250 seconds)
12:54Faith has joined IRC (Faith!~paty@143.107.231.49)
12:55Faith is now known as Guest19773
12:55F-GT has left IRC (F-GT!~phantom@ppp121-44-138-161.lns20.syd7.internode.on.net, Ping timeout: 272 seconds)
12:56Guest19773 is now known as Faith
12:56Faith has joined IRC (Faith!~paty@unaffiliated/faith)
12:59syrius has left IRC (syrius!~syrius@thunder.stormtek.net, Ping timeout: 244 seconds)
13:02syrius has joined IRC (syrius!~syrius@thunder.stormtek.net)
13:32PeperPots___ has joined IRC (PeperPots___!sid1218@gateway/web/irccloud.com/x-qxrcjhtwnggvbfbe)
13:49syrius has left IRC (syrius!~syrius@thunder.stormtek.net, Ping timeout: 250 seconds)
13:50ben_roose has joined IRC (ben_roose!~roose@156.26.10.48)
14:02PeperPots___ has left IRC (PeperPots___!sid1218@gateway/web/irccloud.com/x-qxrcjhtwnggvbfbe, Ping timeout: 245 seconds)
14:10PeperPots___ has joined IRC (PeperPots___!sid1218@gateway/web/irccloud.com/x-ymfxvcnfspujrhuz)
14:25sutula_ has joined IRC (sutula_!~sutula@207-118-180-127.dyn.centurytel.net)
14:25sutula has left IRC (sutula!~sutula@207-118-180-127.dyn.centurytel.net, Read error: Connection reset by peer)
14:25sutula_ is now known as sutula
14:34mip5 has joined IRC (mip5!~chatzilla@208.72.71.69)
14:55bennabiy has joined IRC (bennabiy!~bennabiy@unaffiliated/bennabiy)
14:56
<mip5>
Hi Folks - I was able to build my clients successfully after alkisg helped me diagnose errors in my dhcpd.conf file. And I was able to fix the dual monitor bug, by appending video=LVDS-1:d to /var/lib/tftpboot/ltsp/amd64/pxelinux.cfg/default. However, the clients are very slow - much slower than they had been in previous versions. Here's a copy of my ltsp-build-client.conf http://pastebin.com/E39
14:56
U0XHS
14:56
Sorry - pastebin is: http://pastebin.com/E39U0XHS
14:56
<championofcyrodi>
mip5: what hardware are your clients?
14:57
<mip5>
polywell - they have worked great in the past
14:57
<championofcyrodi>
what model
14:58
<mip5>
I'm not onsite - let me look at my records and see if I can get that.
14:58ogra_` has joined IRC (ogra_`!~ogra_@p5098ed03.dip0.t-ipconnect.de)
14:59
<championofcyrodi>
im curious as to what exactly is 'slow' ramdisk i/o, network disk i/o, gpu, cpu...
14:59Freejack has left IRC (Freejack!~Freejack@unaffiliated/freejack, *.net *.split)
14:59mgariepy has left IRC (mgariepy!~mgariepy@ubuntu/member/mgariepy, *.net *.split)
14:59ogra_ has left IRC (ogra_!~ogra_@p5098ed03.dip0.t-ipconnect.de, *.net *.split)
14:59klausade has left IRC (klausade!~klaus@cm-84.215.169.187.getinternet.no, *.net *.split)
14:59andygraybeal has left IRC (andygraybeal!~andy@h210.32.30.71.dynamic.ip.windstream.net, *.net *.split)
15:00
<championofcyrodi>
http://www.polywell.com/us/oem/enclosure.asp
15:00
^list ?
15:00ogra_` is now known as ogra_
15:01Freejack has joined IRC (Freejack!~Freejack@unaffiliated/freejack)
15:02
<mip5>
Yeah - me too. I'll get onsite and look. They are probably 3 years old, have 2 gbs of ram. They are fanless. I'm pretty sure they were i5 something. I'll be able to check in about 15 minutes. Thanks for your interest in helping!
15:06andygraybeal has joined IRC (andygraybeal!~andy@h210.32.30.71.dynamic.ip.windstream.net)
15:07mip5 has left IRC (mip5!~chatzilla@208.72.71.69, Ping timeout: 244 seconds)
15:09
<championofcyrodi>
the fanless series on the polywell site doesnt seem to include i series processors.
15:10
which means it may just be a celeron or atom, thus natively slower.
15:10
actuallly, i see a couple of fanless haswells
15:12mgariepy has joined IRC (mgariepy!~mgariepy@styx-204.ccs.usherbrooke.ca)
15:23mip5 has joined IRC (mip5!~chatzilla@208.72.71.69)
15:35
<mip5>
championofcyrodi: Here's the link to the machines: http://www.polywell.com/us/oem/2700L2D-MxPC.asp
15:36
<championofcyrodi>
dual display is going to cause that to run sluggish
15:36sutula has left IRC (sutula!~sutula@207-118-180-127.dyn.centurytel.net, Quit: ZNC - http://znc.sourceforge.net)
15:36
<championofcyrodi>
Intel® Atom™ Dual-Core D2550, 1.86GHz Processor
15:36PeperPots___ has left IRC (PeperPots___!sid1218@gateway/web/irccloud.com/x-ymfxvcnfspujrhuz, Remote host closed the connection)
15:37
<championofcyrodi>
Application:Vehicle/Boat PC, Set Top Box, Digital Signage, Network Appliance, Traffic Control, Kiosk, POS, Surveillance
15:37
not the ideal workstation.
15:38
<mip5>
Could be - but we've been using them for a few years, and they have been fine. They are much slower now that I'm running 14.0.3. They were running on 12.04.5, and were quite a bit faster. Though they may not be buff, they should be able to run better.
15:38sutula has joined IRC (sutula!~sutula@207-118-180-127.dyn.centurytel.net)
15:39
<championofcyrodi>
I've never seen an Atom perform well. And I believe is about on par with the old AMD-Turion-64-X2, circa 2006
15:39
maybe try xfce
15:39
if youre using unity
15:40
#xubuntu
15:40PeperPots___ has joined IRC (PeperPots___!sid1218@gateway/web/irccloud.com/x-lvnaiwqlhviflbgg)
15:40
<championofcyrodi>
is more lightweight
15:40telex has left IRC (telex!teletype@freeshell.de, Remote host closed the connection)
15:41
<mip5>
right - but they were running much better before, even using unity. I think there's a config issue somewhere. A quick speedtest showed fine download speeds - on par with other devices on the network. I'm thinking it's graphics.
15:42
<championofcyrodi>
X is newer
15:42telex has joined IRC (telex!teletype@freeshell.de)
15:43
<championofcyrodi>
mip5 if you have a budget for it now or later, i recommend something like this: http://www.amazon.com/Intel-D34010WYK-DisplayPort-i3-4010U-Consumer/dp/B00F3F381A
15:43
we have about 30 of them in operation and they work very well.
15:44
the haswell is optimized to perform well with the integrated GPU
15:45
<mip5>
sadly, we're phasing out ltsp clients in favor of chromebooks, as they are more mobile, and work with the online testing that is required by the state and federal governments here in CO. These are the only machines I have, so I need to make them work well.
15:47
<championofcyrodi>
my gov. customers mandate Firefox or IE. nothing else is approved :(
15:48
also wireless is a no go. we could use chrome books for development, but dual monitors is a must have for almost all the developers.
15:48
the display port on the NUC can also push >1080
15:48
resolution.
15:49
also they don't want disks in the workstation, so fat clients w/ 16GB RAM and an i3 are ideal.
15:49
and at $400 per workstation, you can't really beat it.
15:49
(including RAM)
15:50
<mip5>
wow - those sound great.
15:50
Interesting - I just noticed a high load average: 4.88 4.46 2.71
15:51
<championofcyrodi>
that is high
15:51
<mip5>
I've got libreoffice running and chrome, but nothing else
15:51
<championofcyrodi>
chrome can be a hog
15:51
seriously
15:52
<mip5>
Chrome is now off - no difference in load
15:52
<championofcyrodi>
https://www.reddit.com/r/chrome/comments/2vhoea/is_this_normal_memory_use_for_chrome/
15:53
<mip5>
compiz is always at the top of the list in top. Taking about 8% of cpu
15:53
<championofcyrodi>
compiz is a hog too.. i don't think its used in XFCE
15:54
<mip5>
Right - I agree with everything you're saying. The issue is that using chrome and unity in the past has been fine, and now it's quite a bit slower, so something is not right with the current installation.
15:54
<championofcyrodi>
when you click the unity button... is it transparent?
15:55
<mip5>
yeah, and the search window takes about 1 or 2 seconds to appear
15:59
<championofcyrodi>
12.04 -> X.Org X Server 1.11.3
15:59
14.04 -> X.Org X Server 1.15.1
16:01
<mip5>
I'm sure I can make it more efficient. It's very "gluey" It can't just be the newer version
16:03
I think I used to use this line in lts.conf LDM_SESSION="gnome-session --session=ubuntu-2d". It's not in my current environment. I'm going to try that.
16:04
<championofcyrodi>
i was going to say earlier, try ubuntu-2d
16:04
that will disable a lot of the compiz effects
16:05
they version of X also has an impact on the drivers for your GPU
16:05
or rather, the drivers available.
16:05
I couldnt upgrade past 8.10 because my video cards support for X ended.
16:05
(back in the day)
16:05
~2007
16:06
yea intrepid
16:06
i bet 2d will sort things out, and if is your old LDM_SESSION, then likely why it ran smoother berfore.
16:06
i was under the impression you were running 12.04 w/ compiz 3d enabled.
16:07
or rather, OpenGL effects...
16:07
Compiz is an OpenGL compositing manager that use GLX_EXT_texture_from_pixmap for binding redirected top-level windows to texture objects. It has a flexible plug-in system and it is designed to run well on most graphics hardware.
16:09
<mip5>
I'm running 14.04.3. I was actually thinking of using MATE w/out compiz.
16:09
<championofcyrodi>
http://askubuntu.com/questions/34913/what-is-the-difference-between-unity-2d-and-unity-3d
16:12
i think your goal will be to move away from unity-3d/compiz. the 1.9Ghz processor w/o dedicate GPU is probably not enough to get a satisfactory UI experience.
16:12
you really want to save as much as possible for that chrome redering of youtube, etc.
16:17
<mip5>
Can you tell me where I could try that? Using LDM_SESSION="gnome-session --session=ubuntu-2d" didn't make a difference. I don't think I have to rebuild the image for that setting to take place do I? Just a reboot of the client should do it, right?
16:22
sbalneav1: I saw a video regarding mate and ltsp. I'd like to try that, as I prefer mate to unity. Can I specify "mate-desktop" as an option in ltsp-build-client.conf, or would I go into the chroot and install it there, then rebuild the image? Any other method you recommend?
16:25AlexPortable has joined IRC (AlexPortable!uid7568@gateway/web/irccloud.com/x-hdjvtrgvkcyfoybd)
16:25
<mip5>
sbalneav1: I'm using ubuntu 14.0.3. Clients have 2 gbs of ram, atom cpus (dual core).
17:07work_alkisg is now known as alkisg
17:15
<alkisg>
!seen sbalneav1
17:15
<ltsp`>
I have not seen sbalneav1.
17:15
<alkisg>
!seen sbalneav
17:15
<ltsp`>
sbalneav was last seen in #ltsp 36 weeks, 0 days, 19 hours, 2 minutes, and 22 seconds ago: <sbalneav> If we have the "ltsp" user, that would tie in nicely with what I'm trying to accomplish, IF we don't feel that's a security risk.
17:15
<alkisg>
mip5: he hasn't been around lately :)
17:17
<mip5>
alkisg: Thanks! I think I've got it going. Is there a way to specify mate as a build option in ltsp-client-build.conf? mate runs better on these machines than unity, though it's still not as fast to load apps like libreoffice as Steve's do in his video..;)
17:19
<alkisg>
mip5: are you using thin clients or fat clients?
17:19
<mip5>
alkisg: fat clients.
17:20
<alkisg>
So, if you open a terminal, you see something like user@ltsp123?
17:20
Or user@server ?
17:20
<mip5>
yes
17:20
<alkisg>
Which of those two?
17:20
<mip5>
user@ltsp72
17:20
<alkisg>
Well, you can chroot to your chroot and install mate-desktop
17:21
No need to run ltsp-build-client again
17:21
<mip5>
okay - that is what I did, and it worked.
17:21
I set the default session to mate in lts.conf, so that's working too.
17:22
I was just wondering what was the *best* way. It doesn't take too long to build a new client, and sometimes in teh past running updates on the client w/in chroot has yielded errors I was unable to fix, so periodically I have had to rebuild the image
17:23
<alkisg>
!ltsp-pnp
17:23
<ltsp`>
ltsp-pnp: ltsp-pnp is an alternative (upstream) method to maintain LTSP installations for thin and fat clients that doesn't involve chroots: https://help.ubuntu.com/community/UbuntuLTSP/ltsp-pnp
17:23
<alkisg>
That's the best way :)
17:24
<mip5>
Really? okay - if it's the best way, it's time to tackle it! Thanks
17:24
<alkisg>
ltsp-build-client --desktop=something will work as well, but I haven't used that in ages...
17:25
<mip5>
I have two nics on the server, and have seperate vlans for my clients. I assuming that ltsp-pnp can make use of that?
17:26
<alkisg>
Sure, the drawbacks is that the server installation needs to be the same arch (e.g. i386) as the clients, and you shouldn't have too many heavy services on the server without disabling them for the clients with RM_SYSTEM_SERVICES=xxx in lts.conf
17:26
You can also use a VM if you prefer, e.g. virtualbox
17:26
for the "ltsp-pnp server == template client"
17:28
<mip5>
The server is only used for this project, so that's not an issue, and the clients now are 64bit, so that's not an issue either. Will the performance be better, or is it just easier to maintain?
17:31
Just had a crazy issue pop up. The screen got locked - and the password I use to login won't unlock it.
17:34dgroos has joined IRC (dgroos!~dgroos@x-134-84-0-160.vpn.umn.edu)
17:35
<championofcyrodi>
https://pcpartpicker.com/trends/price/internal-hard-drive/
17:35
http://arstechnica.com/gadgets/2015/08/samsung-unveils-2-5-inch-16tb-ssd-the-worlds-largest-hard-drive/
17:35dgroos_ has joined IRC (dgroos_!~dgroos@x-134-84-0-160.vpn.umn.edu)
17:36
<championofcyrodi>
the singularity is getting closer.
17:42
<mip5>
alkisg: is there anyway to disable screen locking for all users?
17:54
<alkisg>
mip5: easier to maintain
17:55
!LDM_PASSWORD_HASH
17:55
<ltsp`>
Error: "LDM_PASSWORD_HASH" is not a valid command.
17:55
<alkisg>
!LDM_HASH_PASSWORD
17:55
<ltsp`>
Error: "LDM_HASH_PASSWORD" is not a valid command.
17:55
<alkisg>
!hash
17:55
<ltsp`>
I do not know about 'hash', but I do know about these similar topics: 'ROOT_PASSWORD_HASH'
17:55
<alkisg>
Meh
17:56
<mip5>
!'ROOT_PASSSWORD_HASH'
17:56
<ltsp`>
Error: "'ROOT_PASSSWORD_HASH'" is not a valid command.
17:56
<mip5>
!'ROOT_PASSWORD_HASH'
17:56
<ltsp`>
Error: "'ROOT_PASSWORD_HASH'" is not a valid command.
17:56
<alkisg>
mip5: set LDM_PASSWORD_HASH=True for the passwords to work
17:56
And use the greek schools ppa to get a recent version for that
17:56
!greek
17:56
<ltsp`>
greek: Στο παρόν κανάλι μιλάνε μόνο Αγγλικά, για υποστήριξη στα Ελληνικά από την υπηρεσία Τεχνικής Στήριξης ΣΕΠΕΗΥ διαβάστε το http://ts.sch.gr/wiki/IRC και στη συνέχεια πληκτρολογήστε /j #ts.sch.gr
17:56
<mip5>
in lts.conf?
17:56
<alkisg>
!greek-schools
17:56
<ltsp`>
I do not know about 'greek-schools', but I do know about these similar topics: 'greek-schools-ppa'
17:56
<alkisg>
!greek-schools-pa
17:56
<ltsp`>
I do not know about 'greek-schools-pa', but I do know about these similar topics: 'greek-schools-ppa'
17:56
<alkisg>
Yes, in lts.conf
17:56
!greek-schools-ppa
17:56
<ltsp`>
greek-schools-ppa: https://launchpad.net/~ts.sch.gr/+archive/ppa/ supports LTS Ubuntu releases with newer LTSP versions, bug fixes etc
17:56
<Phantomas>
:D
18:02
<mip5>
cool - thanks
18:07
<alkisg>
!learn LDM_PASSWORD_HASH as LDM_PASSWORD_HASH=True in lts.conf saves the password hash to /etc/shadow on login, so that the users can unlock the screensaver etc. If they happen to change their password though, that only takes effect until logout.
18:07
<ltsp`>
The operation succeeded.
18:15
<dgroos>
Howdy!
18:15
Am using ltsp-pnp/ on Ubuntu 14.04 (server is 64, clients 32, using pae version on server) Prob: FAT clients don’t boot. I get:
18:16
“Trying to load: pxelinux.cfg/default Could not find kernel image: vmlinuz”
18:16
ideas? There is an image at /opt/ltsp/…
18:17
<alkisg>
!vnc-dide | echo dgroos:
18:17
<ltsp`>
dgroos: vnc-dide: To share your screen with me, run this: sudo apt-get --yes install x11vnc; x11vnc -connect srv1-dide.ioa.sch.gr - this is a reverse connection, it doesn't need port forwarding etc.
18:17
<alkisg>
Hi dgroos
18:17
<dgroos>
:-) alkisg
18:18
alkisg—you help so many people via that route that you’ve turned it into a chat-room command :-) nice
18:18
I’ll get it going…
18:18
<alkisg>
Saves time! :)
18:20
<dgroos>
it’ll be a moment, just finishing re-re-re building image…
18:21
<alkisg>
No worries, I'm looking into systemd units... :-/
18:23
<mip5>
I still can't unlock the screen once it's been locked in my clients. I've added the line LDM_PASSWORD_HASH=True in lts.conf. It's near the bottom, below the LDM_SESSION line. There are no quotes around it. Should there be?
18:23
<alkisg>
mip5: did you use the ppa to your chroot?
18:23
*in
18:24
<mip5>
yes
18:24
and rebuilt the image
18:24
<alkisg>
and in your server?
18:24
<mip5>
yes
18:24
<alkisg>
and apt-get updated etc, right?
18:24
<mip5>
yes
18:24
<alkisg>
Do you have root access to the client? Can you see if it's there in /etc/shadow?
18:24
getent shadow user ==> returns the specific line
18:25
<mip5>
in a terminal?
18:25
on thin client
18:25
<alkisg>
On the thin client, as root, yes
18:25
<mip5>
not sure I've enabled root in thin clients
18:25
<alkisg>
!ROOT_PASSWORD_HASH
18:25
<ltsp`>
ROOT_PASSWORD_HASH: to be able to login as root in vt1, with password "qwer1234", put this in lts.conf: INIT_COMMAND_01="sed 's!^root:[^:]*:!root:$6$p2LdWE6j$PDd1TUzGvvIkj9SE8wbw1gA/MD66tHHlStqi1.qyv860oK47UnKcafSKqGp7cbgZUPlgyPv6giCVyCSCdJt1b0:!' -i /etc/shadow"
18:26
<alkisg>
!SCREEN_02
18:26
<ltsp`>
SCREEN_02: To get a root shell on an Ubuntu thin client: https://help.ubuntu.com/community/UbuntuLTSP/ClientTroubleshooting#Using_a_shell_SCREEN
18:26
<alkisg>
...do one of those
18:28
<dgroos>
alkisg: … there now
18:33
<alkisg>
dgroos, the problem is that you have a separate /boot partition
18:33
Let me get you the bug report...
18:33
https://bugs.launchpad.net/ltsp/+bug/1352038
18:33
<dgroos>
I had tried using that other ltsp-update-image file to, didn’t work.
18:33
<alkisg>
There is a workaround in that bug report
18:33
<dgroos>
Not the file lyou asked people to try?
18:33
<alkisg>
Vagrantc and me uploaded some fixes, but not for 12.04/14.04
18:33
<dgroos>
ahh..
18:33
<alkisg>
It's for older and newer versions :-/
18:34
<dgroos>
of course :_
18:34
<alkisg>
So, for the time being, just do the workaround mentioned there,
18:34
<dgroos>
Cool, will do!
18:34
<alkisg>
and do comment about "please also support overlayfs, 14.04" :)
18:34
<dgroos>
Thanks, and thanks :-)
18:34
will do.
18:34
<alkisg>
dgroos, ah, wait a moment,
18:35
<dgroos>
…?
18:35
<alkisg>
I think there is a version of ltsp-update-image that does support it...
18:35
moment
18:36
Yup, I did put support in the 2648 revision, it was overwritten later on
18:38
dgroos, ping me when ltsp-update-image finishes
18:38
<dgroos>
‘k
18:39
<mip5>
Sorry, but I can't get a prompt on ctrl-alt-F2. I can get one on crtl-alt-F1, and can get back to ctrl-alt-F7. I'm not sure my lts.conf file is being read. Here's a link to my dhcpd.conf file, just in case something is still wrong there: http://pastebin.com/tkPrE5Sn
18:40
<alkisg>
filename "/ltsp/images/amd64.img"; ==> put /ltsp/amd64/lts.conf there
18:41
<mip5>
ok
18:45
;-( still not getting shell on ctrl-alt-f2
18:45
I'm rebooting thin client, but not rebuilding image. That should do it, right?
18:46
wait - I didn't restart dhcp doh!
18:48
got it now. I'll try to lock and unlock the screen
18:49
<alkisg>
dgroos, try rebooting the client
18:50
<dgroos>
did and it said…” …Invalid PBLK length [7]”
18:50
but after a bit it still worked!
18:51
alkisg: it’s not going to be a proxy?
18:51
<alkisg>
depends on what you want
18:51
Now you have eth1=192.168.67.1, which is not the proxy mode
18:52
<dgroos>
that got me into HUGE trouble in my last school :-)
18:52
good, don’t want…
18:52
I’ve got the 2 NIC setup
18:52
<alkisg>
OK, seems fine now
18:53
<dgroos>
Cool, I’ll re-try…
18:56
<mip5>
In trying various things to get graphics better, I've got these in my lts.conf. http://pastebin.com/iQyza6sU - if you do't mind, what should I change?
18:58
I'm getting an error on the desktop now: "Error activating XKB configuration"
18:58
<dgroos>
Works :-) Thanks again :-D Now I can get back to pulling wires in my computer-embedded tables.
18:59
alkisg: and another beer/s…
19:04
<mip5>
That error "Error activating XKB configuration" will through up 20 alerts.
19:05
Also - when I select Applications, the additional menu items don't follow the cursor as I try to select them. After a little while (20 sec) then my cursor is tracked well, and the menu items get highlighted as I pass over them. Any thoughts on this?
19:07
btw - the screen unlocking does work now. Thanks for that.
19:08
<alkisg>
dgroos, you're welcome
19:09
mip5, don't use 16 color depth on fat clients
19:09
<dgroos>
alkisg: will be cloning this setup to 4 other rooms this year.
19:09
<mip5>
ok - should I use 8?
19:09
<alkisg>
mip5: no, leave the default 32 bpp
19:10
<mip5>
oh - ok!
19:10
<alkisg>
I'm not sure that XKBLAYOUT=en is correct, maybe you mean "us"? Is that needed?
19:10
(i.e. don't use X_COLOR_DEPTH at all)
19:10
<mip5>
ok
19:11
<alkisg>
For better graphics, google for exa vs sna etc
19:11
It's probably a graphics driver issue if it was better in previous versions
19:11
Try live usb sticks with various ubuntu releases to see where it "broke"
19:11
<mip5>
okay - does the # sign function as a comment? I'm assuming so, but maybe I'm wrong.
19:11
<alkisg>
Yes
19:11
<mip5>
ok
19:12
the machines have 2 gbs of ram. Should I disable nbd swap? it's set as true
19:12
<alkisg>
Would you use a swap partition if you were doing local installation?
19:12
<mip5>
I always create one - i've heard that it's better that way, so yes.
19:12
<alkisg>
Then, use nbd swap as well
19:13
<mip5>
ah, ok.
19:13
<alkisg>
It depends on your max mem usage
19:13
After a few hours of use, run `free` on a client terminal
19:13
If you see that it has used some swap space, then it needs it, don't disable it
19:13
<mip5>
okay - early results of that show less than half being usd, and no swap
19:14
<gehidore>
swap is always healthy, it allows the kernel to offload boot related items to disk and really maximize caching of 'more than once run' items
19:14
<alkisg>
It doesn't hurt to leave it enabled anyway
19:14
gehidore, in this case both swap and disk == network...
19:14
<gehidore>
alkisg: fair enough
19:14
<alkisg>
(and the nbd disk on the network is cached in the server ram)
19:16
<mip5>
any thoughts on why menus would be so slow to populate?
19:17
<alkisg>
!lan-benchmark
19:17
<ltsp`>
lan-benchmark: If you have a mixed-speed network (gigabit server<=>switch connection, and 100 Mbits/sec clients<=>switch connections), then you might suffer from the !flow-control issue. To benchmark your LAN with epoptes, see http://www.epoptes.org/documentation/lan-benchmark
19:17
<alkisg>
Do check your network in any case...
19:17
Unless it's all gigabit, end to end
19:18
<mip5>
my server is gig to switch, and clients are 100 speed.
19:18
<alkisg>
What network card on the server, and which switch?
19:20
<mip5>
server Intel Corporation 82576 Gigabit Network Connection (rev 01), cisco 3550, with gigbit card
19:20
gigabic
19:21
just double checked clients. They have gigabit ports as well
19:22
But the switch they are connected to (3550) definitely only has 100 etherfast ports.
19:22
<alkisg>
http://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3550/software/release/12-1_19_ea1/configuration/guide/3550scg/swint.html#wp1068564
19:22
Check that ethernet flow control is disabled on the switch
19:22
on the port where the server is connected
19:22
!flowcontrol
19:22
<ltsp`>
I do not know about 'flowcontrol', but I do know about these similar topics: 'flow-control'
19:22
<alkisg>
!flow-control
19:22
<ltsp`>
flow-control: https://help.ubuntu.com/community/UbuntuLTSP/FlowControl
19:24
<mip5>
ok I'll look into that. Thanks.
19:28dgroos_ has left IRC (dgroos_!~dgroos@x-134-84-0-160.vpn.umn.edu)
19:30dgroos has left IRC (dgroos!~dgroos@x-134-84-0-160.vpn.umn.edu, Quit: dgroos)
19:35
<mip5>
well, disabling flowcontrol send on the server interface didn't seem to make a difference
19:37
Overall it's okay. The xkblayout error went away when I used "us" rather than "en" which is good. These machines are used mostly for web browsing and google doc use, so they are probably good enough to go for now.
19:43alkisg is now known as work_alkisg
19:52
<mip5>
work_alkisg: I'll try to set up the pnp version of ltsp when I get the chance. Thanks for all your help the past couple of days.
20:06ricotz has left IRC (ricotz!~rico@ubuntu/member/ricotz, Quit: Ex-Chat)
20:12mip5 has left IRC (mip5!~chatzilla@208.72.71.69, Ping timeout: 250 seconds)
20:20dgroos has joined IRC (dgroos!~dgroos@x-134-84-0-160.vpn.umn.edu)
20:40pppingme has left IRC (pppingme!~pppingme@unaffiliated/pppingme, Ping timeout: 250 seconds)
20:46mip5 has joined IRC (mip5!~chatzilla@208.72.71.69)
20:57dgroos has left IRC (dgroos!~dgroos@x-134-84-0-160.vpn.umn.edu, Quit: dgroos)
20:58Faith has left IRC (Faith!~paty@unaffiliated/faith, Quit: Saindo)
21:18pppingme has joined IRC (pppingme!~pppingme@cpe-24-166-185-43.kc.res.rr.com)
21:18pppingme has joined IRC (pppingme!~pppingme@unaffiliated/pppingme)
21:47mip5 has left IRC (mip5!~chatzilla@208.72.71.69)
22:39gehidore has left IRC (gehidore!~username@unaffiliated/man, Quit: WeeChat 1.2)
22:39gehidore has joined IRC (gehidore!~username@unaffiliated/man)
22:45Ark74 has joined IRC (Ark74!~Ark74@189.220.255.72.cable.dyn.cableonline.com.mx)
22:48pppingme has left IRC (pppingme!~pppingme@unaffiliated/pppingme, Ping timeout: 272 seconds)
23:01telex has left IRC (telex!teletype@freeshell.de, Remote host closed the connection)
23:01gehidore is now known as man
23:02man is now known as gehidore
23:02telex has joined IRC (telex!teletype@freeshell.de)
23:06pppingme has joined IRC (pppingme!~pppingme@unaffiliated/pppingme)
23:17ben_roose has left IRC (ben_roose!~roose@156.26.10.48, Remote host closed the connection)