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


Channel log from 9 October 2009   (all times are UTC)

00:02Ahmuck has quit IRC
00:34vagrantc has quit IRC
00:55avishek has joined #ltsp
00:58avishek has quit IRC
01:00avishek has joined #ltsp
01:05avishek has quit IRC
01:06vagrantc has joined #ltsp
01:57Egyptian[Home] has joined #ltsp
01:58* vagrantc cackles maniacally while porting LTSP to Debian GNU/kFreeBSD
01:59
<vagrantc>
finally managed to boot one of these things
02:24nubae|work has joined #ltsp
02:25alkisg has joined #ltsp
02:26vagrantc has quit IRC
02:27
<alkisg>
Good morning
02:31chupacabra has joined #ltsp
03:04zavag has joined #ltsp
03:06ogra has joined #ltsp
03:23ogra has quit IRC
03:25ogra has joined #ltsp
03:25ogra has quit IRC
03:25ogra has joined #ltsp
03:26ogra has joined #ltsp
03:36artista-frustrad has quit IRC
03:37artista-frustrad has joined #ltsp
04:10F-GT has quit IRC
04:11garymc has joined #ltsp
04:21F-GT has joined #ltsp
04:36zavag has quit IRC
04:42Selveste1 has joined #ltsp
04:49alkisg has quit IRC
04:57mikkel_ has joined #ltsp
05:22Alocado has joined #ltsp
05:23
<Alocado>
hello... i'm trying to use ltsp for a kiosk system
05:24
my client is booting (with ubuntu progress bar) but then there's only a cursor in the top left corner... nothing else
05:24
on console1 there is information about ip's, boot path ... nothing else
05:25
any idea?
06:01ogra has quit IRC
06:12leio_ has joined #ltsp
06:26pmatulis has joined #ltsp
06:26leio has quit IRC
07:09bieb has joined #ltsp
07:16
<_UsUrPeR_>
mornin all! :D
07:16
IT IS GREAT TO BE ALIVE
07:17alkisg has joined #ltsp
07:24ogra has joined #ltsp
07:30gentgeen__ has joined #ltsp
07:34garymc has quit IRC
07:36gentgeen__ has quit IRC
07:36gentgeen__ has joined #ltsp
07:37artista-frustrad has quit IRC
07:38artista-frustrad has joined #ltsp
07:39alkisg has quit IRC
07:41nubae|work has quit IRC
07:41garymc has joined #ltsp
07:49Alocado has quit IRC
08:19ogra has quit IRC
08:34gentgeen__ has quit IRC
08:35garymc has quit IRC
08:45alkisg has joined #ltsp
09:03ogra has joined #ltsp
09:18gentgeen__ has joined #ltsp
09:24Kicer86 has joined #ltsp
09:31CAN-o-SPAM has joined #ltsp
09:40korcan has quit IRC
09:40korcan has joined #ltsp
09:41leOn has joined #ltsp
09:41
<leOn>
hello
09:43
can someone advise me regarding a xdmpc connection? ... from what i can tell, i have it all set up, but then, while using rdesktop to access via XDMCP, all i get is a black xnest window, which eventually closes
09:43
xdmcp, even
09:47
<sbalneav>
Which version of LTSP are you using?
09:47
<leOn>
5 I believe ..
09:49
but i'm still not using ltsp to access the gdm server
09:50
<sbalneav>
OK, well, how did you install LTSP? What's the OS on the server, etc. We need a little more info. LTSP5 doesn't USE xdmcp by default, so I'll need more info to help you at this point.
09:51alkisg has quit IRC
09:52
<leOn>
hmmm.. even if i define xdmcp in gdm.conf, on the ltsp server ?
09:53
the server is a debian lenny
09:53
and the server wasn't installed by me .. i'm picking up someone elses work
09:55
<sbalneav>
So, you're trying to use the thin client to contact a microsoft server? That's what rdesktop is for...
10:02
<leOn>
i'm sorry .. i meant xnest ...
10:03
basically i'm trying to connect through xdmcp, with xnest, from a regular linux client, to the ltsp server (which is working properly for the thin clients)
10:03cliebow has joined #ltsp
10:04
<leOn>
is there anything in the usual ltsp server configuration that prevents xdmcp? (apart from the gdm.conf enabling stuff)
10:08
hmmm .. ltsp uses its own greeter ...
10:11
<sbalneav>
Yes, ldm
10:11
ltsp tunnels it's logins over ssh
10:11
and potentially, the entire session over ssh
10:12
<leOn>
ok .. is it possible to have only the logins over ssh? .. i believe that the entire thing is using ssh right now
10:16
<sbalneav>
Yes
10:16
Set LDM_DIRECTX=True in lts.conf
10:16
The docs have lots of good info.
10:16
!docs
10:16
<ltspbot>
sbalneav: "docs" is For the most current documentation, see http://wiki.ltsp.org/twiki/bin/view/Ltsp/LtspDocumentationUpstream
10:17
<sbalneav>
brb, off to a doctors appt
10:17staffencasa has joined #ltsp
10:20
<cliebow>
BOATRIDE!!!!
10:20cliebow has quit IRC
10:25tstafford has quit IRC
10:27tstafford has joined #ltsp
10:38
<leOn>
heh .. i just forced LDM_DIRECTX=True and the thin client stoped working ..
10:40fotanus has joined #ltsp
10:41
<leOn>
using LDM_DIRECTX=True, how does the client connect to the remote X server? .. using xdmcp ?
10:42
<ogra>
nope
10:42
it just uses X
10:42
a simple DISPLAY forward and the according xauth setup
10:43
speed and traffic wise the same as xdmcp though
10:43
<leOn>
one of the things i was noticing was that thin client connection was a bit slow .. probably due to encrypted tunnel ...
10:44tstafford has quit IRC
10:44
<leOn>
the thin clients are a bit low end (and old i think)
10:45
<ogra>
if you have directx set only the PW excange is through ssh
10:45cg_uira has joined #ltsp
10:45tstafford has joined #ltsp
10:45
<leOn>
besides setting LDM_DIRECTX=True on lts.conf, should i have any other concerns on the server?
10:45
<ogra>
and communication about local devices etc
10:46
but thats not havving any effect
10:48
<leOn>
what do you mean by "not having any effect" ?
10:49
<ogra>
the messages being sent over the tunnel are just a few byte
10:51
<leOn>
but in the docs i can read "If processing power is a concern to you (...)"
11:00johnny has joined #ltsp
11:01vagrantc has joined #ltsp
11:06
<sbalneav>
leOn: Correct, but that's for X. Very little goes over the tunnel for plumbing local dev stuff.
11:07alexqwesa has quit IRC
11:11alexqwesa has joined #ltsp
11:16
<leOn>
ok, so if i choose LDM_DIRECTX=True, X communitation is direct, but all other stuff (auth, devices, etc) goes through the ssh tunnel .. is that it?
11:18ogra has quit IRC
11:18
<sbalneav>
Device DATA access does not, nor does sound.
11:18
Neither do regardless.
11:18
but Auth, and the plumbing of device connections will continue to go over ssh.
11:20
<leOn>
ok .. so if i want to have sound, etc, i'll need to use the whole thing through the ssh tunel .. ?
11:23johnny has left #ltsp
11:24
<sbalneav>
No, sound *never* goes through the ssh tunnel.
11:24
Only X and auth goes through the ssh tunnel
11:24
and by specifying LDM_DIRECTX=True, then just the auth is going through the ssh tunneling.
11:25
<leOn>
gotcha ..
11:26
well .. somehow, using LDM_DIRECTX=True i'm not being able to connect .. *sigh*
11:27
<sbalneav>
At what point is it failing?
11:27gentgeen__ has quit IRC
11:28gentgeen__ has joined #ltsp
11:28gentgeen__ has quit IRC
11:29gentgeen__ has joined #ltsp
11:30zavag has joined #ltsp
11:34garymc has joined #ltsp
11:37artista-frustrad has quit IRC
11:38artista-frustrad has joined #ltsp
11:39zavag has quit IRC
11:41alkisg has joined #ltsp
11:43garymc has quit IRC
11:46
<leOn>
sbalneav: trying to track down the issue .. it presents me the ldm, and seems it's failing when connecting to the other X server
11:47
<vagrantc>
does it work if you disable LDM_DIRECTX ?
11:47
do you have a window manager installed?
11:48
what's it say in /home/$USER/.xsession-errors ?
11:48
those are just a few first guesses at what to look into next :)
11:49Ahmuck has joined #ltsp
11:51
<leOn>
vagrantc: disabling LDM_DIRECTX it works just fine
11:52
<vagrantc>
is the server on the same network segment, or across a NATted firewall?
11:53
<sbalneav>
I'm wondering if he needs to ltsp-update-sshkeys && ltsp-update-image and reboot.
11:53shawnp0wers has quit IRC
11:53
<vagrantc>
if it works without LDM_DIRECTX, that part should be fine...
11:54
<leOn>
vagrantc: they're in different networks, but no nat .. just regular routing
11:54
<vagrantc>
i really should add some mechanism to have ltsp-update-sshkeys take effect without having to run ltsp-update-image one of these days...
11:55
leOn: no other firewalling that might get in the way? on the server or router?
11:55
<leOn>
not that i know of
11:56
<vagrantc>
having to rebuild the image after running ltsp-update-sshkeys has been one of the things that's prevented me from switching to NBD for debian...
11:56
<leOn>
let me just check with the noc guys .. but i'm pretty sure there's no restriction
11:56
<vagrantc>
better to check than spend hours of troubleshooting :)
11:58
<leOn>
yep =)
11:58ogra has joined #ltsp
11:59Lns has joined #ltsp
12:04ogra has quit IRC
12:05ogra has joined #ltsp
12:09
<vagrantc>
sbalneav: you know your way around ifdef type C hacking? :)
12:10Lns has joined #ltsp
12:10
<vagrantc>
i'm just shy of being able to upload ltsp to debian with crude kfreebsd support.
12:11
need to patch getltscfg to have different code for processing ip and mac address.
12:11
and then it's upload-worthy.
12:12
or anybody, for that matter :)
12:12
also need a patch for ldm WEXITD stuff ... but i want to start with the basics first :)
12:12
<alkisg>
So you need an ifdef to see if it runs on kfreebsd?
12:13
<vagrantc>
alkisg: well, more like an ifdef that it isn't *freebsd. that'll get me an ugly patch where i just remove support for it.
12:14
alternately, i could conditionally apply the patch only on kfreebsd ... i think i know how to do that in debian/rules ... but really, i need to figure out how to support it properly, rather than just remove support for it.
12:14
it's the GetAddrs function in client/getltscfg/getltscfg.c
12:16
<alkisg>
How would that be in *freebsd?
12:16
<vagrantc>
don't know :)
12:17leOn_ has joined #ltsp
12:17
<vagrantc>
but if i disable it entirely, it works, for the most part, just doesn't have support for configuring thin clients by mac address or ip
12:17
<alkisg>
Ah... you get compilation errors?
12:17
<vagrantc>
a failed build log: https://buildd.debian.org/fetch.cgi?pkg=ltsp&arch=kfreebsd-i386&ver=5.1.90-1&stamp=1254744786&file=log&as=raw
12:17
most of the way down...
12:17
<leOn_>
omfg .. apparently there was lost fw rule somehere denying X11 connections ... ARGH!
12:17
all is fine and dandy now
12:18
<vagrantc>
leOn: nice!
12:18
alkisg: simply stripping GetAddrs out entirely gets it to build, and it even works and stuff.
12:18
<leOn_>
heh .. i see LOTS of improvement in connection speed from the thin clients if not using the ssh tunnel for everything
12:19
it's only a geode cpu MHz : 365.246
12:19
with 128M of ram
12:19
<vagrantc>
yeah, that'll take a big hit.
12:22rjune_wrk has quit IRC
12:22rjune_wrk has joined #ltsp
12:27leOn has quit IRC
12:32LaserJock has joined #ltsp
12:44tstafford has quit IRC
12:46tstafford has joined #ltsp
12:47
<alkisg>
vagrantc: (sorry too many phones): A quick way to do that is:
12:47
void GetAddrs()
12:47
{
12:47
#ifdef SIOCGIFHWADDR
12:47
...
12:47
out:
12:47
free(ifc.ifc_buf);
12:47
#endif
12:47
}
12:48
<vagrantc>
alkisg: ah, i special cased it base on the OS to not even have a GetAddrs function ...
12:48
but that might be simpler.
12:49
basically making GetAddrs a no-op.
12:49
<sbalneav>
Wouldn't #ifdef __GNU__ be better?
12:49
<vagrantc>
sbalneav: it's Debian GNU/kFreebsd, in this case, so no.
12:49
<alkisg>
My web dev experience says that it's better to check for features than for os/versions :)
12:49
<sbalneav>
ah
12:50
<vagrantc>
but really, i've got to figure out a patch that actually works, rather than disabling it :)
12:50
<alkisg>
You'd need someone that would read about sockets in freebsd... :D
12:51
...another quick hack would be to call `ip` or `ifconfig` to see the interface :P
12:51
<vagrantc>
looking into the ifconfig code is probably the way to get it "right" :)
12:52
i've found executing binaries from C and reading the output to be an exercise in frustration...
12:55
probably not sockets, so much as looking at interfaces and such ... so freebsd-tools's ifconfig would be the place to look
12:55* alkisg would rather see ldm being replaced with xdmcp over ssh... /me also ducks to avoid flying bricks :)
12:56
<vagrantc>
alkisg: you'd have to teach either xdmcp to use tcp, or ssh to do udp. i don't know which is more an exercise in cruelty.
12:56* leOn_ tosses a brick
12:56
<alkisg>
vagrantc: nah, I'd ssh into the machine first, and then use xdmcp locally... but there are other problems with dbus etc, that would require another ssh connection, and it gets compilated
12:57
<leOn_>
vagrantc: is there any easy way to enable the thin client X server to allow xdmcp connections?
12:57
<vagrantc>
alkisg: that seems like the worst of both worlds.
12:57
!xdmcp
12:57
<alkisg>
Well, it saves the ltsp devs from maintaining ldm
12:57
<ltspbot>
vagrantc: Error: "xdmcp" is not a valid command.
12:58
<leOn_>
i'm hating having to get up all the time to test stuff on the thin client
12:58
<vagrantc>
alkisg: almost all the ldm work as of late has been on adding features you just couldn't easily do with xdmcp.
12:58
<leOn_>
only if i could simulate a console with xnest =)
12:58
<alkisg>
leOn_: sshd on the chroot?
12:59
vagrantc: sure, I know... yet many of those features are standard *dm features, and ldm doesn't even have all of them
12:59
<leOn_>
alkisg: that won't work ... i have 1 ltsp server, 1 thin client where i'm testing stuff and then i have my workstation
12:59
<alkisg>
E.g. no languages installed on the chroot, no face browser etc etc
12:59
<leOn_>
my workstation is not near either of the other two ...
13:00
so if i could simulate the thin client console over here ...
13:00
<alkisg>
leOn_: if you ssh to the server, and from there ssh to the client?
13:00
<vagrantc>
alkisg: what do you mean "no languages installed on the chroot" ?
13:00
<leOn_>
i don't want ssh .. i want the graphical interface
13:00
<alkisg>
leOn_: you could also install italc :)
13:01
vagrantc: the "Preferences" button for example isn't translated
13:01
<leOn_>
italc?... wass that?
13:01
<alkisg>
!italc
13:01
<ltspbot>
alkisg: Error: "italc" is not a valid command.
13:01
<alkisg>
Bah damn bot
13:01
You don't know anything :)
13:01
<sbalneav>
So teach it :)
13:01
<vagrantc>
alkisg: it is when i run it in spanish.
13:01
<alkisg>
leOn_: it's a vnc clone, integrates well with ltsp - at least on ubuntu
13:02
<leOn_>
seems cute
13:02
<alkisg>
!learn italc is see http://italc.sourceforge.net/ or https://help.ubuntu.com/community/UbuntuLTSP/iTalc
13:02
<ltspbot>
alkisg: Invalid arguments for learn.
13:02
<alkisg>
Never mind :)
13:03
<vagrantc>
alkisg: learn as
13:03
<leOn_>
maybe this one too .. http://italc.sourceforge.net/wiki/index.php?title=ITALC_in_a_ThinClient_environment
13:03
<vagrantc>
learn foo as
13:03
<alkisg>
vagrantc: in the default installation it isn't translated; one has to install the language packs into the chroot
13:03
<vagrantc>
ltspbot: learn italc as see http://italc.sourceforge.net/ or https://help.ubuntu.com/community/UbuntuLTSP/iTalc
13:03
<ltspbot>
vagrantc: The operation succeeded.
13:03
<vagrantc>
alkisg: that's an ubuntu problem. works automatically on debian.
13:03
<alkisg>
Yeah leOn_ gave a better link :)
13:03
vagrantc: you install *all* the language packs?!!! or something else?
13:04
<vagrantc>
ltspbot: learn italc as http://italc.sourceforge.net/wiki/index.php?title=ITALC_in_a_ThinClient_environment
13:04
<ltspbot>
vagrantc: The operation succeeded.
13:04
<alkisg>
!italc
13:04
<ltspbot>
alkisg: "italc" is (#1) see http://italc.sourceforge.net/ or https://help.ubuntu.com/community/UbuntuLTSP/iTalc, or (#2) http://italc.sourceforge.net/wiki/index.php?title=ITALC_in_a_ThinClient_environment
13:04
<alkisg>
!forget italc #1
13:04
<ltspbot>
alkisg: Error: There is no such factoid.
13:04
<alkisg>
!forget italc
13:04
<ltspbot>
alkisg: Error: 2 factoids have that key. Please specify which one to remove, or use * to designate all of them.
13:04
<vagrantc>
alkisg: there are no language packs in debian, it dynamically builds enabled languages at install time.
13:04
<alkisg>
And why *$(& did Ubuntu change that? :(
13:05
!forget italc 1
13:05
<ltspbot>
alkisg: The operation succeeded.
13:05
<alkisg>
!italc
13:05
<ltspbot>
alkisg: "italc" is http://italc.sourceforge.net/wiki/index.php?title=ITALC_in_a_ThinClient_environment
13:05
<alkisg>
At last :)
13:05
!v
13:05
<ltspbot>
alkisg: Error: "v" is not a valid command.
13:05
<leOn_>
thanks for all the good pointer and advices
13:05
<vagrantc>
alkisg: by default on debian, all languages enabled on the server are enabled in the chroot.
13:05jammcq has joined #ltsp
13:05
<leOn_>
time to head home
13:05
=)
13:05
<alkisg>
!learn v as vagrantc!!!!!!!!!!!!!!!!!!1!!!!!
13:05
<ltspbot>
alkisg: The operation succeeded.
13:05
<jammcq>
hello firends
13:05
<leOn_>
have a great weekend
13:05leOn_ has quit IRC
13:05
<jammcq>
err.. s/firends/friends/
13:06* vagrantc kind of likes firends
13:06
<alkisg>
vagrantc: ok, really nice. But wouldn't _not_ maintaining a dm be simpler for you devs?
13:07
<vagrantc>
jammcq: so, the port of LTSP to Debian GNU/kFreeBSD is well under way, frakenstein though it may be :)
13:07
alkisg: only if it does what we need, and adapts when we need it.
13:07
<jammcq>
wow
13:08
<alkisg>
Such as? E.g. load balancing isn't really a dm job...
13:08
<jammcq>
does that mean we're gonna change the name to FTSP ?
13:08
<vagrantc>
alkisg: getting GDM to do what we need would require a huge number of patches, and previous attempts have ended in utter defeat.
13:08
alkisg: even simply getting in support over SSH.
13:09
<alkisg>
Why is ssh a dm job? It could connect to the server before the dm launches, couldn't it?
13:09
<vagrantc>
alkisg: and all the rc.d hooks and such ... support for localapps, local sound, etc.
13:09staffencasa has quit IRC
13:09
<vagrantc>
alkisg: how to you handle the username/password of the ssh tunnel? require the user to type it in twice?
13:10
alkisg: there's no hooks mechanisms for the other display managers.
13:10
<alkisg>
I haven't thought this through, but I wonder if it would be simpler for you all
13:10
vagrantc: doesn't pam provide for such hooks?
13:10
<vagrantc>
alkisg: so you either have to get support upstreamed, patch in something, or you have *no* flexibility.
13:10
<sbalneav>
Exactly. That's why we finally broke down and wrote our own.
13:11
<alkisg>
E.g. install pamltsp, and voila, it works with any dm
13:11
(yeah I know it's science fantasy :P)
13:11
<vagrantc>
alkisg: it would be a nice idea ... look forward to seeing it work :)
13:13
<alkisg>
OK... /me will start hacking a pam-sshfs for standalone ubuntu classrooms, and if that works, I'll surely try to propose something like this for ltsp too. If only the day had 88 hours... :-/
13:15
<vagrantc>
jammcq: the proper name for it, is, of course, dgkfbsdtsp.
13:17
<jammcq>
oh, nice
13:17
is that russian ?
13:17
<sbalneav>
alkisg: What's your email, a couple of us tried this a while back, and I have a libpam-ssh module here that I and Moquist worked on.
13:17
<vagrantc>
jammcq: Debian GNU/kFreeBSD Terminal Server Project :)
13:17
<alkisg>
gmail alkisg - thanks man
13:18
sbalneav: why did you drop that? not enough hooks in pam?
13:19
<sbalneav>
No, couldn't handle password expiry
13:19
1 sec, I'll mail it.
13:22
sent.
13:24
<alkisg>
Thanks! OK don't let me take up your time with silly questions, I'll dive into the code first and ask questions later.
13:25* alkisg first has to setup a TURN server for remote supporting teachers behind nat, though... argh :(
13:25
<sbalneav>
vagrantc: dgkfbsdtsp?
13:25
Did it hurt when you smacked your face into the keyboard? :)
13:26
Here, I'll try:
13:26
<vagrantc>
sbalneav: more like a peculiar euphoric sensation
13:26
<sbalneav>
Meh, help popped up
13:26
:)
13:26
Must not be smacking hard enough
13:27
So, I have a funny story to relate.
13:27
That a buddy of mine who was an electronic tech, who repaied med. equipment at the St. Boniface hospital told me.
13:28
So, he's down in the shop one day, working on something, and one of his co-workers was working on the machine that they use for electro-shock therapy.
13:29
That's the thing where they induce seizures by zapping your noggin with high voltage.
13:29
Anyway, the guy fixes it, and asks my buddy Doug : "So, how do I test it?"
13:30
This other guy was pretty new on the job, but Doug says (figuring to make a joke) "Well, just charge it up, stick it on your temples, and see what happens!"
13:31
Assuming that no one in his right mind would consider doing it.
13:31
So, he hear's the machine charging up (that "flash camera" incrasing charge whine), looks over, and sees the guy moving the paddles to his head.
13:32
Apparently he screamed "What ARE YOU NUTS" loud enough to make the guy pause.
13:32
Explained to him he should go get the highvoltage probe, and do a proper measurement. :)
13:33
The moral of the story: Never assume something's so obviously silly that someone won't take you seriously.
13:34
That concludes #ltsp story time.
13:34
NOW YOU KIDS GET TO SLEEP AND NO MORE JUMPING ON THE BED!!!
13:34* alkisg imagines sbalneav telling stories to his kids round the fireplace... "OK dad I'm heading off to sleep!"
13:35
<sbalneav>
You're allowed a glass of milk and ONE cookie.
13:36tstafford has quit IRC
13:37tstafford has joined #ltsp
13:37tstafford has quit IRC
13:39tstafford has joined #ltsp
13:41
<Lns>
hahahaha
13:46
<rjune_wrk>
jammcq got two... I want two
13:48Kicer86 has quit IRC
13:49Ahmuck has quit IRC
13:50* Lns pours his glass of milk on rjune_wrk
13:54
<rjune_wrk>
DAAAAAAAAAD!!!!
13:54
<Lns>
bwwahahaha
13:55* vagrantc fires up the tesla coils in the basement
14:05* Lns runs to bed
14:09tstafford has quit IRC
14:09ogra has quit IRC
14:09sakhi__ has quit IRC
14:09comfrey has quit IRC
14:09|Paradox| has quit IRC
14:09artista-frustrad has quit IRC
14:09Egyptian[Home] has quit IRC
14:09dkostousov has quit IRC
14:09ltsppbot has quit IRC
14:09Appiah has quit IRC
14:09sep has quit IRC
14:09shogunx has quit IRC
14:09bieb has quit IRC
14:09alexqwesa has quit IRC
14:09yanu has quit IRC
14:09elias_a has quit IRC
14:09spectra has quit IRC
14:09Selveste1 has quit IRC
14:09vlt has quit IRC
14:09Topslakr has quit IRC
14:09rm-rf has quit IRC
14:09panthera has quit IRC
14:09dberkholz has quit IRC
14:09jammcq has quit IRC
14:09mikkel_ has quit IRC
14:09tarbo has quit IRC
14:09kusznir has quit IRC
14:09pmatulis has quit IRC
14:09F-GT has quit IRC
14:09cyberorg has quit IRC
14:09knipwim has quit IRC
14:09Ryan52 has quit IRC
14:09ajohnson has quit IRC
14:09ltsplogbot has quit IRC
14:09sutula has quit IRC
14:09stgraber has quit IRC
14:09NeonLicht has quit IRC
14:09Sarten-X has quit IRC
14:09zamba has quit IRC
14:09lejo has quit IRC
14:09Lns has quit IRC
14:09alkisg has quit IRC
14:09LaserJock has quit IRC
14:09strattog has quit IRC
14:09vagrantc has quit IRC
14:09cg_uira has quit IRC
14:09korcan has quit IRC
14:09CAN-o-SPAM has quit IRC
14:09leio_ has quit IRC
14:09loather-work has quit IRC
14:09japerry has quit IRC
14:09wwx has quit IRC
14:09_UsUrPeR_ has quit IRC
14:09benGREEN has quit IRC
14:09Patina has quit IRC
14:15ltspbot has joined #ltsp
14:16tstafford has quit IRC
14:18johnny has joined #ltsp
14:18tstafford has joined #ltsp
14:21rjune_wrk has joined #ltsp
14:22tstafford has quit IRC
14:23tstafford has joined #ltsp
14:29pmatulis has quit IRC
14:29pmatulis has joined #ltsp
14:36tstafford has quit IRC
14:39tstafford has joined #ltsp
14:47LaserJock has quit IRC
14:52shawnp0wers has joined #ltsp
14:53bieb has left #ltsp
14:57tstafford has quit IRC
14:59tstafford has joined #ltsp
15:01
<Lns>
I'm trying to figure out how to allow a non-root user to kill a client's automatic shutdown cron job, which was set by root. Is there any way to do this cleanly?
15:02
(without using gksudo or something)
15:02* alkisg wonders why shutdown was put as a cron job in the first place :)
15:02
<Lns>
alkisg: automatic thin client shutdown to save energy
15:02* jammcq can't even think of a dirty way to do it
15:03
<alkisg>
Lns, is that per client, or a "global" setting?
15:03
<Lns>
I've got a nice shell script going with zenity to prompt the user...i just need it to kill the cronjob if exit = 1
15:03
alkisg: it's on all clients, set in the chroot
15:03
<alkisg>
Wouldn't that be better done on the server cron?
15:04
<Lns>
alkisg: the server would need access to the clients through ssh or something, which they don't currently have
15:04
<alkisg>
Lns, well you could put nc to listen on a specific port for a shutdown command or something
15:05
<Lns>
well, i think tcm is going to have this functionality soon anyway, i just need something in the interim
15:05
<johnny>
or just kill the auto cron job
15:05
disable it
15:05
and then manually execute the stuff yourself..
15:05
<Lns>
users have no way of disabling the cron job if they're still working
15:05
<jammcq>
cron calls a script to do the shutdown?
15:05
<Lns>
jammcq: yes
15:06
<alkisg>
Lns, can the user run localapps?
15:06
<Lns>
nope, 8.04
15:06pmatulis has quit IRC
15:06
<jammcq>
have your zenity script drop a file in /tmp, called something like 'no_shutdown'
15:06
and have your cron shutdown script look for that file. if not found, then proceed with the shutdown
15:06
<Lns>
oooo
15:06
<johnny>
/tmp/username-noshutdown
15:06
<alkisg>
Well, then he'd have to have a way to make the clients execute commands. If he had such a way, then the cron job wouldn't be needed :)
15:06
<_UsUrPeR_>
oh nice jamm
15:06
<Lns>
very nice jammcq, thanks!
15:06
<jammcq>
no prob
15:07
<tstafford>
compiz as a local app is awesome
15:07
<alkisg>
Doesn't the script run on the client?
15:07
<tstafford>
i just felt like sharing
15:07
<alkisg>
Lns, how would it check on the server /tmp?
15:07
<Lns>
alkisg: yeah
15:07
<jammcq>
where is the zenity script running?
15:07
<Lns>
alkisg: it would be in the client /tmp
15:07
no this is all done in the chroot
15:07
<alkisg>
But the user can't access the local filesystem
15:07
<Lns>
oh. yeah.
15:07
<alkisg>
Didn't you say he can't run localapps?
15:07
<jammcq>
does the cron job run the script. the script pops up a window asking if it's Ok to power-down?
15:08
<Lns>
jammcq: yes
15:08
<jammcq>
I'm guessing if it gets no response in a certain amount of time, it goes ahead and shuts down
15:08
<Lns>
correct
15:08
<jammcq>
assuming the user is gone
15:08
cool
15:09
<Lns>
maybe just set an env var?
15:09
<_UsUrPeR_>
ok, I've "got one". I am trying to allow a user to change his password with kdepasswd. I need to add that program to every LTSP user's desktop upon user creation. We are using ldap for authentication, and skel to create users in an nfs mounted home directory.
15:09
<johnny>
Lns, imo you should just disable the automatic cron..
15:09
<_UsUrPeR_>
how do I change the default programs added to a user's directory upon creation?
15:09
<Lns>
johnny: we need it for power savings.
15:10
<johnny>
Lns, uhmm.. how about just shut em all down :)
15:10
<Lns>
johnny: *sigh* you tell that to the lab techs when they have a bazillion other things to do :)
15:10
<alkisg>
Lns, maybe you could set an xprop as the user, and have the cron script check it out.
15:10
<johnny>
Lns, tell them to pay you some more money
15:10
and upgrade to 9.04 :0
15:10
<vagrantc>
Lns: you can display a graphical prompt by displaying on the X server?
15:10* Lns ignores johnny's suggestions ;)
15:10
<johnny>
lol
15:10
_UsUrPeR_, you can put it in skel too..
15:11
<vagrantc>
Lns: you could have the cron job ask the user...
15:11
<johnny>
~/.local/share/applications or sometin
15:11
_UsUrPeR_, read the menu spec
15:11
<_UsUrPeR_>
johnny: rgr. I'll take a closer look at skel
15:11
<Lns>
vagrantc: ugh..well maybe i can't. can you not use a zenity script in the chroot to display on the client's x session?
15:11
<vagrantc>
Lns: you could either connect to the X server directly, or run a zenity command through the ssh tunnel.
15:12* Lns is still a scripting n00b
15:12
<vagrantc>
Lns: the latter might be a little better, as it'll mostly just run as the user.
15:12
<alkisg>
Lns, do you need a specific client to ignore shutdown, or all of them?
15:12
<johnny>
any one of them it sounds like..
15:12
<Lns>
alkisg: no, it's per-client.
15:13
i'm using the automatic shutdown that i wrote on the wiki. i want to present the user with a choice 5 minutes before the shutdown happens to either let it happen or cancel it.
15:14
<alkisg>
Yeah what vagrantc said sounds like the best option then
15:14
<Lns>
vagrantc: why would i need an ssh tunnel if the script is already in the chroot? i know that probably sounds ignorant of me
15:14
does it not have access to the local x server/session?
15:15
<vagrantc>
Lns: it does, but then it's running as root.
15:15
<Lns>
oh jeez. that's right. =p~
15:15
<vagrantc>
Lns: i'd minimize what you're running as root as much as possible.
15:15
but either way... probably mostly ok.
15:15
<Lns>
cool. thank you all for the input!
15:15
<alkisg>
I'd suppose it would be *better* to run it as root
15:15
<Lns>
this is all pretty temporary anyway
15:15
<alkisg>
...to enable the user to cancel it while still on ldm
15:15tstafford has quit IRC
15:15
<Lns>
nah...sitting at ldm isn't an issue
15:16
they can always just turn it back on
15:16
there have just been cases where people are working and it turns off ;)
15:16
oops
15:16tstafford has joined #ltsp
15:16
<alkisg>
Lns, then why don't you *always* call the logout command before shutting off?
15:16
Ah, hardy :(
15:17
No 60 secs timout...
15:17
<tstafford>
metacity --replace
15:24tstafford has quit IRC
15:26tstafford has joined #ltsp
15:34Lns has quit IRC
15:37artista-frustrad has quit IRC
15:38artista-frustrad has joined #ltsp
15:42shawnp0wers has quit IRC
15:45* vagrantc sighs
15:46tstafford has quit IRC
15:46jammcq has quit IRC
15:46
<vagrantc>
the next ltsp packages will actually require a backport :(
15:46
stupid libpopt0
15:46tstafford has joined #ltsp
15:50johnny has left #ltsp
15:53CAN-o-SPAM has quit IRC
16:07tstafford has quit IRC
16:16Beer30 has joined #ltsp
16:20
<Beer30>
Local Device / FUSE question: Why doesn't an icon show up on my desktop? I am using Gentoo / Gnome. USB stick is identified and shows up in mount command on server. I can access the directory on the client via gnome-terminal. What am I missing?
16:24sene has joined #ltsp
16:27
<Beer30>
icon for the USB Stick DOES show up on server, however.
16:29
(never mind last statement; usb stick was plugged directly into server, not via fuse.)
16:31fotanus has left #ltsp
16:35* alkisg loves nc!!! An admin "A" wants to help a teacher "T", but both of them are behind NAT. A server "S" with a public ip is available to help them. Easy solution with nc: Server S does: nc -l -p 1234 -c 'nc -l -p 4321' / Client A does: nc server 1234 -c 'nc localhost 5900' / Client B then connects to the server port 4321, and sees the vnc that A offers :) Die teamviewer, you've just been defeated! :)
16:37
<Beer30>
Humm.... rebooted client, plugged in the USB stick before I logged in, logged into client, opened "Computer", icon now shows up, but when I doubled clicked the icon, it said "Cannot mount volume". Then after a second or so, a popup said "Opening USB Drive".... then it sits there for like a minute then this error pops up: "Unable to mount location" "DBus error org.freedesktop.org.DBus.Error.NoReply: Did not receive a reply" blah blah blah.
16:39
That gives me something to Google on, but if anyone has any suggestions, please let me know :).
16:45sene has quit IRC
16:46alkisg has quit IRC
17:08pmatulis has joined #ltsp
17:10Beer30 has quit IRC
17:13otavio has quit IRC
17:20Egyptian[Home] has quit IRC
17:22Egyptian[Home] has joined #ltsp
17:25BugsBunnyBR has joined #ltsp
17:27BugsBunnyBR has quit IRC
17:28BugsBunnyBR has joined #ltsp
17:30BugsBunnyBR has joined #ltsp
17:31
<kusznir>
Hi all: Got another question for you: I noticed CentOS is not listed in the ltsp5 supported updates anywhere. Are there any known methods of at least doing a login to a CentOS 5 server other than xdmcp?
17:31BugsBunnyBR has quit IRC
17:31
<kusznir>
(i.e., something with encrypted logins and/or encrypted keyboard traffic at a minimum?)
17:32
We have several software programs that only work on CentOS/RHEL, and I'd like to go ltsp+thin clients for our next lab refresh.
17:32BugsBunnyBR has joined #ltsp
17:34cg_uira has quit IRC
17:37leOn has joined #ltsp
17:37
<leOn>
hello
17:37
<kusznir>
Another question: I just was looking through the wiki page on LtsConf, and it seems that it doesn't mention anything about SCREEN_ (except that it should mention something about it...)
17:38
My understanding is that that would be where I'd set up multiple login options. Is that correct?
17:38
<leOn>
the autologin process, using ldm, only requires LDM_USERNAME and LDM_PASSWORD in lts.conf, right ?
17:38
<kusznir>
(i.e., I want ctrl-alt-f1 to be one server, and ctrl-alt-f2 to be a different x server, I could do that there, right?
17:38
<leOn>
kusznir: from what i know, you can do that, yes
17:39
<kusznir>
What's the syntax?
17:39
<leOn>
no idea .. i just know you can do that =)
17:39
someone i work with already did that
17:40
<kusznir>
I used to do it back in ltsp 4.x days, but that was pre-ldm, and I'm not sure I even remember how to do different x servers..I can probably find an old config file that did rdp on one and X on another.
17:40
<leOn>
damn .. i have both LDM_USERNAME and LDM_PASSWORD defined in lts.conf, but autologin isn't working ... i think ...
17:41
yep .. not working .. there are no processes running in the server for that user
17:42
<kusznir>
Where is ldm configured?
17:43
<leOn>
lts.conf
17:43
<kusznir>
Umm..where is the daemon side of ldm....Where the theme that is displayed and such configured?
17:43BugsBunnyBR has quit IRC
17:44BugsBunnyBR has joined #ltsp
17:44
<leOn>
kusznir: http://www.ltsp.org/~sbalneav/LTSPManual.html#ldm
17:45
ah ah! .. LDM_AUTOLOGIN defaults to false
17:46
<kusznir>
le0n: thanks...that really sheds a lot of light on things...
17:50
<leOn>
kusznir: http://www.nabble.com/Changing-the-thin-client-login-theme-on-Hardy-td18352592.html
17:50
google is your friend also .. not mine only
17:51
kusznir: and sarcasm is not good policy when searching for help
17:54
hmm .. guys .. i need to lauch the ica server on the thinclient .. is it possible to do so BEFORE the login takes action? .. i.e. .. i want to be able to connect remotely to the thin client and access whatever is happeining at the moment, be it just the login window or the user session
17:54
<kusznir>
My understanding was that ldm was just like gdm: a daemon that listened for connections. I'm only now truly grasping what it is and how it works...Which is actually pretty cools.
17:54
<leOn>
s/lauch/launch/
17:56
<vagrantc>
kusznir: ldm is very different from gdm.
17:56
kusznir: it's essentially a GUI frotend for "ssh -X"
17:57
i mean, it's more complicated than that, but that's the basic jist
17:57
<kusznir>
vagrantic: I'm in the process of figuring that out :)
17:57
<leOn>
hi vagrantc
17:57
<kusznir>
How do you start a full gnome session via a forwarded ssh X session?
17:57
<leOn>
say .. would i be able to lauch the ica server from /usr/share/ltsp/screen.d/ldm ?
17:57
<kusznir>
(I haven't encountered that in the docs, although its not really important to what I'm trying to do, just trying to better understand how ldm works)
17:57
<vagrantc>
kusznir: ldm basically logs into the server something like this: ssh -x user@server /etc/X11/Xsession
17:58
kusznir: different distros put Xsession in different places.
17:58
<kusznir>
Ahh..Ok.
17:58
<vagrantc>
er, ssh -X user@server /etc/X11/Xsession
17:59
<kusznir>
One of the things I want to do is have it "log into" a CentOS box. I can have a ubuntu lts server, but my "application servers" need to be CentOS.
18:00
<vagrantc>
kusznir: best bet if you want a CentOS box is to build the LTSP5 environment on a supported distro, copy the public keys over so ltsp-update-sshkeys generates known_hosts entries for the CentOS server, optionally set up ldminfod on your CentOS server (especially if Xsession is in a different location), and set LDM_SERVER=ip.of.centos.server
18:02
<leOn>
vagrantc: say .. what's described in here http://italc.sourceforge.net/wiki/index.php?title=ITALC_in_a_ThinClient_environment .. what it truely does is launch ica on the server, right? .. not the thin client itself ..
18:03
i say this because they mention the login process and kdm ...
18:04
<vagrantc>
leOn: i've never used italc ...
18:04
<kusznir>
vagrantc: that's pretty much the conclusion I was coming to after reading through the documentation le0n sent me a link to.
18:10
vagrantc: So, I'm trying to get the first part done: getting a "host selection box" to show up and allow users to select between different hosts.
18:11
I've attempted to follow the instructions in http://www.ltsp.org/~sbalneav/LTSPManual.html#ldm section 22, by defining LDM_SERVER= <server1> <server2>, where in this case server1 is the ubuntu ltsp server, and server2 is the centos server. I've saved that lts.conf in my i386 tftp directory on the ubuntu server.
18:12
Unfortunately, I booted the thin client, and I don't see any host selection options/boxes.
18:13
(I'd like to, for now anyway, offer users a selection of hosts. Possibly even a different selection of hosts according to thin client.
18:14
<vagrantc>
i haven't messed with that feature for a while ... i don't remember how old that feature is, but should be present in all recent ubuntu releases.
19:00mikkel_ has quit IRC
19:03Selveste1 has quit IRC
20:08try2free has joined #ltsp
20:13try2free has left #ltsp
21:21johnny has joined #ltsp
21:21johnny is now known as Guest31455
21:26LaserJock has joined #ltsp
21:38sene has joined #ltsp