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


Channel log from 5 September 2011   (all times are UTC)

00:00
<TheMatrix3000>
hey parket
00:00
parker*
00:00
<Parker955>
ehh matrix
00:01
<TheMatrix3000>
how would you go about restarting gnome-panel on ltsp
00:01
for fat clients and thin clients
00:01
<Parker955>
no clue :)
00:01
hell no idea why I'm in here since I only played with ltsp for like 2 nights haha
00:01
<TheMatrix3000>
ha
00:07bakytn has left IRC (bakytn!~bakytn@airport.kg, Quit: Leaving)
00:13netwareru has left IRC (netwareru!~netwareru@213.115.13.181, Ping timeout: 258 seconds)
01:41artista-frustrad has joined IRC (artista-frustrad!~fernando@201-14-24-109.ctame704.dsl.brasiltelecom.net.br)
01:57staffencasa has left IRC (staffencasa!~staffenca@128-193-147-197.oregonstate.edu, Ping timeout: 260 seconds)
02:38petre has joined IRC (petre!~petre@scheie.homedns.org)
03:04petre has left IRC (petre!~petre@scheie.homedns.org, Quit: Leaving)
03:12Parker955 is now known as Parker955_Away
03:12leio_ has joined IRC (leio_!~leio@gentoo/developer/leio)
03:13leio has left IRC (leio!~leio@gentoo/developer/leio, Ping timeout: 252 seconds)
03:46Parker955_Away is now known as Parker955
05:13alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg)
05:43staffencasa has joined IRC (staffencasa!~staffenca@128-193-144-211.oregonstate.edu)
05:57Parker955 is now known as Parker955_Away
06:31Selveste1 has left IRC (Selveste1!~Selveste1@31.25.23.230, Ping timeout: 240 seconds)
06:32Selveste1 has joined IRC (Selveste1!~Selveste1@0125600186.0.fullrate.dk)
06:39ddave7 has joined IRC (ddave7!~Miranda@109-183-234-74.tmcz.cz)
06:44ddave7 has left IRC (ddave7!~Miranda@109-183-234-74.tmcz.cz, Read error: Connection reset by peer)
06:53ddave7 has joined IRC (ddave7!~Miranda@109-183-25-67.tmcz.cz)
07:16Selveste1 has left IRC (Selveste1!~Selveste1@0125600186.0.fullrate.dk, Read error: Operation timed out)
07:34bobby_C has joined IRC (bobby_C!~bobby@85-124-22-227.teleworker.xdsl-line.inode.at)
07:49toscalix has joined IRC (toscalix!~toscalix@76.Red-88-12-65.dynamicIP.rima-tde.net)
08:19leio_ has left IRC (leio_!~leio@gentoo/developer/leio, Read error: Operation timed out)
08:21cyberorg has joined IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg)
08:28leio has joined IRC (leio!~leio@gentoo/developer/leio)
08:33Selveste1 has joined IRC (Selveste1!~Selveste1@31.25.23.230)
08:38toscalix has left IRC (toscalix!~toscalix@76.Red-88-12-65.dynamicIP.rima-tde.net, Read error: No route to host)
08:39toscalix has joined IRC (toscalix!~toscalix@76.Red-88-12-65.dynamicIP.rima-tde.net)
08:50
<vlt>
Hello. On gdm I get "Keine Antwort des Server. Neustart ..." (translates to "server not responding. restart ...") after one specific user tries to login. Access via ssh on the LTSP server is possible. Any idea how to debug this?
08:52
<alkisg>
vlt: "after one specific user tries to login." => with a specific user? or that happens with all users?
08:53
<vlt>
alkisg: Not all users. But at least three users I tried.
08:53
<alkisg>
vlt: so there's at least one user that *can* login?
08:53
<vlt>
alkisg: Yes.
08:54
alkisg: At least 4, actually.
08:54
<alkisg>
That's very strange. If no user could log in it would make sense, but not now.
08:54
See your server's /var/log/auth.log, do you see failed login entries?
08:54
<vlt>
alkisg: I tried different clients. No difference.
08:55
<alkisg>
vlt: and you're *SURE* that some users can login, and other users cannot?
08:55
Or is it possible that no user can login?
08:57
<vlt>
alkisg: I'm *SURE* that some users can login, even on that client.
08:57
<alkisg>
OK
08:57
(11:54:41 πμ) alkisg: See your server's /var/log/auth.log, do you see failed login entries?
08:57
<vlt>
alkisg: "getent passwd" lists the users, and they can login via ssh
08:57
<alkisg>
I'm not talking about that
08:58
I'm asking this: can at least one user login with ldm now?
08:58
<vlt>
alkisg: Yes.
08:58
<alkisg>
OK
08:58
Go on with checking auth.log
08:58
<vlt>
alkisg: I meant, even the users that fail can login via ssh.
08:58
<alkisg>
I understand
08:58
Do you see failed login entries in the server's /var/log/auth.log?
08:59
(or whatever else your distro uses for authentication logging)
08:59
Which distro/version are you using btw?
09:00
<vlt>
alkisg: Ubuntu 10.04 LTS
09:00
alkisg: auth.log: http://pastebin.com/ttJK3ZY0
09:01
<alkisg>
Sep 5 10:46:56 glitter sshd[10557]: Failed password for mw from 192.168.5.205 port 38310 ssh2
09:01
That means that the user with the problem has given the wrong password
09:01
Maybe your keyboard layout is incorrect
09:01
Or maybe you have numlock on/off
09:01
Try to type the password where the username is
09:01
So that you see what you're typing
09:02
<vlt>
alkisg: No swapped keys, the passwd contains no special chars.
09:02
<alkisg>
The message is clear; the password is wrong
09:02
Failed password, it says
09:03
<vlt>
alkisg: Wrong passwords for at least three users? Using the same non-special-char passwds via ssh works fine.
09:05
<alkisg>
That message comes from sshd, not from LTSP
09:05
So, sshd tells you the password has failed
09:06
I'd try typing the password in the username box if I were you. Or, temporarily setting the password to 12345678.
09:07
<vlt>
alkisg: I did.
09:08
<alkisg>
And? Still no clue as to why this is happenning?
09:09
Let's make it simpler:
09:09
!SCREEN_02
09:09
<ltsp>
alkisg: SCREEN_02: to get a root shell on an Ubuntu thin client: https://help.ubuntu.com/community/UbuntuLTSP/ClientTroubleshooting#Using%20a%20shell%20SCREEN
09:09
<alkisg>
Get a local shell on the client as it's described above
09:09
From there, give this command: ssh <user>@server
09:09
Change <user> to an existing username
09:10
Leave server exactly as it is, the word "server", don't replace it
09:10
See if you can login from there.
09:10
That's what ldm does, it just calls ssh
09:11
So if you can login from the local client shell, then you should be able to login with ldm too.
09:11
<vlt>
alkisg: I already tried this.
09:11leio has left IRC (leio!~leio@gentoo/developer/leio, Read error: Operation timed out)
09:11
<alkisg>
And?
09:12
<vlt>
Works.
09:12
But still not the ldm login.
09:12
<alkisg>
Then the only thing I can think of, is that you gave me the wrong log
09:12
<vlt>
alkisg: It's the correct log.
09:12
<alkisg>
I.e. that the users successfully login, and X crashes, and you just gave me a failed login attempt that only happened once
09:13
<vlt>
SURE
09:13
<alkisg>
So. tail /var/log/auth.log now,
09:13
then try to login
09:13
then again: tail /var/log/auth.log,
09:13
and see if you got a failed password again
09:13* vlt runs "tail -f"
09:14
<alkisg>
OK, go ahead and try to login from ldm
09:14leio has joined IRC (leio!~leio@gentoo/developer/leio)
09:14
<alkisg>
If you're sure that you get a failed password from ldm, but not from ssh on the local terminal, and yet your keyboard settings is not the problem, then I don't know what is.
09:14
That would mean that LDM changes the password before sending it to ssh
09:15
Which I don't believe is the case.
09:16
<vlt>
alkisg: auth.log from "tail -f": http://pastebin.com/XrZL5LRa -- You can see me logging out from the client successfully before trying ldm login.
09:17
<alkisg>
Sep  5 11:14:34 glitter sshd[11788]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.5.205  user=af
09:17
Why is there an authentication failure there?
09:17
(before the password failure from ldm below)
09:17bobby_C has left IRC (bobby_C!~bobby@85-124-22-227.teleworker.xdsl-line.inode.at, Ping timeout: 260 seconds)
09:18
<vlt>
nfc
09:18
<alkisg>
Also. When you tried ssh <user>@server from the local terminal on the ltsp client (it's very important that you try that from the ltsp client and not from another machine), did you get any warnings or error messages?
09:18
Or info messages? I see you have "verbose=on", maybe you got some output while logging in?
09:20
<vlt>
alkisg: This is logging in from the client via ssh as the very same user: http://pastebin.com/hkBYrYRt
09:23
<alkisg>
And your output was like this, i.e. exactly 2 lines without anything between them?
09:23
$ ssh af@server
09:23
af@server's password:
09:23
prompt >
09:23
Because LDM parses ssh output
09:24
So if anything is different there, it would confuse LDM
09:24
Also, check /var/log/ldm.log on the client
09:27
Sep  5 11:19:39 glitter sshd[12146]: pam_unix(sshd:account): account af has password changed in future
09:27
^^^ This is also an indication of some problem
09:28
<vlt>
alkisg: I get the passwd in future msg for more than 60 users on 8 different LTSP servers. Usually no problem at all.
09:29
<alkisg>
Well, if all that you're saying is correct, and we don't have communication problems (english isn't my native language), then it means that LDM has a bug and changes the password before sending it to ssh, which is something I haven't heard of again.
09:30
So I don't know how to help - but I'm still believing that we lost something on our troubleshooting process.
09:30
<vlt>
alkisg: I'm sure about that. That's why my initial question was about debugging options.
09:31
<alkisg>
Change the ldm code and have it write the password to the log file
09:31
I don't think we have debugging info for that
09:34ddave71861 has joined IRC (ddave71861!~Miranda@171-49-13-46.tmcz.cz)
09:38
<alkisg>
apt-get source ldm, then change file sshutils.c
09:38
write(fd, ldm.password, strlen(ldm.password));
09:38ddave7 has left IRC (ddave7!~Miranda@109-183-25-67.tmcz.cz, Ping timeout: 258 seconds)
09:38
<alkisg>
After that put a loginfo call, to write the password to the log
09:38
Compile, put it in the chroot + update image
09:39
I still don't think the problem is in LDM, though.
09:56
<vlt>
alkisg: I rebooted one client (for the sixth time) and now logging was possible. I have absolutely no idea what could have changed now. :/
09:56
*logging _in_
09:56
<zamba>
in soviet russia /unq
09:56
hhehe
09:57
sorry about that :)
09:58
<vlt>
zamba: "/unq"?
10:06map7_ has joined IRC (map7_!~map7@ppp118-209-19-140.lns20.mel4.internode.on.net)
10:11
<zamba>
short for /unquery
10:11
in irssi
10:18bobby_C has joined IRC (bobby_C!~bobby@85-124-22-227.teleworker.xdsl-line.inode.at)
10:44klausade has joined IRC (klausade!~klaus@cm-84.215.171.127.getinternet.no)
10:50toscalix has left IRC (toscalix!~toscalix@76.Red-88-12-65.dynamicIP.rima-tde.net, Remote host closed the connection)
10:54
<Hyperbyte>
vlt: http://forum.soft32.com/linux/unix_chkpwd-4275-account-root-password-changed-future-ftopict506099.html
10:56
<alkisg>
I think vlt is using some mysql backend for passwords, maybe samba?
10:56
But in any case, ssh from SCREEN_02 shouldn't ever behave differently than LDM, as LDM uses ssh
10:57alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Quit: Leaving.)
11:03staffencasa has left IRC (staffencasa!~staffenca@128-193-144-211.oregonstate.edu, Ping timeout: 258 seconds)
11:06pedronveloso has joined IRC (pedronveloso!~pedro@static-b4-252-232.telepac.pt)
11:24pedronveloso has left IRC (pedronveloso!~pedro@static-b4-252-232.telepac.pt, Quit: Leaving)
11:42Trixboxer has joined IRC (Trixboxer!~Trixboxer@office.supportdepartment.net)
12:17
<Hyperbyte>
Google has really awesome homepage today
12:35alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg)
12:43xavierb has joined IRC (xavierb!~xavier@APoitiers-552-1-80-100.w92-136.abo.wanadoo.fr)
13:03
<xavierb>
Hello, to reduce my network traffic, I would like to disable remote syslog. I don't see any option for that in lts.conf.
13:11
<alkisg>
xavierb: https://bugs.launchpad.net/ltsp/+bug/697387
13:12
I.e. set SYSLOG=False in lts.conf
13:18
<xavierb>
alkis: thanks!
13:20
<muppis>
Foe curiosity, how much that reduces?
13:20
<xavierb>
why SYSLOG is true by default?
13:20
<muppis>
For..
13:21
<alkisg>
xavierb: SYSLOG is undocumented, imho it should be eliminated from the code
13:21
<xavierb>
as one need to setup also the server rsyslog.conf, I don't see why default SYSLOG is true
13:21
<alkisg>
I just proposed a workaround in the bug report
13:22
Good point, do mention that in the bug report too
13:22
xavierb: did you check the network packets? Does the client try to send logs to the server, even if the server isn't listening?
13:23
Or the client stops trying in this case?
13:23
<xavierb>
alkisg: I agree with your workaround
13:24
alkisg: no, I didn't yet, but I need to enable ryslog reception for debugging one problematic thin-client
13:24
<alkisg>
Because if the client stops trying, and no network traffic is generated, then the current defaults are reasonable
13:25
(it also saves client RAM, as the local syslog would be stored in the tmpfs otherwise)
13:26
<xavierb>
you mean: if the client stops trying, it should dont even generate local syslog?
13:27
<alkisg>
Well, if the configuration file tells the client to log on the server, and the server isn't listening, I don't see why the client would log locally
13:27
Haven't tested though
13:30poff has joined IRC (poff!~poff@ARennes-258-1-260-17.w81-53.abo.wanadoo.fr)
13:30
<xavierb>
I've just ssh into one client: it does some local log.
13:30poff has left IRC (poff!~poff@ARennes-258-1-260-17.w81-53.abo.wanadoo.fr, Client Quit)
13:30
<xavierb>
Now we need an option to disable local log :)
13:30
(and save ram)
13:33m29poff has joined IRC (m29poff!~m29poff@ARennes-258-1-260-17.w81-53.abo.wanadoo.fr)
13:38TanzJack has joined IRC (TanzJack!~TanzJack@197.250.28.108)
13:42
<TanzJack>
hi
13:43
anybody there?
13:43
<xavierb>
hello
13:44
<TanzJack>
hi how is it?
13:45
<xavierb>
fine :)
13:46
<alkisg>
xavierb: btw, I'm not sure that /etc/rsyslog.d/ltsp.conf actually override the ubuntu defaults in /etc/rsyslog.d/50-defaults, so it's possible that whatever LTSP writes in that file, doesn't matter
13:47
I tried renaming it to 60-ltsp, and the local logging stopped :)
13:47
More testing is needed...
13:48
<xavierb>
alkisg: I'm using Debian, there is nothing in /etc/rsyslog.d except ltsp.conf
13:48
<alkisg>
Ah
13:48
So... why do you see local logging?!
13:48
Are the dates on those files recent?
13:49
<xavierb>
may be I've checked too fast. I think it's only first boot and X log, sorry
13:50
<alkisg>
No problem, you just helped me find out that I need to file a bug about it in Ubuntu :D
13:51
<xavierb>
Now, one just need to update the documentation: ir rsyslog doesn't accept remote logging, no logs are sent to the network nor local, am I right?
13:53
<TanzJack>
guess what? A problem with LTSP drove me here. A really simple one I guess but I really dont find the answer: I need my clients to run a script directly after login (want to synch the home folder with a fix template every time somebody logs in). WHERE do I put it that it will be executed? I tried "/etc/init.d/" and "/usr/share/ldm/rc.d/" (both in chroot) such as "/etc/X11/Xsession.d/" on the server; the latest got me the script executed when I log in ON th
14:00
<xavierb>
TanzJack: the home folder is on the server
14:01
<alkisg>
TanzJack: this might help you: http://www.mail-archive.com/ltsp-discuss@lists.sourceforge.net/msg39777.html
14:02
Copying the files needs to be done at the very start of the session, before other scripts have started running
14:04
<xavierb>
alkisg: can't this be done on the server? I mean the server knows when someone log in.
14:04
<alkisg>
xavierb: sure, I've also a pam-based implementation for this
14:04
But you can't do it from e.g. /etc/xdg/autostart, it runs too late
14:05
So if you erased/synced stuff at that point, you'd delete .xauthority, .gconfd and other needeed files
14:06
<xavierb>
and in /etc/profile.d ?
14:07
<alkisg>
No idea when distros source that
14:07
Isn't that only sourced from bash?
14:08map7_ has left IRC (map7_!~map7@ppp118-209-19-140.lns20.mel4.internode.on.net, Ping timeout: 276 seconds)
14:09
<xavierb>
yes. I forgot that the shell runned by the user at login is on the thin-client
14:10
yup, I'm wrong again: user launch a shell on the server at login (at least with kde4)
14:10
<alkisg>
I tried exporting a variable in /etc/profile.d, and then "ssh user@localhost", and the variable wasn't exported
14:10
So it doesn't look like a robust method anyway
14:12
Ah it needs a .sh extension
14:12
Anyway, I'm not sure if that's early enough e.g. for .xauthority
14:14
<xavierb>
don't know
14:15m29poff has left IRC (m29poff!~m29poff@ARennes-258-1-260-17.w81-53.abo.wanadoo.fr, Quit: Quitte)
14:15
<xavierb>
alkisg: I need to quit, thanks for your help
14:15
bye
14:15
<alkisg>
bb
14:15xavierb has left IRC (xavierb!~xavier@APoitiers-552-1-80-100.w92-136.abo.wanadoo.fr, Quit: Konversation terminated!)
14:16m29poff has joined IRC (m29poff!~m29poff@ARennes-258-1-260-17.w81-53.abo.wanadoo.fr)
14:17xavierb has joined IRC (xavierb!~xavier@APoitiers-552-1-80-100.w92-136.abo.wanadoo.fr)
14:19
<xavierb>
alkisg: I forgot something. While you are changing SYSLOG script, woudn't it be good to change default port? because rsyslog documentation says that TCP and UDP ports should be different and that TCP port 514 is often used by RPC.
14:21
see http://www.rsyslog.com/using-the-syslog-receiver-module/ and http://www.rsyslog.com/sending-messages-to-a-remote-syslog-server/
14:25xavierb has left IRC (xavierb!~xavier@APoitiers-552-1-80-100.w92-136.abo.wanadoo.fr, Quit: Konversation terminated!)
14:29alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Quit: Leaving.)
15:04irule has joined IRC (irule!~irule@187.175.154.140)
15:05Damianos has joined IRC (Damianos!~Damianos@adsl-070-145-074-043.sip.cha.bellsouth.net)
15:41m29poff has joined IRC (m29poff!~m29poff@125.213.206.77.rev.sfr.net)
15:48TanzJack has left IRC (TanzJack!~TanzJack@197.250.28.108, Ping timeout: 260 seconds)
15:59Parker955_Away is now known as Parker955
16:11dptech has joined IRC (dptech!~dptech@can06-1-82-242-223-39.fbx.proxad.net)
16:17Parker955 is now known as Parker955_Away
16:33drdata has joined IRC (drdata!~drdata@tw2.udallas.edu)
16:43toscalix has joined IRC (toscalix!~toscalix@76.Red-88-12-65.dynamicIP.rima-tde.net)
16:45Parker955_Away is now known as Parker955
16:48[GuS] has joined IRC ([GuS]!~MysT@213-117-16-190.fibertel.com.ar)
16:48[GuS] has joined IRC ([GuS]!~MysT@unaffiliated/gus/x-663402)
16:50
<dptech>
Hello Where can i found ltsp cluster tuto ? thanks
16:54ddave71861 has left IRC (ddave71861!~Miranda@171-49-13-46.tmcz.cz, Ping timeout: 258 seconds)
17:00garymc has joined IRC (garymc!~chatzilla@host81-148-107-162.in-addr.btopenworld.com)
17:01
<garymc>
hi my ltsp server has lost internet connection and I cant work out whats wrong
17:04alkisg has joined IRC (alkisg!~alkisg@ppp046176136116.dsl.hol.gr)
17:04alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg)
17:04alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Client Quit)
17:07Parker955 is now known as Parker955_Away
17:14garymc has left IRC (garymc!~chatzilla@host81-148-107-162.in-addr.btopenworld.com, Quit: ChatZilla 0.9.87 [Firefox 6.0.1/20110830092941])
17:22vagrantc has joined IRC (vagrantc!~vagrant@c-24-21-191-93.hsd1.or.comcast.net)
17:24
<TheMatrix3000>
hey all
17:24
anyone here doing a memtest in the pxeboot with ltsp? that can lend me advice on how to do it
17:26
<vagrantc>
there are some tricks
17:27
i seem to recall adding some support for memtest to the code a while ago...
17:29
TheMatrix3000: there's code in ltsp to add memtest entries to the pxe boot menu
17:31
<TheMatrix3000>
where is it?
17:31
lol
17:31
I need it to test thin clients
17:32
<vagrantc>
it's well hidden
17:32
<TheMatrix3000>
i know
17:32
otherwise I would find it
17:32
<vagrantc>
what distro & version you running? what version of ltsp?
17:33
<TheMatrix3000>
It's kinda like FAT_RAM_THRESHOLD
17:33
11.04
17:33
<vagrantc>
no, this is much more difficult to find than FAT_RAM_THRESHOLD
17:34
ok, the code's been in there since mid-2009, so you should be good...
17:34
<TheMatrix3000>
Are you trying to say you have no idea where it is?
17:35
<vagrantc>
it's complicated enough that it's not just simply enabling a feature in lts.conf, so i'm reading the code to try to *help* you :P
17:35
if you'd rather read it yourself, look in update-kernels
17:35
<TheMatrix3000>
ah, haha, nice
17:35
I don't even know where to see that lol
17:36
<vagrantc>
in the source, it's in ltsp-trunk/client/update-kernels
17:36
and in the chroot, maybe /opt/ltsp/i386/usr/share/ltsp/update-kernels
17:37
<TheMatrix3000>
ill try looking too
17:37
two heads are better than oen
17:37
<vagrantc>
ok, i think in order to usefully get memtest working, you'd need a boot menu... in /opt/ltsp/i386/etc/ltsp/update-kernels.conf ... set PXELINUX_DEFAULT=menu (or vesamenu)
17:37
<TheMatrix3000>
found it
17:37
lol
17:38
whats menu vs vesamenu
17:39
<vagrantc>
one uses VESA graphics, the other just plain console features
17:39
in my experience, the occasional machine doesn't work with vesamenu, but i'm guessing neewer ones support it well enough (i deal with a lot of old hardware)
17:40
it looks purtier
17:40
allegedly
17:40
<TheMatrix3000>
then run an ltsp-update-kernels
17:40
<vagrantc>
not done yet
17:40
<TheMatrix3000>
ah lol
17:40
<vagrantc>
then, i guess, for some bizarre reason, you need to manually copy memtest86+.bin into place
17:40
but it's not that simple!
17:41
you need to copy it without the .bin extension, or you may run into bugs with pxelinux
17:41
and by into place, i mean: /opt/ltsp/i386/boot
17:41
<TheMatrix3000>
where is memtest86+.bin
17:42
<vagrantc>
i think it was because of http://bugs.debian.org/546219 that i got stymied on how to implement it properly
17:42
<TheMatrix3000>
ha nbm
17:42
nvm
17:42
im dumb
17:42
i can find it in /boot/
17:42
lol
17:42Parker955_Away is now known as Parker955
17:42
<vagrantc>
you can install it on your server or in the chroot
17:42
but wait, there's more ...
17:43
sudo ltsp-chroot /usr/share/ltsp/update-kernels ; sudo ltsp-update-kernels
17:43
then, if you're lucky, this will work.
17:43* vagrantc remembers when ltsp-update-kernels ran /usr/share/ltsp/update-kernels automatically
17:44
<vagrantc>
but we disabled that for some reason i don't quite remember ... maybe it was even me
17:44Damianos has left IRC (Damianos!~Damianos@adsl-070-145-074-043.sip.cha.bellsouth.net, Quit: Damianos)
17:44
<TheMatrix3000>
i need to remove the .bin from memtest86+ right?
17:45
<vagrantc>
cp /boot/memtest86+.bin /opt/ltsp/i386/boot/memtest86+
17:45
for example
17:45
<TheMatrix3000>
memtest is already in my boot part of the chroot
17:45
so let me cp it as without .bin
17:45
<vagrantc>
you could also just install memtest86+ into the chroot, and symlink it
17:46
symlink would be better, just in case you ever upgraded the version in the chroot, you wouldn't have to remember to copy it again
17:47
<TheMatrix3000>
ha it worked
17:47
<vagrantc>
ah, good
17:47
<TheMatrix3000>
ah menu looks gay
17:47
using visamenu
17:48TheMatrix3000 has left IRC (TheMatrix3000!~TheMatrix@rrcs-70-61-255-226.central.biz.rr.com)
17:48TheMatrix3000 has joined IRC (TheMatrix3000!~TheMatrix@rrcs-70-61-255-226.central.biz.rr.com)
17:48
<TheMatrix3000>
ah, oops
17:48
didn't click out of my window and closed it
17:48
<vagrantc>
a happy menu, how chipper
17:49
<TheMatrix3000>
lets see what visa looks like
17:49
ooo
17:49
could not find kernel image
17:49
visamenu
17:50markit has joined IRC (markit!~marco@88-149-177-66.staticnet.ngi.it)
17:50
<vagrantc>
vesamenu
17:51
<TheMatrix3000>
ha that's better
17:51
i wonder how to customize it
17:52
<vagrantc>
others know better than i... i mostly go with functional, and leavy pretty to others
17:52
<TheMatrix3000>
lol
17:53
thank you for the help
18:25petre has joined IRC (petre!~petre@scheie.homedns.org)
18:26
<dptech>
Hello Where can i found ltsp cluster tuto ? thanks
18:40
<petre>
dptech, have you looked at https://www.ltsp-cluster.org/?
18:43
<dptech>
Yes, i'd like found other informations...
18:53Damianos has joined IRC (Damianos!~Damianos@adsl-070-145-074-043.sip.cha.bellsouth.net)
19:06TheMatrix3000_ has joined IRC (TheMatrix3000_!~TheMatrix@rrcs-70-61-255-226.central.biz.rr.com)
19:08TheMatrix3000 has left IRC (TheMatrix3000!~TheMatrix@rrcs-70-61-255-226.central.biz.rr.com, Ping timeout: 240 seconds)
19:12Lumiere has left IRC (Lumiere!~jstraw@cpe-70-117-27-227.satx.res.rr.com, Ping timeout: 252 seconds)
19:13TheMatrix3000__ has joined IRC (TheMatrix3000__!~TheMatrix@rrcs-70-61-255-226.central.biz.rr.com)
19:14dptech has left IRC (dptech!~dptech@can06-1-82-242-223-39.fbx.proxad.net, Quit: When two people dream the same dream, it ceases to be an illusion. KVIrc 3.4.2 Shiny http://www.kvirc.net)
19:14irule has left IRC (irule!~irule@187.175.154.140, Ping timeout: 260 seconds)
19:17TheMatrix3000_ has left IRC (TheMatrix3000_!~TheMatrix@rrcs-70-61-255-226.central.biz.rr.com, Ping timeout: 240 seconds)
19:20TheMatrix3000___ has joined IRC (TheMatrix3000___!~TheMatrix@rrcs-70-61-255-226.central.biz.rr.com)
19:23TheMatrix3000__ has left IRC (TheMatrix3000__!~TheMatrix@rrcs-70-61-255-226.central.biz.rr.com, Ping timeout: 240 seconds)
19:28Damianos has left IRC (Damianos!~Damianos@adsl-070-145-074-043.sip.cha.bellsouth.net, Quit: Damianos)
19:48Parker955 is now known as Parker955_Away
20:01[GuS] has left IRC ([GuS]!~MysT@unaffiliated/gus/x-663402, Remote host closed the connection)
20:04TheMatrix3000___ has left IRC (TheMatrix3000___!~TheMatrix@rrcs-70-61-255-226.central.biz.rr.com, Ping timeout: 240 seconds)
20:04Damianos has joined IRC (Damianos!~Damianos@adsl-070-145-074-043.sip.cha.bellsouth.net)
20:09TheMatrix3000 has joined IRC (TheMatrix3000!~TheMatrix@rrcs-70-61-255-226.central.biz.rr.com)
20:10KBme has left IRC (KBme!~KBme@2001:470:cabe:666:666:666:666:666, Ping timeout: 260 seconds)
20:11KBme has joined IRC (KBme!~KBme@2001:470:cabe:666:666:666:666:666)
20:15Damianos_ has joined IRC (Damianos_!~Damianos@adsl-070-145-074-043.sip.cha.bellsouth.net)
20:18Parker955_Away is now known as Parker955
20:18xavierb has joined IRC (xavierb!~xavier@APoitiers-552-1-80-100.w92-136.abo.wanadoo.fr)
20:19Damianos has left IRC (Damianos!~Damianos@adsl-070-145-074-043.sip.cha.bellsouth.net, Ping timeout: 264 seconds)
20:19Damianos_ is now known as Damianos
20:23Parker955 is now known as Parker955_Away
20:40ddave7 has joined IRC (ddave7!~Miranda@93-153-83-164.tmcz.cz)
20:44ddave71861 has joined IRC (ddave71861!~Miranda@93-153-43-203.tmcz.cz)
20:47ddave7 has left IRC (ddave7!~Miranda@93-153-83-164.tmcz.cz, Ping timeout: 258 seconds)
20:51ddave71861 has left IRC (ddave71861!~Miranda@93-153-43-203.tmcz.cz, Ping timeout: 258 seconds)
20:52ddave7 has joined IRC (ddave7!~Miranda@109-183-147-127.tmcz.cz)
20:59
<TheMatrix3000>
running fat-client having issues with gnome panel displaying
20:59
how do i fix it?
21:02
<vagrantc>
this is not my forte, but you'll probably need to give more detailed information before someoen could help
21:04xavierb has left IRC (xavierb!~xavier@APoitiers-552-1-80-100.w92-136.abo.wanadoo.fr, Quit: Konversation terminated!)
21:04xavierb has joined IRC (xavierb!~xavier@APoitiers-552-1-80-100.w92-136.abo.wanadoo.fr)
21:04
<TheMatrix3000>
gnome-panel simply isn't running
21:04
when a user logs in on a fat client
21:06Trixboxer has left IRC (Trixboxer!~Trixboxer@office.supportdepartment.net, Quit: "Achievement is not the end, its the beginning of new journey !!!")
21:07toscalix has left IRC (toscalix!~toscalix@76.Red-88-12-65.dynamicIP.rima-tde.net, Remote host closed the connection)
21:09Parker955_Away is now known as Parker955
21:14drdata has left IRC (drdata!~drdata@tw2.udallas.edu, Ping timeout: 276 seconds)
21:20
<Hyperbyte>
TheMatrix3000, we've done this before.
21:21
<TheMatrix3000>
ok ill try searching logs
21:21
<Hyperbyte>
You told me about gnome-panel, I asked you what you see when you type 'gnome-panel' in a terminal
21:21
And then you never got back to me.
21:21
<TheMatrix3000>
oh i never saw that
21:21
i must of left the office or something
21:21
one second
21:30Parker955 is now known as Parker955_Away
21:33drdata has joined IRC (drdata!~drdata@tw2.udallas.edu)
21:35Parker955_Away is now known as Parker955
21:40drdata has left IRC (drdata!~drdata@tw2.udallas.edu, Quit: drdata)
21:54ddave7 has left IRC (ddave7!~Miranda@109-183-147-127.tmcz.cz, Quit: Miranda IM! Smaller, Faster, Easier. http://miranda-im.org)
21:56m29poff has left IRC (m29poff!~m29poff@125.213.206.77.rev.sfr.net, Quit: Ex-Chat)
22:03drdata has joined IRC (drdata!~drdata@tw2.udallas.edu)
22:04
<markit>
hi, I'm try to decode the english of this page in some points: https://help.ubuntu.com/community/UbuntuLTSP/FatClients
22:04
what is the meaning of "Home directories mounted on login with sshfs unless the solution. "
22:05
i can't get the "unless the solution." part
22:05
(I'm not native english speaker)
22:05
maybe some expert of FAT installation can help
22:06
also "The NBD root on the thin client version simply has to get the client to and SSH/LDM logon screen"
22:06drdata has left IRC (drdata!~drdata@tw2.udallas.edu, Remote host closed the connection)
22:06
<markit>
what does it mean "get the client to"?
22:11
<vagrantc>
markit: it isn't the best written english, if that makes you feel any better
22:11
<markit>
vagrantc: lol, thanks, I would love to understand and improve (editing the wiki), but I'm not sure about the real intention of the writer
22:12
is funny having an howto in "crypting english" :)
22:12
<vagrantc>
the "unless the solution." part seems like they were going to say more
22:12bobby_C has left IRC (bobby_C!~bobby@85-124-22-227.teleworker.xdsl-line.inode.at, Ping timeout: 252 seconds)
22:12
<markit>
really
22:12
<vagrantc>
and just didn't finish
22:13
i think "get the client to an SSH/LDM logon screen" is what the other meant to say
22:13
<markit>
maybe instead of "unless" was "while the thin solution uses..." I don't know, what does it use?
22:13
(I'm trying my first fat installation on a test VM
22:13
)
22:14
<vagrantc>
markit: there is an option to use NFS_HOMEDIRS or some such
22:14
so maybe it was talking about using sshfs (the default) vs. NFS home dirs.
22:14
<markit>
ok, I'm to ignorant to edit that
22:14
<vagrantc>
some applications have issues with sshfs homedirs
22:14
<markit>
so "unless NFS_HOMEDIRS is specified"
22:15
but should be about the differences among thin and fat
22:15
<vagrantc>
i'm not sure on the exact name for the option, but yes, i think that's what they were getting at
22:15
<markit>
let's wait alksig :)
22:16
<vagrantc>
well, with a true thin client, there's no homedir mounted locally ... but most thin clients have support for localapps available by default, so then the difference between thin and fat is ... blurry
22:16
<markit>
vagrantc: do you use fat config?
22:16Appiah has left IRC (Appiah!~appiah@ip69.hethane.riksnet.nu, Ping timeout: 252 seconds)
22:16
<vagrantc>
i've been meaning to explore it more for years, but haven't put it into production yet
22:17
the biggest annoyance is with screensavers/screenlockers and other apps that need to authenticate to the server.
22:17
because by default, there's no valid authentication with a localapp or fatclient
22:17
<markit>
urgh, I thought was effortless, explain to me
22:18
I know nothing about the inner working of all this stuff :(
22:18
so if screen locks and you are asked for the password, you are lost?
22:18
<vagrantc>
well, there's no authentication necessary for most setups, but if your screensaver locks the screen and is runnin g locally, there's no local password for it to authenticate against.
22:18Parker955 has left IRC (Parker955!~parker@d72-39-190-3.home1.cgocable.net, Ping timeout: 258 seconds)
22:19
<vagrantc>
all the authentication is done on the server.
22:19
<markit>
isn't possible to modify pam or some other (I really don't know) config to autenticate to the server?
22:19
ok, so the whole system should "redirect" authentication to the server
22:19
included screensaver
22:19
no?
22:19
<vagrantc>
the simplest workaround is to figure out a way to run ... hah! ... remoteapps for things like screensavers on the server.
22:20* markit scaried like hell
22:20
<vagrantc>
markit: there is work to get the local pam stuff to authenticate properly, but it's not quite ready
22:20
<markit>
wondering how is that GNU is so weak on this stuff... should be available since long long time
22:21
<vagrantc>
scotty has been working on libpam-ssh, which would be able to use the existing setup to authenticate
22:21
<markit>
M$ has AD, GNU has... a mess
22:21
<vagrantc>
markit: free software can implement it in a million ways... and so it gets implemented in a million mostly incompatible ways.
22:21
<markit>
never used myself, but the magic word for this stuff usually is "LDAP"
22:21Parker955 has joined IRC (Parker955!~parker@d221-68-136.commercial.cgocable.net)
22:21
<markit>
lol, sad but true
22:22
is scotty still working on it? expected time for "it's ready"?
22:22
<vagrantc>
yeah, some people have configured ldap and such to ahdnle authentication, but we've been holding out for this libpam-ssh thing, since it would require considerably less configuration for the administrator
22:23
<markit>
I love this part :)
22:23
<vagrantc>
but the timeframe has proven ... slow
22:23
hopefully they'll get it thoroughly tested at the hackfest i think near the end of october
22:24
<markit>
we should have schools give money or, if high school, programmers to ltsp project
22:24
they have all the savings, we have all the burden, is not fair
22:25
<vagrantc>
probably should get some google summer of code projects next year for ltsp
22:25
as much as i'm no fan of google, that is a really cool program
22:25
<markit>
really, better than nothing
22:25
if you consider the HUGE amount of money google gets
22:26
in any case, I consider that without google we will be lost much faster
22:26
i.e. webm standard or phone market will be killed asap without them
22:27
but the best would be that the users will give back to FOSS
22:27
instead of hoping that "someone else" will
22:27
wondering with FAT how much the lan is stressed
22:27
<vagrantc>
we've got to provide (easy) avenues for them to contribute.
22:28
markit: i just talked with someone who implemented fat clients at a local school, and he said a faiirly modest server with gigabit, 100-megabit network could handle well over 100 clients without any noticeable load
22:28
<markit>
I've the feeling tha people a) don't value freedom as an added value b) don't realize that is not "free as in beer" but they should contribute
22:29
IMPOSSIBLE
22:29
<vagrantc>
yes, people really don't get the importance of freedom
22:29
<markit>
or my users are all "power hungry", or there is something strange
22:29
<vagrantc>
markit: this was fat clients, with some very impressive fat clients ...
22:30
i don't know the exact details, but it sounds good to me
22:30
<markit>
100 are really many.. I've a 18pc lab "thin" that put my 8GB quad core on it's knee with libreoffice impress and some graphics pasted in
22:30
<Hyperbyte>
Yes, but thin clients generally use a lot more bandwith than fat clients...
22:31
<markit>
while people here talsk about "12MB ram for atom clients" and "4GB server" for 100.000 pc ;P
22:31
<vagrantc>
when you're only serving up the filesystem, and if they have enough ram, the fat client will only hit the filesystem once per file loaded (due to "disk" caching)
22:31
<markit>
mmm I see, thought was the contrary
22:31
"only screen" vs "all data and programs and swap"
22:31
<vagrantc>
yes, but with fatclients, all the CPU happens on the client
22:32
transmitting video over the wire is expensive, and fat clients don't do that part :)
22:32
<Hyperbyte>
markit, try and imagine for a second... one screen, refresh rate 60hz (so 60 images per second), resolution of 1280x1024, 24-bit color depth
22:32
<markit>
yes, but instead of a local 50MB/s hd you have a 50MB/s lan to share with 100 other clients...
22:32
<Hyperbyte>
markit, that, vs, transferring files for say OpenOffice across network.
22:33
<markit>
Hyperbyte: well, screen is not refreshed at 60hz, X-Window sends you only the part has changed, when changed
22:33
and IF changed
22:33
<vagrantc>
it's transferring the interactive video of using the application vs. just downloading the applicationc and running it locally
22:34
<markit>
ok, I'll do some test soon, happy if you are right (I think you are, just not 100% convinced, lol)
22:34
<vagrantc>
the interactivity is another point ... if the download happens in 1 second, or 3 seconds, it's not a huge deal, but if your mouse click takes 1-3 seconds, you'll notice the difference
22:34
<Hyperbyte>
markit, still, even with only changed areas, it adds up...
22:35
<markit>
vagrantc: good point
22:36
also we had old recycled pc vs brand new, 3Ghz, icore 3, 4GB ram clients :)
22:36
<vagrantc>
you'd think that should make a difference :)
22:36
<markit>
also like simply thin clients you notice the difference (1gb nic, well supported intel 4500video)
22:37
I could build a cluster instead, lol
22:39
<vagrantc>
just make a cluster out of screensaver time
22:39
screensavers are such a waste of energy ... they usually use more CPU than fullscreen video
22:40
and with a network of thin clients ... ugh.
22:44
<markit>
well, I've seen some windows program that grab screensaver images from internet as well, changing it each minute or so
22:45
just to eath your bandwidth too
22:45
but users are so happy :)
22:46
<vagrantc>
well, good chattinng ... but i've got to enjoy thiss sun while it lasts
22:47* vagrantc waves
22:50Parker955 has left IRC (Parker955!~parker@d221-68-136.commercial.cgocable.net, Ping timeout: 258 seconds)
22:50Parker955 has joined IRC (Parker955!~parker@d221-68-136.commercial.cgocable.net)
22:52xavierb has left IRC (xavierb!~xavier@APoitiers-552-1-80-100.w92-136.abo.wanadoo.fr, Quit: Konversation terminated!)
22:56
<markit>
bye vagrantc, see you
22:56Appiah has joined IRC (Appiah!~appiah@ip69.hethane.riksnet.nu)
22:58vagrantc has left IRC (vagrantc!~vagrant@c-24-21-191-93.hsd1.or.comcast.net, Ping timeout: 245 seconds)
23:00Parker955 is now known as Parker955_Away
23:02Parker955_Away is now known as Parker955
23:24TheMatrix3000_ has joined IRC (TheMatrix3000_!~TheMatrix@rrcs-70-61-255-226.central.biz.rr.com)
23:26TheMatrix3000 has left IRC (TheMatrix3000!~TheMatrix@rrcs-70-61-255-226.central.biz.rr.com, Ping timeout: 246 seconds)
23:39Parker955 is now known as Parker955_Away
23:44Parker955_Away has left IRC (Parker955_Away!~parker@d221-68-136.commercial.cgocable.net, Ping timeout: 258 seconds)