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


Channel log from 2 March 2011   (all times are UTC)

00:52alkisg (~alkisg@ubuntu/member/alkisg) joined #ltsp.
00:53alkisg (~alkisg@ubuntu/member/alkisg) left irc: Read error: Connection reset by peer
00:53alkisg1 (~alkisg@ubuntu/member/alkisg) joined #ltsp.
01:03alkisg1 (~alkisg@ubuntu/member/alkisg) left irc: Ping timeout: 240 seconds
01:08alkisg1 (~alkisg@ubuntu/member/alkisg) joined #ltsp.
01:08alkisg1 (~alkisg@ubuntu/member/alkisg) left irc: Client Quit
01:12alkisg (~alkisg@ubuntu/member/alkisg) joined #ltsp.
01:29
<alkisg>
!xauthority
01:30
<ltspbot`>
alkisg: "xauthority" :: to access the client X session from a local root shell, try: eval $(tr '\0' '\n' < /proc/$(pidof -s ldm gdm-simple-greeter gnome-session | cut -d' ' -f1)/environ | egrep '^DISPLAY=|^XAUTHORITY=') && export DISPLAY XAUTHORITY
01:31
<muppis>
alkisg, why you don't make an alias for that?
01:32
<alkisg>
muppis: on all different computers that I sit on? how?
01:33
<muppis>
alkisg, once for all chroot's.
01:33
<alkisg>
No I mean that e.g. I go to 5 different schools to support etc
01:34
So I don't have access to their chroots before I go there...
01:34
For my own pc, I do have scripts in ~/bin to automate stuff
01:35
<muppis>
I meant for possible future use.
02:28shawnp0wers (~spowers@linuxjournal/staff/shawnp0wers) left irc: Quit: Leaving.
02:34dobber (~dobber@89.190.197.77) joined #ltsp.
03:02komunista (~slavko@adsl-195-098-017-177.dynamic.nextra.sk) joined #ltsp.
03:02gypsymauro (~colorioma@84.18.151.77) joined #ltsp.
03:02
<gypsymauro>
hi
03:03
<komunista>
hi ;-)
03:03
<gypsymauro>
there is a way to connect to an ltsp server from a client using something like rdesktop? using a Xnest -query maybe?
03:04
hi komunista
03:04
:)
03:06bobby_C (~bobby@85-124-22-227.teleworker.xdsl-line.inode.at) joined #ltsp.
03:07
<komunista>
gypsymauro: IMHO yes, but some tweaking will be needed - because default LTSP uses ssh autentification
03:07
<gypsymauro>
I c
03:08
<komunista>
you will need allow X connections or some like this
03:11
<gypsymauro>
komunista: I was searching something like ..rdesktop :)
03:14
<komunista>
this http://kangkam.blogspot.com/2008/05/tutorial-konfigurasi-ltsp-dan-rdesktop.html ?
03:14
it is a first link from google...
03:14
<gypsymauro>
not exactly
03:15
<komunista>
and what you want?
03:15
<gypsymauro>
nevermind, I'm running ltsp server on ubuntu, there is a way to lock down users? for example removing desktop background, desktop effects and so on?
03:16
komunista: I was meaning, with rdesktop you can connect directly to a windows TS from a client, suppose I've already my linux desktop, but I want to deploy some applications with LTSP, there is a way to connect using a single command to LTSP server ?
03:16
<komunista>
some days agou a read some article about locking clients from server by screensaver - I have not link
03:17
but you can try the italc, it is documented in ubuntu wiki
03:18
<alkisg>
gypsymauro: you mean, to connect to an ltsp server from another linux machine?
03:18
You can use vnc or neatx-server for that
03:19* alkisg prefers neatx-server, faster and easier to install, no configuration needed
03:20
<gypsymauro>
alkisg: in fact, I was thinking about that :) do you have news about neatx? I know that nx will be closed source from 4
03:21
<alkisg>
You mean the nomachine nx server? Isn't it already closed source?
03:21
The freenx and the neatx servers are open source though, so I don't think they can be closed source
03:22
<gypsymauro>
yes nomachine one
03:22
<alkisg>
It's already closed source
03:22
<gypsymauro>
I know but it seems a dead project
03:22
the free one I mean
03:22
<alkisg>
neatx isn't actively developed, sure, but it works, and receives updates now and then
03:22
freenx is more actively developed, it's just a bit more hassle to configure it
03:23
<elias_a>
alkisg: Speaking of freenx - what ports does it use for communication? OpenMeetings uses it for screenshare and we bumped into some problems.
03:23
alkisg: Or maybe this is a trivial google it yourself type of question...
03:23
<alkisg>
gypsymauro: nx is the best option currently, much faster than vnc or anything else I tried. So I'm using it. If it ever breaks in the future, i'll search then for any alternatives :)
03:23
elias_a: it works over ssh, so port 22
03:24
<elias_a>
alkisg: Thanks!
03:24
<komunista>
to connect LTSP server from my Windows workstation I am using NX - FreeNX combination
03:30Gremble (~Ben@cpc12-aztw24-2-0-cust146.aztw.cable.virginmedia.com) joined #ltsp.
03:31alkisg (~alkisg@ubuntu/member/alkisg) left irc: Quit: Leaving.
03:31Gremble (~Ben@cpc12-aztw24-2-0-cust146.aztw.cable.virginmedia.com) left irc: Client Quit
03:32
<gypsymauro>
komunista: what kind of combination? why not all freenx?
03:34
<komunista>
freenx is server solution
03:34
and as client I am suing official NX software - with no exact reason
03:36
but official NX client is simplest way for Windows systems
03:37
<sep>
komunista, there is also something called x2go you can test using nx libsm just like freenx
03:37
<komunista>
yes, I tried it
03:37
it works
03:38
but I tried it only from Linux workstation
03:38
freenx is working for me more than 1.5 year without any problem
03:40
I was tried the NX client as localapps on thin client too - by some problems with slow kicad (solved now by new version of kicad)
03:44
<gypsymauro>
kicad?
03:48artista_frustrad (~artista_f@200-96-4-175.ctaje701.dsl.brasiltelecom.net.br) joined #ltsp.
03:59markit (~marco@adsl-156-149.38-151.net24.it) joined #ltsp.
04:01
<markit>
hi, is it normal that for each user connected (thin client), "who" shows 2 entries, only one with the IP resolved in the name (I've entries in /etc/hosts)? Like: gfassina pts/1 2011-03-02 11:11 (ltsp108) ANDgfassina pts/2 2011-03-02 11:12 (192.168.20.108:7)
04:10garymc (~chatzilla@host81-148-15-59.in-addr.btopenworld.com) joined #ltsp.
04:12
<komunista>
gypsymauro: kicad is software for electric schemas and PCBs development - I am teacher on electrical school
04:13
<gypsymauro>
great komunista :) it's so rare to find teachers that loves FLOSS
04:19
<komunista>
gypsymauro: I love my wife and daughters - FOSS I am using only :-)
04:25
<markit>
komunista: great!
04:25
<gypsymauro>
komunista: :)
04:36
<komunista>
and (to be more exact) I contribute too... ;-)
04:57alkisg (~alkisg@ubuntu/member/alkisg) joined #ltsp.
05:13
<alkisg>
Hi, I'm trying to `apt-get dist-upgrade` a natty chroot, and apport fails to be configured. In /var/log/daemon.log I get:
05:13
Mar 2 14:11:11 alkis init: apport pre-start process (15957) terminated with status 1
05:13
Mar 2 14:11:11 alkis init: apport post-stop process (15958) terminated with status 1
05:14
In apport.postinst there is this call, added by dh_installinit:
05:14
invoke-rc.d apport start || exit $?
05:14litlebuda (~litlebuda@144.178.108.93.rev.vodafone.pt) joined #ltsp.
05:15
<alkisg>
So the question is, should that invoke-rc.d call succeed, or should the postinst have an `|| true` at that line?
05:16
Heh. Wrong channel. Ignore me :)
05:36gnunux (~emmanuel@194.167.18.244) joined #ltsp.
05:38MorningSon (~MorningSo@cpe-70-114-21-95.satx.res.rr.com) joined #ltsp.
06:07
<alkisg>
Maybe we can replace "LTSP_HANDLE_DAEMONS" with an "in_chroot()" call which would automatically take care of invoke-rc.d?
06:07
http://paste.ubuntu.com/574434/
06:35gypsymauro (~colorioma@84.18.151.77) left irc: Quit: leaving
06:39drdata (~drdata@pool-173-57-189-158.dllstx.fios.verizon.net) left irc: Remote host closed the connection
06:39drdata (~drdata@pool-173-57-189-158.dllstx.fios.verizon.net) joined #ltsp.
06:43alkisg (~alkisg@ubuntu/member/alkisg) left irc: Quit: Leaving.
06:46alkisg (~alkisg@ubuntu/member/alkisg) joined #ltsp.
06:50alkisg (~alkisg@ubuntu/member/alkisg) left irc: Client Quit
06:51
<Naranek>
Any pointers to getting sudo to work on a ltsp-client? I've tried editing /etc/sudoers on server and chroot jail, but it doesn't help. Googling is also hard, because the hits seem to be about using sudo in installing the ltsp server
06:52uday (foobar@117.200.179.108) joined #ltsp.
06:52alkisg (~alkisg@ubuntu/member/alkisg) joined #ltsp.
06:57garymc (~chatzilla@host81-148-15-59.in-addr.btopenworld.com) left irc: Quit: ChatZilla 0.9.86 [Firefox 3.6.13/20101203074432]
07:03
<markit>
Naranek: I remember there are info about enable root access from clients
07:04
with something like chroot, add password to root, reboot the client, etc
07:04
don't know if this helps
07:04
<Naranek>
thanks. I would like to have it done without enabling the root password
07:04
<alkisg>
Naranek: sudo should work fine on ltsp clients
07:04
Or are you talking about fat clients?
07:05
<Naranek>
fat clients indeed
07:05
<alkisg>
OK, can we start with "what do you need sudo for, on fat clients"?
07:05
Because there are *many* misconceptions there
07:06
<Naranek>
I want to test changing the swappiness setting on a single computer before applying it for everyone
07:06
<alkisg>
OK, testing is indeed a good reason
07:06
!SCREEN_02
07:06
<ltspbot`>
alkisg: "SCREEN_02" :: to get a root shell on an Ubuntu thin client: https://help.ubuntu.com/community/UbuntuLTSP/ClientTroubleshooting#Using%20a%20shell%20SCREEN
07:06
<alkisg>
You can test swappiness from SCREEN_02=shell, so no need for sudo
07:06
<Naranek>
Thanks. I'll try that.
07:06
<alkisg>
You can only do that for the specific client where you sit
07:07
By a [mac:address] lts.conf section
07:07
<Naranek>
yeah. I actually tried that before, but it didn't work because I had borked some other settings, which I only found out later. better try that again :)
07:07
thanks for the help
07:07
<alkisg>
np
07:25
<markit>
alkisg: what kind of misconception? I'm trying (if my school buys some pc) to "migrate" to fat clients soon
07:26
<alkisg>
markit: many people are trying to use `sudo` to do stuff on fat clients that should be done on the server chroot instead
07:26
E.g. installing / updating programs or putting mandatory gconf settings
07:27
I've yet to find a useful case for using sudo on fat clients, where SCREEN_02 doesn't suffice
07:27
<markit>
I see... so for fat clients you have the "fat chroot" and you have to act there like you do in "thin chroot", correct?
07:28
btw, is it normal that for each user connected (thin client), "who" shows 2 entries, only one with the IP resolved in the name (I've entries in /etc/hosts)? Like: "gfassina pts/1 2011-03-02 11:11 (ltsp108)" AND "gfassina pts/2 2011-03-02 11:12 (192.168.20.108:7) "
07:30
<alkisg>
Yeah I think we can easily avoid one of them by modifying a bit ldm.c, but I can't easily test the upstream code right now so I'm hoping some other dev can test + commit it
07:30
I.e. instead of running `echo LTSPROCKS; /bin/sh` to run `echo LTSPROCKS; exec /bin/sh`
07:32
<markit>
alkisg: ok, in any case don't understand why one has the name, the other only the IP, if, just in case you have to patch code, is relevant for you
07:33
<alkisg>
I guess in the first case a dns resolution happens while it doesn't on the second case, I don't think it's anything to concern yourself about
07:33
<markit>
thanks
07:40RiXtEr (~blah@69-179-107-137.dyn.centurytel.net) left irc: Ping timeout: 240 seconds
07:41RiXtEr (~blah@69-179-104-85.dyn.centurytel.net) joined #ltsp.
07:52Gadi (~romm@ool-18bbe47a.static.optonline.net) joined #ltsp.
08:17uday (foobar@117.200.179.108) left irc: Ping timeout: 264 seconds
09:00litlebuda (~litlebuda@144.178.108.93.rev.vodafone.pt) left irc: Ping timeout: 246 seconds
09:06Gremble (~Ben@cpc12-aztw24-2-0-cust146.aztw.cable.virginmedia.com) joined #ltsp.
09:18staffencasa (~staffenca@128-193-148-151.oregonstate.edu) joined #ltsp.
09:21Gremble (~Ben@cpc12-aztw24-2-0-cust146.aztw.cable.virginmedia.com) left irc: Quit: I Leave
09:22gnunux (~emmanuel@194.167.18.244) left irc: Quit: Ex-Chat
09:30alkisg (~alkisg@ubuntu/member/alkisg) left irc: Ping timeout: 252 seconds
09:39drdata (~drdata@pool-173-57-189-158.dllstx.fios.verizon.net) left irc: Ping timeout: 240 seconds
09:46Trixboxer (~Trixboxer@office.supportdepartment.net) joined #ltsp.
09:49uday (foobar@117.200.183.194) joined #ltsp.
10:03markit (marco@adsl-156-149.38-151.net24.it) left #ltsp ("Konversation terminated!").
10:10bieb (~hbieber@gw1.johnmarshall.edu) joined #ltsp.
10:27uday (foobar@117.200.183.194) left irc: Quit: Ex-Chat
10:29Nick change: zz_evil_root -> evil_root
10:35toscalix (~toscalix@77.208.125.101) joined #ltsp.
10:47drdata (~drdata@tw2.udallas.edu) joined #ltsp.
10:59drdata (~drdata@tw2.udallas.edu) left irc: Ping timeout: 240 seconds
11:27dobber (~dobber@89.190.197.77) left irc: Remote host closed the connection
11:32alkisg (~alkisg@ubuntu/member/alkisg) joined #ltsp.
11:33shawnp0wers (~Adium@24-247-230-102.static.trcy.mi.charter.com) joined #ltsp.
11:33shawnp0wers (~Adium@24-247-230-102.static.trcy.mi.charter.com) left irc: Changing host
11:33shawnp0wers (~Adium@linuxjournal/staff/shawnp0wers) joined #ltsp.
11:44Nick change: evil_root -> zz_evil_root
11:48patrickmw (~pwright@ip68-231-4-153.ph.ph.cox.net) left irc: Quit: Ex-Chat
12:00Kicer86 (~Kicer86@host-5db0eeee.sileman.net.pl) joined #ltsp.
12:04toscalix (~toscalix@77.208.125.101) left irc: Remote host closed the connection
12:04Gremble (~Ben@cpc12-aztw24-2-0-cust146.aztw.cable.virginmedia.com) joined #ltsp.
12:08Nick change: leio_ -> leio
12:16jhutchins_lt (~jonathan@64-151-37-66.dyn.everestkc.net) left irc: Ping timeout: 246 seconds
12:17jhutchins_lt (~jonathan@64-151-37-66.dyn.everestkc.net) joined #ltsp.
12:20drdata (~drdata@tw2.udallas.edu) joined #ltsp.
12:26patrickmw (~pwright@ip68-231-4-153.ph.ph.cox.net) joined #ltsp.
12:36patrickmw (~pwright@ip68-231-4-153.ph.ph.cox.net) left irc: Quit: Ex-Chat
12:39patrickmw (~pwright@ip68-231-4-153.ph.ph.cox.net) joined #ltsp.
12:55ogra (~ogra@ubuntu/member/ogra) left irc: Excess Flood
12:56ogra (~ogra@p5098ed03.dip0.t-ipconnect.de) joined #ltsp.
12:56Nick change: ogra -> Guest42737
12:57Nick change: Guest42737 -> ogra_
12:57ogra_ (~ogra@p5098ed03.dip0.t-ipconnect.de) left irc: Changing host
12:57ogra_ (~ogra@ubuntu/member/ogra) joined #ltsp.
12:58shawnp0wers (~Adium@linuxjournal/staff/shawnp0wers) left irc: Quit: Leaving.
12:59patrickmw (~pwright@ip68-231-4-153.ph.ph.cox.net) left irc: Read error: Connection reset by peer
13:04patrickmw (~pwright@ip68-231-4-153.ph.ph.cox.net) joined #ltsp.
13:25Nick change: zz_evil_root -> evil_root
13:25RiXtEr (~blah@69-179-104-85.dyn.centurytel.net) left irc: Ping timeout: 272 seconds
13:26RiXtEr (~blah@99-195-111-131.dyn.centurytel.net) joined #ltsp.
13:35Gremble (~Ben@cpc12-aztw24-2-0-cust146.aztw.cable.virginmedia.com) left irc: Quit: I Leave
13:42Gadi (romm@ool-18bbe47a.static.optonline.net) left #ltsp.
14:02komunista (~slavko@adsl-195-098-017-177.dynamic.nextra.sk) left irc: Quit: Leaving.
14:03bieb (hbieber@gw1.johnmarshall.edu) left #ltsp.
14:24RiXtEr (~blah@99-195-111-131.dyn.centurytel.net) left irc: Ping timeout: 240 seconds
14:25RiXtEr (~blah@75-121-253-78.dyn.centurytel.net) joined #ltsp.
14:34Kicer86 (~Kicer86@host-5db0eeee.sileman.net.pl) left irc: Quit: KVIrc Insomnia 4.0.2, revision: 4740, sources date: 20100627, built on: 2010-08-08 18:29:00 UTC http://www.kvirc.net/
15:02vagrantc (~vagrant@75-150-46-245-Oregon.hfc.comcastbusiness.net) joined #ltsp.
15:02pingpangqui (~pingpong@ip-178-200-55-107.unitymediagroup.de) joined #ltsp.
15:03
<pingpangqui>
Hi
15:04
<alkisg>
vagrantc: can we replace policy-rc.d with this one? http://paste.ubuntu.com/574434/ - it's supposed to work automatically, without having to manually set LTSP_HANDLE_DAEMONS...
15:04
<pingpangqui>
I have a strange problem: when I try to login via ldm it seems to work but ends up at the ldm login screen
15:05
did anyone have had a similar experience
15:05
<vagrantc>
alkisg: if it works consistantly on all architectures...
15:05
er, distros
15:06
<pingpangqui>
oh this might of concern: I'm using debian squeeze
15:07Trixboxer (~Trixboxer@office.supportdepartment.net) left irc: Quit: "Achievement is not the end, its the beginning of new journey !!!"
15:07
<alkisg>
vagrantc: erm, do other distros have policy-rc.d? I don't think it will work on non-linux architectures though, as it uses /proc - I've no idea if that is available on freebsd kernels etc
15:07
<vagrantc>
ah
15:07
alkisg: well, we also mess with start-stop-daemon directly, if something doesn't respect policy-rc.d
15:07
which i think is in other distros
15:07
not that they necessarily use it
15:08
<alkisg>
(but btw we 're using /proc a lot in the code, so I don't suppose that would be a problem)
15:09
pingpangqui: do you get an entry in /var/log/auth.log ?
15:12
<pingpangqui>
hm I can't find such an file in the chroot environment
15:12
or should it be on the server?
15:12
<alkisg>
Server
15:14
<pingpangqui>
thats what I get:
15:14
Mar 2 22:59:26 debian sshd[5028]: Accepted password for swi from 192.168.2.20 port 46696 ssh2
15:14
Mar 2 22:59:26 debian sshd[5028]: pam_unix(sshd:session): session opened for user swi by (uid=0)
15:14
Mar 2 22:59:27 debian sshd[5033]: subsystem request for sftp
15:14
Mar 2 22:59:27 debian sshd[5033]: Received disconnect from 192.168.2.20: 11: disconnected by user
15:14
Mar 2 22:59:27 debian sshd[5028]: pam_unix(sshd:session): session closed for user swi
15:14
<alkisg>
OK, try this:
15:14
!compiz
15:14
<ltspbot`>
alkisg: "compiz" :: the default window manager in gnome is gnome-wm, which automatically chooses compiz if it thinks that the card supports it. Compiz is causing login problems to some clients (LP #673072). To disable it, see !disable_compiz. To restore it, see !restore_compiz
15:16
<alkisg>
vagrantc: also, if you're testing the new ldm, (I'll be testing it for 12.04, after 1 year :)), this "exec" should save us a bash for each connected user: src/plugins/ssh/ssh.c: sshinfo->server, "echo " SENTINEL "; exec /bin/sh -", NULL);
15:18
<pingpangqui>
well, it seem compiz isn't even installed on my system
15:18
so that can't be the problem
15:19
<alkisg>
pingpangqui: dpkg-query -W compiz-core
15:20
<pingpangqui>
"no package found" (free translation from german)
15:20
login also fails using twm
15:21
<alkisg>
OK, it's not that then, it's another problem
15:21
(the compiz problem is too common, that's why I suggested it first)
15:21
<pingpangqui>
that sok
15:21
<alkisg>
Check that user's ~/.xsession-errors
15:21
<vagrantc>
alkisg: do they show up with "who" or "w" ?
15:22
<alkisg>
vagrantc: not sure, but I don't think having an extra bash makes any difference on that
15:23* alkisg checks...
15:23
<pingpangqui>
besides lots of: (firefox-bin:4483): Gdk-WARNING **: XID collision, trouble ahead
15:24
I found:
15:24
Cannot connect to server socket err = Datei oder Verzeichnis nicht gefunden
15:24
Cannot connect to server socket
15:24
jack server is not running or cannot be started
15:24
Cannot connect to server socket err = Datei oder Verzeichnis nicht gefunden
15:24
Cannot connect to server socket
15:24
jack server is not running or cannot be started
15:25
"Datei oder Verzeichnis nicht gefunden" means "file or path not found"
15:26
<alkisg>
Jack? Doesn't debian use pulseaudio on thin clients?
15:26* vagrantc nods
15:26
<vagrantc>
thought it generally requires some manual configuration
15:26
see /usr/share/doc/ltsp-server/README.Debian.*
15:28
<pingpangqui>
well I suppose whether jack fails shouldn't be a problem for the display, I guess.
15:29
<alkisg>
vagrantc: I think the result on "w/who" comes from launch-ck-session, called by xsession, so it's not related to the ssh connection
15:29
<pingpangqui>
Maybe this might be important: server is an amd64 system and the client an x86 (geode cpu)
15:29* alkisg checks with a fat client...
15:30
<alkisg>
pingpangqui: do other clients have the same problem? Can you try with XSERVER=vesa in lts.conf?
15:30
<pingpangqui>
yes a client with a via cpu has the same problem
15:31
I dont have others than that
15:32
<alkisg>
Hm. Nope, fat client users also show up in "who"
15:33
<pingpangqui>
I played already aroud with lts.conf in chroot and also created a new one in /var/lib/tftpboot/ltsp/i386 with the following content
15:33
[here is my clients mac adress]
15:34
LTSP_CONFIG = True
15:34
XSERVER = geode
15:34
X_RAMPERC = 80
15:34
LDM_DIRECTX = True
15:34
X_MODE_0 = 640x480root@debian:/var/lib/tftpboot/ltsp/i386
15:34
the last line is wrong ofcourse
15:34
ignore everything after x480
15:35
strangly the resolution on the ldm login is still 1024x 768
15:36
I'll try the vesa option though
15:37
but I'm not sure whether the files are actually considered
15:38
at least it doesn't seem so
15:38
<alkisg>
`getltscfg -a` from the client will tell you that
15:38
!SCREEN_08
15:38
<ltspbot`>
alkisg: "SCREEN_08" :: To get a root shell on a Debian thin client, put SCREEN_07=ldm, SCREEN_08=shell and SCREEN_DEFAULT=07 to lts.conf.
15:40
<pingpangqui>
ok I will do so tomorrow. Since I can't get access to the clients (Family is sleeping)
15:42
by the way do you know whether debian is using nfs or nbd by default?
15:42
both seem to be installed
15:42
<alkisg>
vagrantc: ah got it. It's the `ssh -t` option which makes them appear in `w`
15:43
So: ssh user@localhost /bin/sh ==> doesn't appear
15:43
<pingpangqui>
is this a problem ?
15:43
<alkisg>
vagrantc: ssh -t user@localhost /bin/sh ==> appears
15:43
The "exec" part shouldn't make any difference at all
15:43
pingpangqui: it's using nfs by default
15:44
<pingpangqui>
but ndb was automatically installed too
15:44
well strange
15:44drdata (~drdata@tw2.udallas.edu) left irc: Ping timeout: 250 seconds
15:44
<alkisg>
Maybe for swap, if you need it
15:44
(network swap)
15:44
<pingpangqui>
ok
15:45
could nfs be the problem=
15:45
?
15:45
<alkisg>
I don't think so, since it boots
15:45
<pingpangqui>
hm ok
15:46
Ok thanks for Your help so far
15:47
I'll give it another try tomorrow
15:47
<alkisg>
np. Good night all
15:47alkisg (~alkisg@ubuntu/member/alkisg) left irc: Quit: Leaving.
15:47
<pingpangqui>
good night
15:52pingpangqui (pingpong@ip-178-200-55-107.unitymediagroup.de) left #ltsp.
16:12artista_frustrad (~artista_f@200-96-4-175.ctaje701.dsl.brasiltelecom.net.br) left irc: Ping timeout: 276 seconds
16:25artista_frustrad (~artista_f@200-96-4-175.ctaje701.dsl.brasiltelecom.net.br) joined #ltsp.
16:30artista_frustrad (~artista_f@200-96-4-175.ctaje701.dsl.brasiltelecom.net.br) left irc: Ping timeout: 250 seconds
16:38RiXtEr (~blah@75-121-253-78.dyn.centurytel.net) left irc: Ping timeout: 276 seconds
16:38RiXtEr (~blah@75-121-253-78.dyn.centurytel.net) joined #ltsp.
16:42artista_frustrad (~artista_f@200-96-4-175.ctaje701.dsl.brasiltelecom.net.br) joined #ltsp.
17:23bobby_C (~bobby@85-124-22-227.teleworker.xdsl-line.inode.at) left irc: Ping timeout: 252 seconds
17:34jhutchins_lt (~jonathan@64-151-37-66.dyn.everestkc.net) left irc: Ping timeout: 272 seconds
17:36patrickmw (~pwright@ip68-231-4-153.ph.ph.cox.net) left irc: Quit: Ex-Chat
17:44staffencasa (~staffenca@128-193-148-151.oregonstate.edu) left irc: Quit: Leaving
17:56Nick change: evil_root -> zz_evil_root
18:39vagrantc (~vagrant@75-150-46-245-Oregon.hfc.comcastbusiness.net) got netsplit.
18:39zz_evil_root (~evil@host-98-127-40-50.bln-mt.client.bresnan.net) got netsplit.
18:43zz_evil_root (~evil@host-98-127-40-50.bln-mt.client.bresnan.net) returned to #ltsp.
18:45zz_evil_root (~evil@host-98-127-40-50.bln-mt.client.bresnan.net) got netsplit.
18:50vagrantc (~vagrant@75-150-46-245-Oregon.hfc.comcastbusiness.net) got lost in the net-split.
18:51zz_evil_root (~evil@host-98-127-40-50.bln-mt.client.bresnan.net) returned to #ltsp.
19:05Nick change: zz_evil_root -> evil_root
19:19Nick change: evil_root -> zz_evil_root
20:19artista_frustrad (~artista_f@200-96-4-175.ctaje701.dsl.brasiltelecom.net.br) left irc: Quit: Leaving
21:15drdata (~drdata@pool-173-57-189-158.dllstx.fios.verizon.net) joined #ltsp.
21:25MorningSon (~MorningSo@cpe-70-114-21-95.satx.res.rr.com) left irc: Quit: WeeChat 0.3.0
22:09mutex_ (~mutex@67-23-13-54.static.slicehost.net) joined #ltsp.
22:10mutex (~mutex@67-23-13-54.static.slicehost.net) left irc: Ping timeout: 240 seconds
22:14mistik1 (mistik1@unaffiliated/mistik1) left irc: Read error: Connection reset by peer
22:14mistik1 (mistik1@unaffiliated/mistik1) joined #ltsp.
23:01mutex_ (~mutex@67-23-13-54.static.slicehost.net) left irc: Read error: Connection reset by peer
23:08alkisg (~alkisg@ubuntu/member/alkisg) joined #ltsp.
23:48alkisg (~alkisg@ubuntu/member/alkisg) left irc: Quit: Leaving.
00:00--- Thu Mar 3 2011