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


Channel log from 17 November 2010   (all times are UTC)

00:09sweetpi has quit IRC
00:10_UsUrPeR_ has quit IRC
00:10gorkhaan has quit IRC
00:11gorkhaan has joined #ltsp
00:14_UsUrPeR_ has joined #ltsp
00:27evil_root is now known as zz_evil_root
00:59RiXtEr has quit IRC
01:00alexqwesa has quit IRC
01:04alexqwesa has joined #ltsp
01:04jhutchins has quit IRC
01:06jhutchins has joined #ltsp
01:20komunista has joined #ltsp
01:39zz_evil_root has quit IRC
01:39zz_evil_root has joined #ltsp
01:40zz_evil_root is now known as evil_root
02:00alexqwesa has quit IRC
02:02Trixboxer has joined #ltsp
02:02alexqwesa has joined #ltsp
02:04gnunux has joined #ltsp
02:05
<Trixboxer>
Hi, Is it possible to run a script once a user logs in the fat-client ? Where should I write the script, In server or fat-client ?
02:07
<gnunux>
hi
02:13alexqwesa has quit IRC
02:13alexqwesa has joined #ltsp
02:16
<alkisg>
Trixboxer: inside the user session? A good place is in /opt/ltsp/i386/etc/xdg/autostart
02:21dobber has joined #ltsp
02:38Da-Geek has joined #ltsp
02:46leio_ has joined #ltsp
02:47leio has quit IRC
02:55
<Trixboxer>
alkisg: Sorry for late reply.. I was away
02:56
alkisg: Actually the problem is.. when users starts application like firefox it creates a lock file and upon the fat-client hang he has to restart it
02:57
so, the lock files remains there even after restart and from then he cant start firefox
02:57
so I just want to run a script which will clear all log files of the user who is just logging in
02:57
log = lock
03:00
<alkisg>
Trixboxer: if you're just looking for a workaround for firefox, just edit the /usr/bin/firefox script to delete that lock when it starts
03:01
<Trixboxer>
no no its for most of apps like firefox, chrome, opera, thunderbird, skype and ...
03:02wwx has quit IRC
03:03
<alkisg>
Check if you're having the statd problem with nfs on ubuntu
03:03* alkisg had to use NFS_HOME_OPTIONS=nolock to work around it
03:03
<Trixboxer>
whats that 0_o
03:03
ok under [Default] ?
03:04
and my NFS is in sync.. should I make it async ?
03:05
<muppis>
I think Trixboxer means lockfiles set by application itself, like FF's .parentlock
03:05
?
03:05
<Trixboxer>
yes
03:06
under their own app folder
03:06
<alkisg>
Yes, but those should work without having to resort to all these workarounds
03:08
<Trixboxer>
alkisg: shall I put NFS_HOME_OPTIONS=nolock under [Default] ?
03:09
<alkisg>
Trixboxer: I mean that you'd better troubleshoot and find out what's causing that problem
03:09
When do those apps hang? Why don't they start again after hanging? Etc etc
03:09
<Trixboxer>
this is how it looks "./.mozilla/firefox/9jtaholt.default/lock -> 127.0.0.2:+2126"
03:10
"./.thunderbird/0tx7x1s2.default/lock -> 127.0.0.2:+1850"
03:10
and both locks are dead symlinks
03:11
<alkisg>
OK, I have one for mozilla too on my standalone PC. So?
03:14
If I backup that lock, then close firefox, then put back the lock (so as to simulate a crashed firefox), then firefox still starts without complaining
03:14leio_ has quit IRC
03:15
<Trixboxer>
hmm
03:15
The error showed is "Firefox is already running"
03:15
or "Opera is already running"
03:15
and once I remove the lock files .. all goes smooth
03:16
<alkisg>
Is it already running? Why wasn't the lock file removed if it was correctly closed? Etc.
03:24sweetpi has joined #ltsp
03:26
<Trixboxer>
It was not closed correctly
03:27Lifeboy has joined #ltsp
03:27
<Trixboxer>
Due to some bad habits firefox usually hangs the system and then they just press the reboot button
03:27
they open a new firefox instance for every website which they want to visit
03:27
:(
03:28leio has joined #ltsp
03:29
<alkisg>
OK, but even so, after rebooting the fat client, firefox should be able to delete the lock and start without complaining.
03:29wwx has joined #ltsp
03:29
<Lifeboy>
Regarding my jetpipe issue yesterday, which turned out to be due to loading the wrong image from /srv rather than /opt, I now have port 9100 listening on the chroot on the client device. It seems however that I don't have access to the printer from cups since I "find" the printer on 192.168.8.102:9100, but there is no response from the printer at all. Any thoughts?
03:29
<muppis>
How they do that? FF detects if it is already running and responses so it just opens new windows to same process.
03:30
<Trixboxer>
alkisg: when I fired "w" it shows same user twice I think that's the reason..
03:30
after reboot
03:35
<Lifeboy>
Or let me ask this: Are there any special steps that need to be taken to allow printing to a local device (like adding a user to lpadmin or the like?
03:36
<alkisg>
Trixboxer: then maybe you should enable LDM_LIMIT_ONE_SESSION, so that the old session gets deleted before the user logs in again
03:36
<Trixboxer>
wow
03:36
bingo
03:36
but where do I specify this option then ?
03:36
<alkisg>
In lts.conf
03:36
<Trixboxer>
under [Default] correct ?
03:37
<muppis>
yes
03:37
<Trixboxer>
so its only LDM_LIMIT_ONE_SESSION or LDM_LIMIT_ONE_SESSION=true ?
03:38
<alkisg>
LDM_LIMIT_ONE_SESSION=True
03:38
<Trixboxer>
http://pastebin.com/uuJiqPwm
03:38
<alkisg>
There's also LDM_LIMIT_ONE_SESSION_PROMPT if you want
03:38
<Trixboxer>
:) that was the result of google
03:38
<alkisg>
(that'll show them a dialog telling them that they're already logged in, and if they want to kill the old processes etc)
03:38
<Trixboxer>
whenever you give me any option.. I start googling on it
03:39
<alkisg>
(it might be a good idea to remind them that alt+ctrl+del is a bad habit :D)
03:39
<Trixboxer>
and what results is the "#ltsp channel logs" :P
03:39
<alkisg>
Heh
03:39
<Trixboxer>
alkisg: and most of links have your name on it
03:40
<alkisg>
Yeah I think I need to cut down on my IRC time :D
03:40
<Trixboxer>
no please
03:40
:)
03:42
once you spend enogh time here.. there might be some people who will share your unsaid responsibility ( like me ) with required knowledge
03:42
I love IRC.. get help and help other :)
03:50
<Lifeboy>
Anyone? I installed cups and hplip in the chroot originally to try to troubleshoot the printing problem, but since it wasn't printer related I suppose I could remove hplip and cups again?
03:58yanu has quit IRC
04:01
<Lifeboy>
Does anyone know if cups and or hplip has to be installed in the chroot to allow printing to a local printer on a client?
04:01
(For an HP USB printer that is - of course hplip is not needed for other printers)
04:06mikkel has joined #ltsp
04:16
<Lifeboy>
More on the topic of local printing: Does jetpipe use cups to publish the printer?
04:36Hyperbyte has quit IRC
04:42ogra_ac has quit IRC
04:44yanu has joined #ltsp
04:44yanu has joined #ltsp
04:46jhutchins has quit IRC
04:51
<muppis>
Lifeboy, I can't fully recall what I've done, but I think at least cups needed in thin.
04:52sweetpi has quit IRC
05:02bobby_C has joined #ltsp
05:13ogra_ac has joined #ltsp
05:17daya has quit IRC
05:28jhutchins has joined #ltsp
05:52alkisg has quit IRC
05:52alkisg1 has joined #ltsp
06:07otavio has joined #ltsp
06:08[GuS] has joined #ltsp
06:10cyberorg__ has joined #ltsp
06:10cyberorg__ is now known as cyberorg_
06:11cyberorg_ is now known as Guest73571
06:11Guest73571 has joined #ltsp
06:12cyberorg__ has joined #ltsp
06:20bobby_C has quit IRC
06:22
<Lifeboy>
muppis: I have ensured that cups is installed and cups on the server actually connects to the printer on 192.168.8.102:9100. It just doesn't print. It even says in the printer status that the printer is connected!
06:23
There seems to be very little documentation on the details of this. All is assumed to work, but once I've figured it out, I'll add some stuff to the wiki with the info in it.
06:24
<ogra_ac>
generally its very few code thats used on the client
06:24
it is only jetpipe that connects the TCP port directly to the printer device
06:25
no other code is needed, so if you have probs its easy to check whats wrong by just checking port 9100 is available or not
06:25
<Lifeboy>
I tried without cups in chroot, but it doesn't seem to be able to connect to the printer from X then. After I added cups again, it seemed fine.
06:25
<ogra_ac>
ugh
06:25
dont ever install cups in the chroot unless you run a fat client and print locally
06:25
and even then
06:26
drivers and everything else is handled on the server
06:26
if you dont see port 9100 with a single printer attached, debug why jetpipe doesnt run
06:27
<alkisg1>
Does jetpipe work with any printer? Or is it only for some specific hp models?
06:27
<ogra_ac>
jetpipe only connects the lp device to a TCP port
06:27
it does nothing else
06:27
nothing HW specific or anything
06:28
so no, its not printer or vendor specific at all
06:28
its really only a raw datapipe
06:28
Lifeboy, what were the symptoms you had before messing around with your chroot ?
06:29
<alkisg1>
Ah, I thought it was related to jetdirect, which wikipedia says is only for some hp printers... ty
06:29Lifeboy has quit IRC
06:29
<ogra_ac>
you use the jetdirect protocol
06:29
but thats unrelated
06:30
cups does that for any kind of printer ... HP just invented that protocol
06:31
<alkisg1>
So it only does a stream forwarding? Like e.g. inetd or nc does?
06:31
<ogra_ac>
right
06:32Hyperbyte has joined #ltsp
06:32
<ogra_ac>
we should have a printer debugging page so people dont get the insane idea to install cups on the client
06:33
that will very likely end up in race conditions with jetpipe
06:33
and your printer wont print at all
06:38cyberorg__ has quit IRC
06:42Lifeboy has joined #ltsp
06:46
<Lifeboy>
The logs in chroot just have :
06:46
Nov 17 20:47:30 ltsp102 kernel: [ 13.876703] usblp0: USB Bidirectional printer dev 2 if 0 alt 0 proto 2 vid 0x03F0 pid 0x8604
06:46
Nov 17 20:47:30 ltsp102 kernel: [ 13.876987] usbcore: registered new interface driver usblp
06:46
The rest doesn't pertain to printing
06:46
And of course
06:47
roland@ltsp102:~$ netstat -tunap | grep 9100
06:47
(No info could be read for "-p": geteuid()=1000 but you should be root.)
06:47
tcp 0 0 0.0.0.0:9100 0.0.0.0:* LISTEN -
06:47
tcp 68812 0 192.168.8.102:9100 192.168.8.100:33108 ESTABLISHED -
06:47
So the jetpipe is listening
06:50
Here is some more info
06:50
roland@ltsp102:~$ netstat -tunap | grep 9100
06:50
(No info could be read for "-p": geteuid()=1000 but you should be root.)
06:51
tcp 0 0 0.0.0.0:9100 0.0.0.0:* LISTEN -
06:51
tcp 68812 0 192.168.8.102:9100 192.168.8.100:33108 ESTABLISHED -
06:51mistik1_ has joined #ltsp
06:53mistik1 has quit IRC
06:53mistik1_ is now known as mistik1
06:54
<ogra_ac>
Lifeboy, ls -l /dev/usblp0 on your client ?
06:57
as i said above, if you have cups installed while jetpipe is running you will very likely run into race conditions for the device between cups and jetpipe, so your printer wont print at times
06:58
(or even constantly, depending who claims the printer device first)
07:00
<AndyGraybeal>
morning everyone.
07:03mikkel has quit IRC
07:05litlebuda has joined #ltsp
07:19mgariepy has joined #ltsp
07:52bobby_C has joined #ltsp
07:52
<Lifeboy>
ogra_ac: ls -l /dev/usblp0
07:52
lrwxrwxrwx 1 root root 7 2010-11-17 20:47 /dev/usblp0 -> usb/lp0
07:53
<ogra_ac>
so did you try it with /dev/usb/lp0 instead ?
07:54
in lts.conf
07:56
<Lifeboy>
Ok, I missed some stuff that was said re cups in chroot. I'll have to change irc clients. Empathy is not a good one...
07:57
I read it all in the #ltsp logs now, so I'll remove cups again.
07:57
from the chroot that is.
07:58
<ogra_ac>
right, remove cups then chack if jetpipe runs
07:58
<Lifeboy>
jetpipe runs
07:58
<ogra_ac>
if thats the case start looking for the issue on the server side
07:59
<Lifeboy>
the printer doesn'
07:59
t print
07:59
<ogra_ac>
did jetpipe run before you installed cups ?
08:00
<Lifeboy>
Would jetpipe run with the wrong printer setting?
08:00
in lts.conf?
08:00
<ogra_ac>
no
08:00
<Lifeboy>
but jetpipe runs fine now
08:01
<ogra_ac>
but you have cups installed on the client
08:01
jetpipe only check if the device exists
08:01
it doesnt check if it can write to it (since that would print unwanted stuff)
08:01
<Lifeboy>
ok let me first remove that and then we'll see
08:03
<ogra_ac>
if yu have done that and jetpipe still runs fine, start searching for the problem server sided i.e. is the right driver used, is your jetdirect set up properly etc
08:04
jetpipe itself is completely dumb, the original code i wrote was 30 lines, imagine it like a piece of wire, all important stuff happens on the cups server on the server
08:07
there are some HP printers for which you need hplip kernel drivers though, for these you need to run the hplip scripts on the client
08:07
else they wont properly expose their usb device
08:15shawnp0wers has joined #ltsp
08:23
<Lifeboy>
Ok, cups is out and hplip is installed.
08:23
however, if I run hp-setup in chroot it doesn't find a printer
08:23
neither on usb, nor a network printer
08:23
<ogra_ac>
in chroot ?
08:24
<Lifeboy>
yes
08:24
<ogra_ac>
indeed it wont find a printer in a chroot
08:24
so you have a HP printer ?
08:24
<Lifeboy>
:-) no, I expressed myself poorly. I run in an ssh session on the thin client.
08:25
Yes, I have an HP 5443
08:25
deskjet
08:25ogra has quit IRC
08:25
<Lifeboy>
connected to usb0
08:25
the log says:
08:25ogra has joined #ltsp
08:26
<Lifeboy>
Nov 17 20:47:30 ltsp102 kernel: [ 13.876703] usblp0: USB Bidirectional printer dev 2 if 0 alt 0 proto 2 vid 0x03F0 pid 0x8604
08:26
Nov 17 20:47:30 ltsp102 kernel: [ 13.876987] usbcore: registered new interface driver usblp
08:27
that is in /var/log/messages
08:27
<ogra_ac>
looks fine
08:27
so how did you set it up on the server ?
08:27
oh, and is jetpipe still running ?
08:28
(just check with ps )
08:32shawnp0wers has quit IRC
08:32
<Lifeboy>
0:00 /usr/bin/python /usr/sbin/jetpipe -b 9600 -y 8 -p none -x /dev/usblp0 9100
08:32
<ogra_ac>
looks fine
08:32
how is your server set up ?
08:36
<Lifeboy>
I've just asked the client to plug the printer into a different normal desktop computer to see if it works there. I have a suspicion that something has gone wrong with the printer... :-( Once he's completed these tests I'll report back.
08:37
Thanks for all the help so far, ogra_ac and others
08:37
I also aksed him to try another cable for good measure
08:37
I have to run to a meeting, will be back later
08:39Lifeboy has left #ltsp
08:40shawnp0wers has joined #ltsp
09:22Da-Geek has quit IRC
09:39shawnp0wers has quit IRC
09:54alkisg1 is now known as alkisg
10:14staffencasa has joined #ltsp
10:18gnunux has quit IRC
10:18mikkel has joined #ltsp
10:20alkisg has quit IRC
10:33alkisg has joined #ltsp
10:43Mava has quit IRC
10:43Mava has joined #ltsp
10:51dobber has quit IRC
11:06komunista has quit IRC
11:06
<Trixboxer>
alkisg: I have made the necessary changes in lts.conf but still the same user can login from tow places.. and a dialog appears to second user "OK/Cancel" and if he says Ok .. it allows both users to login
11:08
[Default]
11:08
NFS_HOME=/home
11:08
LDM_LIMIT_ONE_SESSION=True
11:08
LDM_LIMIT_ONE_SESSION_PROMPT=True
11:20Trixboxer has quit IRC
11:23robehend1 has quit IRC
11:28shawnp0wers has joined #ltsp
11:44gentgeen__ has joined #ltsp
12:00evil_root is now known as zz_evil_root
12:08alkisg has quit IRC
12:21zz_evil_root is now known as evil_root
12:43shogunx has quit IRC
13:07Gadi has joined #ltsp
13:25alkisg has joined #ltsp
13:35Kicer86 has joined #ltsp
13:37hawkI has joined #ltsp
13:38talntid has joined #ltsp
13:38wideyes has joined #ltsp
13:39
<wideyes>
@alkisg: hey there - just wanted to say I got my setup working, and thanks for your help!
13:39
<alkisg>
You're welcome
13:40
<wideyes>
as you may recall, I had initially copied my tftboot setup files over to my dhcp server, which was separate from my ltsp server
13:40
I was messing around with the next-server directive
13:41
the dhcp setting that I found worked was simply to leave out the next-server AND the root-path options altogether
13:42
my pxelinux.cof/default settings linked to the nbd server on the ltsp station
13:43
I thought I had tried all of that. I think what made the difference was nixing the root-path option
13:43
I remembered that we had left off on that note, so I wanted to fill you in on what ended up working
13:55[GuS] has quit IRC
14:03
<wideyes>
I do have one further question, though: in my lts.conf file, I'm getting strange results when I try to activate a shell using the SCREEN_0X option
14:04Hyperbyte has quit IRC
14:05
<wideyes>
when specifying this, I found that setting SCREEN_07=ldm was the only way to get an ldm login screen at bootup. Fair enough, but when I Ctrl+Alt+F key, it goes to what looks like a login for the local machine, but no username I've tried works
14:05
using SCREEN_02=shell, for example
14:06
but after a moment, what looks like a logged-in root shell will popup, but as soon as I hit enter, it will ask me to login to the local client again
14:06
it's very strange
14:09
<alkisg>
wideyes: about the dhcp server, it'd be best if you specified the next-server, so that you don't have to transfer your ltsp kernels every time you update the chroot
14:10
!SCREEN_02
14:10
<ltspbot>
alkisg: "SCREEN_02" :: (#1) To get a root shell on an Ubuntu thin client, put these in your lts.conf: (default <name>) -- Returns the default value of the configuration variable <name>. {enter}SCREEN_02=shell{enter}SCREEN_07=ldm{enter}. Then reboot the client, and press Alt+Ctrl+F2 to get to the root shell., or (#2) for Debian use SCREEN_07=ldm, SCREEN_08=shell and SCREEN_DEFAULT=07
14:10
<alkisg>
Ugh that's messed up now
14:10
vagrantc, use SCREEN_08 for debian, don't change the ubuntu one :D
14:11
!forget SCREEN_02
14:11
<ltspbot>
alkisg: Error: 2 factoids have that key. Please specify which one to remove, or use * to designate all of them.
14:11
<alkisg>
!forget SCREEN_02 *
14:11
<ltspbot>
alkisg: The operation succeeded.
14:11hersonls has joined #ltsp
14:12
<alkisg>
learn SCREEN_02 as To get a root shell on an Ubuntu thin client, put SCREEN_02=shell and SCREEN_07=ldm in /var/lib/tftpboot/ltsp/i386/lts.conf. Then reboot the client, and press Alt+Ctrl+F2 to get to the root shell.
14:12
!learn SCREEN_02 as To get a root shell on an Ubuntu thin client, put SCREEN_02=shell and SCREEN_07=ldm in /var/lib/tftpboot/ltsp/i386/lts.conf. Then reboot the client, and press Alt+Ctrl+F2 to get to the root shell.
14:12
<ltspbot>
alkisg: The operation succeeded.
14:12
<alkisg>
!learn SCREEN_08 as To get a root shell on a Debian thin client, put SCREEN_07=ldm, SCREEN_08=shell and SCREEN_DEFAULT=07 to lts.conf.
14:12
<ltspbot>
alkisg: The operation succeeded.
14:14
<alkisg>
wideyes: so for a local root shell, you may try setting both SCREEN_02=shell and SCREEN_07=ldm.
14:39hersonls has quit IRC
14:45Kicer86 has quit IRC
14:55
<wideyes>
sorry alki, was pulled away from work
14:55
yes, I tried that setting as you suggested
14:56
I also tried many others, such as putting SCREEN_01-SCREEN_06 all as shell, followed by SCREEN_07 as ldm
14:56
like a typical linux setup
15:00
although, testing it right now to give you some more feedback, it works like it should
15:00
for the first time
15:00
man, you're good, alkisg!
15:01
I'll test it a little more
15:03shogunx has joined #ltsp
15:14Gadi has left #ltsp
15:26gentgeen__ has quit IRC
15:27evil_root is now known as zz_evil_root
15:29zz_evil_root is now known as evil_root
15:33mikkel has quit IRC
15:43Kyle__ has quit IRC
15:45mgariepy has quit IRC
15:53hawkI has quit IRC
15:57Kyle__ has joined #ltsp
16:03wideyes has quit IRC
16:03Hyperbyte has joined #ltsp
16:37ogra_ac_ has joined #ltsp
16:37ogra_ac has quit IRC
16:38ogra_ac_ is now known as ogra_ac
16:42alkisg has quit IRC
17:19jhutchins_kc has joined #ltsp
17:25jhutchins has quit IRC
18:41staffencasa has quit IRC
18:46cliebow has joined #ltsp
19:04bobby_C has quit IRC
19:14
<AndyGraybeal>
i'm on cellular modem at home, no more dial-up :)
19:21litlebuda has joined #ltsp
19:27evil_root is now known as zz_evil_root
20:01
<cliebow>
AndyGrayBeal: i am doing apple training in Boston
20:15zz_evil_root is now known as evil_root
20:24cliebow has quit IRC
20:32evil_root is now known as zz_evil_root
20:34zz_evil_root is now known as evil_root
21:04cyberorg has quit IRC
21:12litlebuda has quit IRC
21:12M4gic5t0rM has joined #ltsp
21:14M4gic5t0rM has quit IRC
21:28daya has joined #ltsp
21:34mistik1 has quit IRC
22:02mistik1 has joined #ltsp
22:03daya has quit IRC
22:04sweetpi has joined #ltsp
22:11cyberorg has joined #ltsp
23:17evil_root is now known as zz_evil_root