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


Channel log from 11 January 2008   (all times are UTC)

00:08rcy is now known as notrcy
00:17tier1 has quit IRC
00:26notrcy is now known as rcy
00:32cyberorg has quit IRC
00:39basanta has joined #ltsp
00:48zodman has quit IRC
00:49jernst has joined #ltsp
00:50zodman has joined #ltsp
01:08ace_suares has quit IRC
01:09Q-FUNK has quit IRC
01:11chup has joined #ltsp
01:13chupa has quit IRC
01:30chupa has joined #ltsp
01:32chup has quit IRC
01:42ogra has quit IRC
01:45daya has quit IRC
01:54plamengr has joined #ltsp
01:55wdg has joined #ltsp
01:57ogra has joined #ltsp
02:07mcfloppy_ has quit IRC
02:10aboo0ood has quit IRC
02:15Egyptian[Home] has joined #ltsp
02:17cyberorg has joined #ltsp
02:19nentis has quit IRC
02:21tuukka has joined #ltsp
02:23
<tuukka>
hi! i've created a file to /etc/X11/Xsession.d/ which works as a login script. but any pointers where i should put corresponding logout script??
02:26
hups... and it should be run everytime someone logs out (it would unmount things that are mounted on login)
03:09makghosh is now known as makghosh|afk
03:11cyberorg has quit IRC
03:35makghosh|afk is now known as makghosh
03:51
<tuukka>
hmm ... does anyone have any idea what files are run when user logs out?? if it's pure logout, then I can't use runlevel-files, right??
03:52
<vagrantc>
tuukka: there usually isn't much of a logout mechanism
03:53
tuukka: and if you did find a place to hook into, your scripts would have to handle an unclean logout
03:55
<tuukka>
vagrantc: Thanks for your answer. so if i want mounted things to be unmounted on logout i have no proper place to do it manually?? i'd had to use ie. pam-mount, autofs..??
03:55
<vagrantc>
tuukka: what are you trying to unmount, and from where?
03:55
tuukka: are you using LDM ?
03:57
<tuukka>
vagrantc: i'm mounting win2003 user folders from win box usings cifs ... they're mounted on login to users home folder...
03:57
<vagrantc>
tuukka: what are you logging in with?
03:58
<tuukka>
with basic thin clients.... (sorry i propably understood your question wrong?!)
03:59
<vagrantc>
tuukka: what linux distro are you using?
03:59
<tuukka>
edubuntu
03:59
7.10 gutsy
03:59
<vagrantc>
got it
03:59
and you're using LDM ?
03:59
<tuukka>
sorry, but LDM ?? (logical disc manager??)
04:00
<vagrantc>
LTSP Display Manager
04:00
tuukka: did you change lts.conf ?
04:00
if you went with a default LTSP install, then you're using LDM.
04:00
<tuukka>
vagrantc: no
04:00
yep, i went with default one
04:01
<vagrantc>
and then things like pam-mount may not work so well
04:01
unless the mount commands don't require root privledges
04:01
<tuukka>
hmm ... okay ... this is the last thing before our school having a first linux-lab, damn...
04:01
they don't require
04:02
<vagrantc>
tuukka: it's a per-user cifs mount?
04:02
<tuukka>
i can use umount-cifs which can be run without root privs
04:02
yep...
04:04
hmm ... if i create a desktop shortcut for each user which name would be something like "logout" ... then i would be able to unmount stuff and force logoff?! could this work?? (i know it's a lousy thing to do but i'm starting to be desperate about this)
04:04
<vagrantc>
maybe
04:04
<tuukka>
by desktop shortcut, i mean a shortcut to a bash script...
04:04
<vagrantc>
you might be able to hook into gnome as well
04:04
that actually does have some login/logout mechanisms
04:05
<tuukka>
okay, that sounds good! it wouldn't be that dangerous if one or two mounts are left open because they are checked again on next login ...
04:06
<vagrantc>
mind you, i don't know how to use them, but they exist :)
04:06
<tuukka>
thanks a lot ... i think i'll first look into gnome logout things and if that doesn't go anywhere i'll try to create a script that i assume users are going to use to logout :)
04:09
<ogra>
vagrantc, what are you doing in my timezone ?
04:09
<vagrantc>
ogra: ?
04:09
<ogra>
(why are you up ?)
04:09
<vagrantc>
heh
04:09
oh, just got in the habit of staying up late
04:10
<ogra>
ah, i know how that goes :)
04:10* vagrantc is learning about raid10
04:14zodman has quit IRC
04:15
<ogra>
thats fun :)
04:15
<vagrantc>
really, i'd best be doing some experiential learning about dreaming
04:19
<ogra>
ah, well
04:19
i did some nightshifts as well during holiday o build my new machine :)
04:20
actually two .... an apt-proxy machine and an ultrafast build server that's also my new ltsp testmachine :)
04:20
with this setup i can build a client in 10 min (including squashfs :) )
04:21
its really fun to do heaviy lifting work on a fast machine
04:27elisboa has quit IRC
04:44jernst has left #ltsp
04:44vagrantc has quit IRC
05:02soneyka has quit IRC
05:02open_lad has quit IRC
05:08tuukka has quit IRC
05:18basanta has quit IRC
05:40wdg has quit IRC
05:50cyberorg has joined #ltsp
05:50wdg has joined #ltsp
05:58otavio has quit IRC
06:00otavio has joined #ltsp
06:11Guaraldo has joined #ltsp
06:22daduke has quit IRC
06:23exodos has joined #ltsp
06:34putty_thing is now known as jim``
06:35elisboa has joined #ltsp
06:39open_lad has joined #ltsp
06:45cliebow has joined #ltsp
06:46open_lad has quit IRC
06:54rjune_ has quit IRC
07:00rjune_ has joined #ltsp
07:01cyberorg has quit IRC
07:13mattwalston has joined #ltsp
07:15
<mattwalston>
Is it possible to have local applications and remote applications share the same screen?
07:18
<sep>
ssh -X user@remotemachine xeyes
07:32Guaraldo has quit IRC
07:32Guaraldo has joined #ltsp
07:33val_ has joined #ltsp
07:33val_ is now known as soneyka
07:35
<mattwalston>
sep: thanks
07:50soneyka has quit IRC
07:53jammcq has joined #ltsp
07:55
<Big-K>
hi guys, i always like getting held from you ;)
07:56
does a thin client read a xorg.conf in /opt/.../etc/X11/
07:56
sry I meant help :D
08:00
<sep>
Big-K, dont think so, but there is a lts.conf option to specify a xorg conf file to use
08:01
Big-K, should be easy to try tho.
08:01
<Big-K>
yeah
08:02
I'm a little bit confused by ltsps behaviour ...
08:03soneyka has joined #ltsp
08:04Q-FUNK has joined #ltsp
08:04wdg has quit IRC
08:06slidesinger has joined #ltsp
08:07
<Big-K>
could I post my xorg.conf somewhere?
08:10K_O-Gnom has joined #ltsp
08:13LTSP07 has joined #ltsp
08:13
<soneyka>
Big-K http://rafb.net/paste/
08:16
<Big-K>
http://rafb.net/p/Q5Ksh024.html
08:16
so please, what's wrong?
08:22cyberorg has joined #ltsp
08:24
<LTSP07>
i've setup ltsp 5 on edubuntu and have tried various video cards for the thin clients and even with correct and detailed setting within lts.conf I keep on getting 800x600 at best as the highest resolution, any ideas why? thanks
08:25
<Big-K>
try putting X_MODE_0=1280x1024 in your lts.conf
08:25
or any other resolution
08:25bobby_C has joined #ltsp
08:26
<LTSP07>
i was testing with s220 and s3virge i don't think it can go that high but i did set it to 1024x768
08:26
even tried with all the other options for 60hz
08:26
same results
08:27
<slidesinger>
LTSP07: Have you tried different monitors?
08:27
<LTSP07>
it only responds to color depth settings such as 8, 16, 24
08:27
<ogra>
Big-K, your x config is generated during boot if you dont fiddle with lts.conf, if you want vesa why dont you just set XSERVER=vesa
08:27
<Big-K>
thx ogra
08:27
<LTSP07>
slidesinger: yes
08:27
<Big-K>
I got that entry
08:27
my problem is the following
08:28
everything is fine, login, resolution ...
08:28makghosh has quit IRC
08:28
<Big-K>
but if i wanna restart the xserver or logout ...
08:28
screen remains black
08:29
<slidesinger>
Have you tried a card and monitor combination that you have been able to get 1024x768 from a live linux cd (dsl, gnoppix, knoppix and, of course, edubuntu?)
08:31
<Big-K>
does the thin client switch to the xorg.conf when restarting the xserver
08:31
?
08:31
<slidesinger>
LTSP07: Basically the steps are as follows: you need to completely eliminate the possibility that hardware is the problem then, if you still have a problem, work on the software side.
08:33K_O-Gnom has quit IRC
08:34
<ogra>
Big-K, it uses the same one it used to ring up ldm the first time ....
08:34
that sounds liek a different issue, not config related
08:34
*like
08:34
<Big-K>
hmmm ok thx
08:36
<ogra>
can you start with a shell on tty2 and check if there are any errors in ldm.log or the X logfiles ?
08:37
<Big-K>
SCREEN_02 = shell option in lts.conf, right?
08:37Q-FUNK has quit IRC
08:38Gadi has joined #ltsp
08:39Guaraldo has quit IRC
08:44
<ogra>
right
08:45
and SCREEN_07=ldm
08:45
(else you boot without any X, thats not what we want)
08:45
<Big-K>
ah ok thx
08:45
thatswhy there are no logs?!
08:46
<ogra>
well, if X doesnt start it wont log anything :)
08:50
<Big-K>
it starts
08:51
<ogra>
then you should have something in /var/log on the client
08:51
<Big-K>
yeah ...
08:51
but don't see any errors
08:51
only an no acpi warning
08:52
problem is ...
08:52
if I don't login, restarting the xserver with ctrl+alt+backspace works fine
08:52
but if i login and try to restart it, it fails
08:54
<mattwalston>
What is the best way to just use a custom x.org file? Can it load through config file or just put it in chrooted /etc/X11?
08:55
<ogra>
mattwalston, both
08:55
<mattwalston>
Why do kernel messages not start on first charecter it is almost like a bad terminal type or something? Any fix?
08:55
<ogra>
you need to put it into the chroot (with newer implementations you also need to run ltsp-update-image) and make the system aware that the file is there through an lts.conf entry
08:56* ogra works on ubuntu, we dont have kernel messages on the screen
09:00
<mattwalston>
ogra: I killed graphical boot so I don't get asked what the hell is ubuntu
09:05
<ogra>
www.ubuntu.com ?
09:06
the OS where ltsp5 got developed under
09:06
<johnny>
by his users ogra :)
09:06
<ogra>
nah, not by me ... i must admit that i only took overthe design skeleton from mdz :)
09:07
much of the flesh is mine though :)
09:07
<johnny>
he doesn't want his users asking what ubuntu is
09:07
<ogra>
(probably a third of what was developed in the last two years)
09:07
<johnny>
and bugging him about it :)
09:11tux_440volt has joined #ltsp
09:12
<mattwalston>
More specifically, I see no reason why this pile of LT210 el cheapo terminals can'
09:12
~'t do the job of these expensive HPs they are thinking of buying
09:14
we are not a school, this is not my basement, this is a 80 user deployment where none of the users are trained on using a linux desktop... we need baby steps
09:15
<Gadi>
mattwalston: grab the company logo and roll your own boot splash
09:15
<mattwalston>
Gadi: good idea, there is an easier answer
09:22
where is the example lts.conf?
09:24
<Big-K>
find -name lts.conf
09:28mikkel has joined #ltsp
09:30
<mattwalston>
I have having responsiveness issues,,, will disabling network compression and using LDM_DIRECTX help?
09:30
<Gadi>
mattwalston: try disabling logging
09:30
wait - what kind of responsiveness?
09:31
u mean video ?
09:31
in that case, yes
09:31
<mattwalston>
yes
09:31
video
09:31
<Gadi>
set LDM_DIRECTX = True
09:31plamengr has quit IRC
09:31
<Gadi>
world of difference
09:31
<mattwalston>
Gadi: what about NETWORK_COMPRESSION? good bad or otherwise?
09:32
<Gadi>
if you set LDM_DIRECTX it wont matter
09:32
one way or the other
09:32
<mattwalston>
Gadi: oh ok
09:32
<Gadi>
the video will no longer be over ssh
09:32
hence the "DIRECT X " part
09:32
<mattwalston>
Gadi: is there a directive to disable logging in lts.conf?
09:32
<Gadi>
if you disable the remote logging feature on the server's syslog, it will in effect disable it
09:33
<mattwalston>
Gadi: oh ok
09:33
<Gadi>
I only mentioned that bec I have had a few setups where logging made a huge delay in the initial ssh connection (delaying login)
09:33
<mattwalston>
oh i see
09:34
i also notice the login takes a little longer on ldm than on local gdm, like about 3 seconds or so after typing password, it says verifying password
09:36
<Gadi>
mattwalston: yeah, well it has to negotiate the ssh connection
09:37
<mattwalston>
oh ok
09:38spectra has joined #ltsp
09:45rasmuson has joined #ltsp
09:50K_O-Gnom has joined #ltsp
09:52tux_440volt has quit IRC
09:53laga has joined #ltsp
09:54mattwalston has quit IRC
09:57slidesinger has quit IRC
10:07sonjag has joined #ltsp
10:11lns has quit IRC
10:22cyberorg has quit IRC
10:24cyberorg has joined #ltsp
10:24sepski has joined #ltsp
10:39staffencasa has joined #ltsp
10:46comperr has left #ltsp
10:47comperr has joined #ltsp
10:53
<Ryudo>
gadi :D
10:53
i'm back :D
10:53
dia you can help me ? about this workaround to fix my local devices bug
10:56
<Gadi>
Ryudo: I am here - sorry about yesterday - can you paste that ldm again?
10:56
!pastebot
10:56
<ltspbot>
Gadi: "pastebot" is The LTSP pastebot is at http://pastebot.ltsp.org. Please paste all text longer than a line or two to the pastebot, as it helps to reduce traffic in the channel. A link to the content will be pasted in the channel.
10:57
<Ryudo>
es
10:57
yes
10:57
i need the woraround and the exactly line i put him in ldm script
10:57
before xsession
10:58
<comperr>
is the source to that bot around- it looks cool ?
10:58
<ltsppbot>
"test" pasted "test" (1 line) at http://pastebot.ltsp.org/410
11:00
<Ryudo>
gadi ?
11:00
<Gadi>
sorry
11:00
too many distractions
11:00
im here
11:01
pastebot is empty
11:01
did you paste the contents of the file?
11:05
<Ryudo>
ok !
11:05
did you wcan wait ?
11:06
i need power on my server
11:06
<Gadi>
Im around for another ~2hrs
11:07
<Ryudo>
whats o clock in your city ?
11:07chup has joined #ltsp
11:09chupa has quit IRC
11:12
<Gadi>
im in USA/NYC
11:12
EST
11:12
its 12:12PM atm
11:13laga has left #ltsp
11:17psycodad has joined #ltsp
11:18yemu has joined #ltsp
11:19
<yemu>
hi, i have a problem with thin clients, i have to identical monitors but one of them boots into 800x600 and other 1024x768?
11:20
is it possible to force resolution to clients?
11:20
<Gadi>
X_MODE_0 = "1024x768"
11:21
CONFIGURE_X=True
11:21
<yemu>
thx, i'll try that
11:22
and how to force x driver to intel?
11:23
<Gadi>
XSERVER=intel
11:26
<yemu>
Gadi: hm, it didn't help... :-(i still get 800x600, i also add X_COLOR_DEPTH=16 and it was applied do the config file is being read
11:28
<Gadi>
open a terminal window and type: xrandr -q
11:28
do you have higher modes?
11:29
its a function of: 1. your driver, 2. your video memory, 3. your monitor
11:29
if you login to the thin client's console, you should be able to look a the logs and find out what is really happening
11:30
(ie /usr/log/Xorg.6.log
11:30
<yemu>
i don't have higher modes listed by xrandr
11:30
on the other terminal on which higer resolution works they
11:30
re listed
11:30
<Gadi>
are they different thin client models?
11:31
<yemu>
yes they are - both compaq but one pIII and the other pII
11:32
<Gadi>
which one is 800x600?
11:32
<yemu>
pIII
11:32
but i have other pIII
11:33
and it works ok
11:33
it's really strange
11:33
<Gadi>
and you are sure it is an intel video chip?
11:33
<yemu>
actually i'm not
11:33
<Gadi>
go into the BIOS and check how much video memory is allocated
11:33
<yemu>
and probably it's not
11:33
<Gadi>
oh, and then check the video chip driver :0
11:33
:)
11:34
find out what driver it has
11:34
then, we should be able to find a fix
11:35
<yemu>
i got into the bios
11:35
but there's no option to change video ram ;-)
11:35
<Gadi>
ok
11:35
could be its onboard
11:35
<yemu>
so probably it onboard
11:35mikkel has quit IRC
11:37
<yemu>
i have to leave for a moment to check the video card
11:37
i'll be back in a moment (i hope) ;-)
11:37yemu has left #ltsp
11:41exodos has quit IRC
11:45
<LTSP07>
Gadi: maybe you can help me figure out why all of PCs that I'm using via ltps 5 running on edubuntu default to 800x600, I've checked that xorg server for s3 / s3virge is installed and specified the ram amount (4MB) etc... even tried X_MODE_0 with the settings for 1024x768 @ 60hz
11:46
still boots to 800x600, at the same time works at correct resolutions with livecd
11:47
i've also tried auto and vesa for XSERVER still get 800x600
11:53
<Gadi>
LTSP07: first, did you verify that the settings are taking effect - always good to be able to switch to a shell on the thin client and see what /etc/X11/xorg.conf got written
11:53
also, I assume you set: CONFIGURE_X=True
11:53
because, by default, it won't make/use a xorg.conf
11:54lns has joined #ltsp
11:55vagrantc has joined #ltsp
11:56
<vagrantc>
otavio: how goes? :)
11:56
<LTSP07>
Gadi: just want to make sure - configure_x is a param within lts.conf is that correct or xorg.conf?
11:57
<Gadi>
lts.conf
11:58
<LTSP07>
Gadi: I only tried making changes through lts.conf at this point by the way on edubuntu it's in a different location
11:58
<Gadi>
on gutsy, it is in /var/lib/tftpboot/ltsp/i386/
11:59
<LTSP07>
correct
11:59
<Gadi>
ever since we went to exporting an *image* rather than a *filesystem*, we wanted a way to update lts.conf without having to reroll the image
11:59
<LTSP07>
let me try your option CONFIGURE_X=True
11:59
<Gadi>
so, now we tftp it down on boot
11:59
hence the change in location
11:59
<LTSP07>
sure makes sense
12:00
takes a while to reroll that image
12:00
<Gadi>
sure can
12:00
:)
12:00
also, updating a config should be more common than updating an image
12:00
:)
12:06
<lns>
Hey all
12:08
<otavio>
vagrantc: fine! working...
12:08
<lns>
I just got back from testing a new site with 35 eager elementary school students and Ubuntu Gutsy LTSP ;) Aside from the (normal) Firefox/OpenOffice clipart pixmap/crash issues (which I know are being worked on) and the tuxmath/tuxtyping just-plain-not-ready-for-ltsp thing, there was a strange crash that cropped up after the students left and I was just on Firefox googling around...here's what happened after the X session locked up completely and I CTRL+ALT+F1:
12:08
<Gadi>
vagrantc: saw you email to the listserv - is your system on crack?
12:09
<vagrantc>
Gadi: well, i've actually heard bug reports that suggest others are affected
12:09
<Gadi>
vagrantc: ah
12:09
<lns>
"nbd0: Attempted send on closed socket" (this shows about 15 times) - and then: "SQUASHFS error: sb_bread failed reading block 0x54d7 -- SQUASHFS error: Unable to read fragment cache block (152f -- SQUASHFS error: Unable to read page, block 152f944, size ..."
12:09
<Gadi>
but a very weird bug
12:10
lns: did your squshfs image get corrupted?
12:10
<lns>
Gadi, i really don't think so, i don't see how it could
12:10
<Gadi>
lns: sure sounds like it
12:11
try an : ltsp-update-image
12:11
<lns>
i was thinking more of a network hickup...could that have caused it too?
12:11
<Gadi>
could be
12:11
<lns>
i'll try that
12:11
<Gadi>
could be the nbd server died
12:12
if ltsp-update-image doesnt cure it
12:12
<lns>
rebuilding it now (remotely)
12:12
<Gadi>
then, have a look at the running nbd-server processes
12:12
<lns>
ok
12:13
thanks =) I was very impressed, actually, with the latest Flash RC - all 35 students were in a game called "MultiFlyer" (graphics intensive flash game) and it didn't experience much more than pegging out the server cpu
12:14
<vagrantc>
otavio: do you think you'll have time for the uploads today?
12:14
<lns>
Gadi, I have about 30 lines of this:
12:14
nobody 7785 0.0 0.0 3428 968 ? S Jan10 0:00 /bin/nbd-server 0 /opt/ltsp/images/i386.img -r -C /dev/null
12:14
nobody 7824 0.0 0.0 1756 500 ? Ss Jan10 0:00 /bin/sh /usr/sbin/nbdrootd /opt/ltsp/images/i386.img
12:15
no one (should) be logged in or even booted up to a thin client
12:15
<Gadi>
lns: ah, then, yeah thats an issue
12:16
if the thin clients are powered off, you should probably kill all of the nbd-server procs
12:16
<lns>
is there a better fix for this than manually killing procs?
12:16
<Gadi>
well, the qu is why is it happening
12:17
<lns>
right
12:17
<Gadi>
can you make sure you have the following line in /etc/hosts.allow:
12:17
nbdrootd: ALL: keepalive
12:17* Gadi thinks that line is needed for proper operation
12:17
<Gadi>
albeit the syntax is counter-intuitive
12:18
<lns>
yep, that's there
12:18
nbdrootd: ALL: keepalive
12:18
<Gadi>
hmm
12:18
managed switch?
12:18
<lns>
definitely hypocritical syntax. ;)
12:18
yes
12:18* sutula recalls struggling with nbd processes that didn't die and swapfiles left around, but that line fixed it for him
12:19
<Gadi>
perhaps its the switch...
12:19
hmm
12:19
damn switches get too smart
12:19
<lns>
lol
12:19
<johnny>
they think they are smarter than you
12:19
<lns>
the server's an HP proliant ML370G5 w/gigabit NIC
12:20
<Gadi>
nbdrootd (which wraps nbd-server) is called from inetd
12:20
<lns>
3COM switch modules
12:20
<Gadi>
inetd services should die when no longer accessed
12:20
on the port
12:20
but, if the port is kept open....
12:21
<otavio>
vagrantc: yes..
12:21
vagrantc: sure
12:21
vagrantc: why?
12:21
<lns>
Gadi, what's (possibly) keeping it open on the switch?
12:22* Gadi shrugs - some switches will kill idle connections after a while, some will never kill idle connections and keep them up
12:23
<Gadi>
the smarter the switch, the more it tries to interfere
12:23
:)
12:23
<lns>
Gadi, well the machines themselves are booted up - into local windows 2000 installs now though
12:23
<Gadi>
ah
12:23
<lns>
oo, check this out when i try to restart nbd-server...
12:23
<Gadi>
next time you are onsite, try rebooting the switch and see if it clears things up
12:23
<lns>
** (process:27272): WARNING **: Could not parse config file: Unknown error
12:23
** Message: Nothing to do! Bye!
12:24
<Gadi>
dont start nbd-server by hand
12:24
it runs from inetd
12:24
<vagrantc>
otavio: maybe i'm just impatient ? :)
12:24
<lns>
ah..ok nm ;)
12:24
<Gadi>
and doesnt use a config file
12:24
_hence the -C /dev/null)
12:24
<vagrantc>
otavio: you did get the upload emails?
12:24
<lns>
rebooting the switch might be an issue since the school uses it all the time.. i might be able to do it after 3...
12:25
<Gadi>
lns: ah, ok - just a test
12:25
to test the theory
12:25
hopefully its not the switch
12:25
<lns>
gotcha
12:25* Gadi wonders if nbd has a heartbeat of sorts - im sure it does
12:25
<lns>
yeah...i can't really think of any switch parms that would want to keep certain port connections alive
12:26
<johnny>
aka.. keepalive..?
12:26
lol
12:27
<lns>
=p but only for certain layer 3 (is it l3?) connections?
12:30
nothing looks out of the ordinary in logs...
12:33
<otavio>
vagrantc: i did, will do then in few minutes
12:34
<vagrantc>
otavio: thanks :)
12:43
<lns>
is there an lts.conf setting to enable numlock for the clients?
12:55gale1 has joined #ltsp
12:56
<Gadi>
lns: no, but you could: apt-get install numlockx on the server and add a startup script to run: numlockx on
12:56gale1 has left #ltsp
12:57gale1 has joined #ltsp
12:58gale1 has left #ltsp
12:58gale1 has joined #ltsp
12:59
<gale1>
kjb
12:59wizzy__ has quit IRC
12:59gale1 has left #ltsp
13:05ltsp has joined #ltsp
13:05
<ltsp>
gadi
13:05
i'm back
13:06
i have the ldm code here
13:06
i'm ryudo
13:07
<Gadi>
ok
13:12
<ltsp>
i paste here ?
13:12Guaraldo has joined #ltsp
13:12
<Gadi>
!pastebot
13:12
<ltspbot>
Gadi: "pastebot" is The LTSP pastebot is at http://pastebot.ltsp.org. Please paste all text longer than a line or two to the pastebot, as it helps to reduce traffic in the channel. A link to the content will be pasted in the channel.
13:12Guaraldo has left #ltsp
13:14
<ltsp>
gadi: http://alburg.net/ldm
13:18
gadi: http://alburg.net/ldm
13:18
<Gadi>
ltsp: got it
13:19
well, lets see...
13:19
<cliebow>
woot!!! remote install "just worked"
13:19
<Gadi>
actually, you can probably do this without changing ldm
13:20
<ltsp>
goood !
13:20
<Gadi>
ltsp: try addind a script in /etc/X11/Xsession.d/ on the server near the beginning, say: 01ltspfscleanup
13:20
and put in it just:
13:20
ltspfsmounter cleanup all || true
13:21
and see if that helps
13:21
it might need: /usr/sbin/ltspfsmounter
13:21
(ie the full path)
13:21
<ltsp>
i try it ,wait one minute
13:22
sudo nano /etc/X11/Xsession.d/01ltspfscleanup
13:23
tspfsmounter cleanup all || true
13:23
i test it now :D ehehe
13:23
<Gadi>
that should be: ltspfsmounter
13:23
'l' not 't'
13:23
typos for sure wont work :)
13:24
<ltsp>
oh ok
13:24
time to test :O
13:27
ltsp@ltsp:~$ sudo cat /etc/X11/Xsession.d/01ltspfscleanup
13:27
ltspfsmounter cleanup all || true
13:27
wont work :(
13:28
i reboot one terminal in live session, after reboot floppy dont work more
13:28
gadi
13:29K_O-Gnom has quit IRC
13:36
<ltsp>
gadi :(
13:40ltsp has quit IRC
13:40sonjag has quit IRC
13:47
<Gadi>
sorry - ph call
13:50
<Ryudo>
gadi dont work this workaround
13:50
:(
13:59
<Gadi>
Ryudo: hmm...
13:59
<Ryudo>
gadi i dont put the complete path
13:59
ltsp@ltsp:~$ sudo cat /etc/X11/Xsession.d/01ltspfscleanup
13:59
ltspfsmounter cleanup all || true
13:59
<Gadi>
try the full path
14:00
<Ryudo>
the correct is /usr/sbin/ltspfsmounter ?
14:00
<Gadi>
ah
14:00
yeah
14:00
I think
14:00
type: which ltspfsmounter
14:00
<Ryudo>
ok i try again
14:00
whereis ltspmounter ?
14:03
<Gadi>
which ltspfsmounter
14:03
nm - it is: /usr/sbin/ltspfsmounter
14:04
Ryudo: gotta go in a few mins
14:08nicoAMG has joined #ltsp
14:08
<vagrantc>
putting it in /etc/X11/Xsession.d/ might clean it out after the other mounts happen...
14:09
<Gadi>
yeah
14:10
i was hoping to catch it before delayed_mounter kicked in (this is feisty)
14:10
Ryudo: any chance you could upgrade to gutsy?
14:10
<vagrantc>
ah
14:11
<Gadi>
then, we can do this in a better way with ldm rc.d scripts
14:11
<vagrantc>
might be a good thing to do by default
14:11
on initial login
14:11* Gadi nods
14:14
<klausade>
vagrantc: i just tried 5.0.39debian1~40.etch.0, it build just fine, and using boot=nfs it even boots up :-) Bot no X yet.
14:14cliebow has quit IRC
14:17
<vagrantc>
klausade: yeah, sometimes X doesn't work so well
14:17
klausade: i'll work on backports of the versions in sid this coming week
14:18
klausade: did you try the instructions for switching to xdebconfigurator for X configuration?
14:18Gadi has left #ltsp
14:18
<vagrantc>
klausade: then it should work at least as good as the older versions as far as X configuration
14:20
<klausade>
vagrantc: tried xdebconf, no luck (on first try)
14:20ltsp has joined #ltsp
14:20
<ltsp>
gadi
14:20
wount work
14:20
i try use this comand in my server
14:20
look
14:21ltsp has quit IRC
14:22
<klausade>
vagrantc: it's still "pkill ldm;pkill X;/etc/init.d/ltsp-client-core start" after I manually edit xorg.conf on the client?
14:22
<vagrantc>
klausade: oh, i always just reboot
14:23
restarting is likely to cause other weirdnesses ...
14:23
restarting ltsp-client-core, that is
14:24
we should clean that up someday...
14:33
<Ryudo>
vagrantc thats command /usr/sbin/ltspfsmounter cleanup all || true return a erro look:
14:33
ltsp@ltsp:~$ sudo ltspfsmounter cleanup all || true
14:33
Traceback (most recent call last):
14:33
File "/usr/sbin/ltspfsmounter", line 85, in <module>
14:33
main()
14:33
File "/usr/sbin/ltspfsmounter", line 72, in main
14:33
conn = get_var('SSH_CONNECTION').split()[0]
14:34
AttributeError: 'NoneType' object has no attribute 'split'
14:34
<vagrantc>
Ryudo: are you logged in from the thin client?
14:34
no need to run it with sudo
14:34
actually
14:34
<klausade>
vagrantc: rebooting when editing the xorg.conf on the client ....
14:34
<Ryudo>
i put this command in this file /etc/X11/Xsession.d/01ltspfscleanup
14:35
i test it on my server
14:35
<klausade>
vagrantc: /etc/init.d/ltsp-client-core start works very well in 5.0.8debian3
14:35pimpministerp has joined #ltsp
14:35primeministerp has quit IRC
14:36
<vagrantc>
klausade: well, i'd define custom X conf in X_CONF=/path/to/custom/xorg.conf in lts.conf
14:36
<Ryudo>
i use the command in my server , testing
14:36pimpministerp has quit IRC
14:44
<LTSP07>
Gadi: configure_x didnt make a difference, I'm still getting 800x600 as default resolution for all thin clients, if you have any other suggestions I would appreciate it, thanks
14:56vagrantc has quit IRC
15:07zodman has joined #ltsp
15:15nicoAMG has quit IRC
15:17zodman has quit IRC
15:24gentgeen__ has joined #ltsp
15:27nicoAMG has joined #ltsp
15:27zodman has joined #ltsp
15:45chupa has joined #ltsp
15:47chup has quit IRC
15:48otavio has quit IRC
16:29nicoAMG has quit IRC
17:25loather-work has quit IRC
17:27LTSP07 has quit IRC
17:27loather-work has joined #ltsp
17:41jammcq has quit IRC
17:48bobby_C has quit IRC
17:50sepski has quit IRC
18:12`Matir has joined #ltsp
18:12`Matir has left #ltsp
18:34ltsp has joined #ltsp
18:46twinprism has quit IRC
18:52rasmuson has quit IRC
18:59staffencasa has quit IRC
19:10
<lns>
Do any devs here do 'sub-contracting' scripting/coding work for LTSP (fixing bugs with LTSP, Gnome, other related software) with implemented networks, feature requests)? If so, raise your hand or msg me
19:14
<iMacGyver>
is there load balancing support in ldm?
19:17ltsp has quit IRC
19:17
<lns>
iMacGyver, i think? Isn't there load balancing support in ltsp as a whole?
19:36vagrantc has joined #ltsp
20:02jammcq has joined #ltsp
20:16warren has quit IRC
21:31warren has joined #ltsp
21:31
<warren>
Hey, can anybody give me non-root ssh access to an Edubuntu 7.10 box?
21:31
I only want to see the location of scripts installed by LTSP5
21:31
and how they interact with other tools
21:32
I haven't been successful in installing it in kvm
21:32
<vagrantc>
warren: you can just look at the packages themselves ...
21:34
warren: what sort of things are you trying to understand?
21:34
<warren>
vagrantc, first where exactly are the files installed
21:35
vagrantc, also how things interact
21:35
vagrantc, non-root ssh would really be helpful
21:35
vagrantc, and I don't really have a clue where to find packages
21:35
<vagrantc>
warren: i don't have any edubuntu boxen or really any sshable boxen ...
21:35
<warren>
I'll wait to see if someone else has one
21:38
<vagrantc>
warren: you can have a look at the debian package contents here: http://packages.debian.org/sid/i386/ltsp-client-core/filelist
21:38
<warren>
vagrantc, and ltsp-server?
21:38
<vagrantc>
s,ltsp-client-core,ltsp-server,
21:39
you'll also want to look at ltspfs, ltspfsd and ldm
21:39
that should be just about everything
21:40
it isn't a shell account, but you can at least see the layout
21:40
<warren>
yeah, this helps
21:40
thanks
21:40
<vagrantc>
and ubuntu 7.10 is pretty similar to what's in debian sid
21:40
<warren>
hmm
21:40
I have to change locations of a few things
21:40spectra has quit IRC
21:40
<warren>
/usr/lib/ltsp/ for example is problematic because we have two arch's that could sit side-by-side
21:40
/usr/share/ltsp should contain the arch-neutral scripts
21:40
<vagrantc>
agreed
21:41* vagrantc tried to get that changed years ago
21:41
<warren>
well I'm going to have to add ugly hacks to detect the location
21:42
if our changes will be suitable for upstream
21:42
<vagrantc>
almost all of /usr/lib/ltsp could go into /usr/share/ltsp, i think.
21:42
<warren>
for ltsp-client it appears all
21:43
<vagrantc>
actually, yes. every single script in there could easily be moved to /usr/share
21:43
<warren>
I'm under time pressure here at FUDCon to get it working, so I'm not going to add upstream suitable stuff yet
21:44
especially since I couldn't successfully install an Edubuntu
21:44
to verify it
21:44
<vagrantc>
well, if you have specific questions, i'd be happy to answer them. i know the overall layout pretty well.
21:45
<warren>
hmm
21:45
http://packages.debian.org/sid/i386/ltsp-server/filelist contains ldm and other stuff
21:46
<vagrantc>
warren: ldminfod is the server-side component that ldm uses to get information like available session types, supported languages, etc.
21:46
<warren>
ooh
21:46
and we use xinet.d instead of inet.d
21:46
inetd
21:47
<vagrantc>
sure
21:47
you can download the actual package at: http://packages.debian.org/sid/PACKAGE
21:48
warren: i could also probably tarball up a chroot and put it up for download
21:48
warren: if that would be helpful
21:49
<warren>
what I really need is a raw disk image
21:49
I can boot a raw disk image in qemu-kvm
21:50
<vagrantc>
i've got a virtualbox image ... don't know if it's bootable from qemu
21:55
nope, qemu can't boot a virtualbox disk
21:56
hmm... guess i could try with a newer version of qemu
21:58
no luck
22:02
<warren>
qemu has a tool to convert disk image formats
22:02
you could see which format virtualbox uses
22:02
<vagrantc>
qemu-img info never seems to give correct information on virtualbox dynamic disks
22:04
it things it's a raw image, and usually reports the virtual size only slightly higher than the disk size
22:04
so the way virtualbox does dynamicly growing disk images confuses it
22:05
<warren>
apparently
22:05
Eric Harrison has an Edubuntu install, I'll see it tomorrow.
22:06
<vagrantc>
i could make a new install using qemu
22:06
i think i could scrounge up enough space
22:07
<warren>
that would be very helpful
22:08
<vagrantc>
i'll have a harder time verifying that the client it generates is bootable for sure
22:08
<warren>
oh
22:09
have you managed to get qemu bridging working?
22:09
<vagrantc>
partially
22:09
i can get it working so that qemu can talk to the host, and the host can talk to a qemu instance, but can't get two qemu instances to talk to one another
22:12
and then someone backported virtualbox-ose to debian etch, and it was ridiculously easy to set up a virtual network, so i've mostly done my ltsp development using virtualbox
22:12
<warren>
oh
22:13
ok don't worry about it
22:13
I'll see Edubuntu soon
22:14
<vagrantc>
well, it wouldn't be a bad thing to have a downloadable image
22:16
<warren>
yeah...
22:18chup has joined #ltsp
22:18chupa has quit IRC
22:20npman has joined #ltsp
22:38zodman has quit IRC
22:56zodman has joined #ltsp
22:59
<vagrantc>
warren: would a qcow format disk image work for you?
22:59
<warren>
vagrantc, yes
23:00
<vagrantc>
warren: i'll make one up and see how it goes
23:00
<warren>
thanks
23:01
<vagrantc>
hm.
23:01
<warren>
gotta sleep now
23:01
<vagrantc>
on second thought, maybe i should just make a raw image, so that i could test in virtualbox
23:01
<warren>
early morning again
23:01
at conference
23:01
<vagrantc>
night
23:02
<warren>
vagrantc, with raw image, zero it out to begin with so it compresses better
23:04
<vagrantc>
warren: does "qemu-img create -f raw" do that?
23:05
warren: it almost seems like it created a sparse image
23:07npman has left #ltsp
23:07npman has joined #ltsp