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


Channel log from 28 May 2009   (all times are UTC)

00:26hanthana has joined #ltsp
00:31
<vagrantc>
is that the same patch alksig posted to the ltsp-developer list a few days ago
00:32knipwim_ has quit IRC
00:35
<Ryan52>
yep
00:36try2free has joined #ltsp
01:07ogra has joined #ltsp
01:10Shane_ has joined #ltsp
01:20Shane_ has left #ltsp
01:22shogunx has quit IRC
01:22shogunx has joined #ltsp
01:23try2free has quit IRC
01:25try2free has joined #ltsp
01:28vagrantc has quit IRC
01:28try2free has left #ltsp
01:29try2free has joined #ltsp
01:30
<try2free>
why my welcome login screen very small, i can't see? how to fix?
01:37ogra has quit IRC
02:01ogra has joined #ltsp
02:07alkisg has joined #ltsp
02:10alkisg has quit IRC
02:15try2free has left #ltsp
02:34nubae1 is now known as Nubae
02:43alkisg has joined #ltsp
02:56Mathis has joined #ltsp
02:56
<Mathis>
hello
02:57
it seems kiwi-ltsp still is buggy
02:58johnny has left #ltsp
03:01knipwim has joined #ltsp
03:03cyberorg has quit IRC
03:19
<Mathis>
somehow kiwi-ltsp-setup -c never touches the nbd server config files nor starts the nbd server
03:19
is that intended?
03:21
<Drakonen>
Mathis: join #kiwi-ltsp
03:23
<Mathis>
I'm already there
03:24
it seems something is wrong with the nbd package
03:25
the Yast software management shows me an nbd package file list, containing more than one file in /etc/nbd-server/
03:25
but somehow it doesnt install more than /etc/nbd-server/config.example
03:25
even when reinstalling it
03:26
<ogra>
on normal ltsp5 implementations the nbd server is handled by inetd ... not sure what kiwi does
03:26
<Mathis>
ogra: seems to be independantly of LTSP in general
03:27
<ogra>
it isnt in normal ltsp environments on distros that implement ltsp5 upstream, kiwi is quite different so i cant say how they handle it there
03:27
usually ltsp-update-image adds a configured nbdrootd line to inetd.conf
03:31
<alkisg>
ogra (hi - sorry for the direct question - need your wisdom :)) I'm creating a collection of shell scripts that would display a menu with some standard tasks for ltsp management: updating chroot etc. Is it weird if I use debconf for its user-interface? Because db_input won't be used to answer a configuration question, it'll be used to enable the user to select a task from the menu... :/
03:32
<ogra>
well, debconf uses a database, do you need stored values for the UI ? also dont forget debconf isnt available on non debian based systems, i'D go with plain whiptail
03:32
<alkisg>
I like it's localization infrastructure, I prefer not to do it with zenity....
03:32
whiptail? /me googles
03:33
<ogra>
looks like the debconf ui but isnt so closely bound to the debconf db infrastructure
03:34bobby_C has joined #ltsp
03:34
<alkisg>
thanks man :)
03:41pasmen has quit IRC
03:41pasmen has joined #ltsp
03:54mikkel has joined #ltsp
03:58
<Mathis>
when adding entries to the local-app variable in ltsp-config, do I also have to make sure the corresponding package is installed somewhere?
04:02ogra has quit IRC
04:04ogra has joined #ltsp
04:05ogra has joined #ltsp
04:08
<Mathis>
I'd like to install dvdrip and transcode locally to my LTSP clients
04:08
since the server is 64bit, I cannot take the packages from there directly
04:10
would adding "dvdrip transcode" to LTSP_LOCALAPPS be sufficient? (me has openSUSE 11.1 64bit)
04:15alkisg has quit IRC
04:19hanthana has quit IRC
04:19
<Mathis>
my question was not rhetoric.
04:49evilx has quit IRC
04:50evilx has joined #LTSP
05:24
<Appiah>
isnt ltsp_localapps supposed to be true/false
05:25
or by LTSP_LOCAL apps you you mean chrooting in the client image and adding transcode and dvdrip (name of packages) ?
05:27
<Mathis>
LTSP_LOCALAPPS is a string
05:28
"Add space separated list of packages to be installed ..."
05:28
does it mean I have to supply just the name, i.e. transcode dvdrip ?
05:29
or do I have to supply a more "complete" name like dvdrip-0.98.10.pm.0.i586.rpm ?
05:29
I have tried the last one, whereas kiwi-ltsp-setup -s runs fine
05:29
but then dvdrip is missing on the clients
05:29
<Appiah>
what version and what dist?
05:30
oh kiwi is suse
05:30
<Mathis>
openSUSE 11.1
05:30
64bit
05:30
<Appiah>
then I have no idea
05:30
<Mathis>
doesnt LTSP5 also support local apps?
05:30
I think, I read something about that
05:31
<Appiah>
it does
05:31
but I have no idea on how kiwi adds the applications ...
05:31
I've been chrooting in the image and just installing the applications
05:32
no LTSP_LOCALAPPS in a file to tell what is supposed to be in it
05:32
first time I heard of it
05:32
<Mathis>
I have already added the packman repository to config.xml (in /usr/share/kiwi/image/ltsp/suse-11.1)
05:33
<Appiah>
like I've said , got no kiwi experince what so ever
05:33
<Mathis>
the problem is: the host is a 64bit OS, while the clients are 32bit
05:33
I cannot simply chroot to it and install packages, it might then install 64bit packages in a 32bit environment
05:37
well, thanks for replying
05:45
interesting to see that with LTSP_LOCALAPPS="transcode" the kiwi-ltsp-setup -s runs fine (until now)
05:46
Appiah: do you happen to know if there is a switch so that the clients dont load a displaymanager (and with it X and a desktop) ?
05:48
<Appiah>
hmm LTSP without LDM? No sorry never heard of that kind of setup
05:48
but there should be a set of scripts that it runs at the startup
05:49
<Mathis>
since my clients are all disk-/monitor- and keyboard-less, I dont need any graphical console
05:49
<Appiah>
maybe you can could remove the one? :P
05:49
<Mathis>
?
05:50
<Appiah>
the script that will launch ldm..
05:50
<Mathis>
if it is a script at all...
05:51
<ogra>
Mathis, SCREEN_07=shell
05:51
in lts.conf
05:51
<Mathis>
thanks
05:51
<Appiah>
but wont LDM show up somewhere else then?
05:51
or is it completley disabled?
05:51
<ogra>
right
05:51
if the tty is taken by a shell ldm wont attempt to start
05:52
<Appiah>
ah ok
05:52
thought it would be looking for another tty to launch it on or something like that
05:52
<Mathis>
yippes, finally got transcode installed on the clients
06:01
nice... cannot mount.nfs
06:01
in my clients
06:08
<Appiah>
have an error?
06:09pmatulis has joined #ltsp
06:10
<Mathis>
mount.nfs not found
06:10
seems I have to additionally install the nfs-client too
06:13
hopefully I dont need the dvdrip package too
06:16Nubae has quit IRC
06:17nubae has joined #ltsp
06:19ogra has quit IRC
06:21
<Mathis>
okay, this also now works
06:33leio_ has joined #ltsp
06:35leio has quit IRC
06:37
<Mathis>
seems I need some ogmmerge package too (for transcode)
06:42
the usual pain... ogmtools (containing ogmmerge) is not accepted by kiwi-ltsp-setup
06:48
seems to have been only a missing repository (luckily)
06:53alkisg has joined #ltsp
07:11
<Mathis>
aaaaand the 3rd time setting up password-less ssh-login
07:14
I copied over the .ssh/id_rsa.pub to /srv/tftpboot/KIWI/authorized_keys and rebooted the client; still it wants a password?!?
07:17vvinet has joined #ltsp
07:28
<Drakonen>
Mathis: did you look in the message log?
07:28
do the keys have the correct permissions?
07:29
<Mathis>
Drakonen: have solved it; had to adjust the /srv/tftpboot/KIWI/config.default again
07:29
was probably overwritten by the script
07:29petre has joined #ltsp
07:40Lumiere_ has joined #ltsp
07:48
<Mathis>
does anyone of you know where I can remove the informations describing the clients? I want to remove one specific clients data
07:53Lumiere has quit IRC
08:02petre has quit IRC
08:04
<Mathis>
it seems to store the client IP address connected to the client MAC address on the server
08:04
but I am unable to find out where it is
08:05
it is definately not in /etc/dhcpd.conf
08:13
<Appiah>
that would be a dhcp lease
08:13
should be a dhcpd.lease file
08:13
you can edit your dhcpd.conf on how long leases should be
08:14
(you can edit dhcpd.lease in texteditor of your choice and just remove the lease)
08:15
<Mathis>
where should the dhcpd.lease sit?
08:15
<Appiah>
/var/lib/dhcp/ somewhere
08:16
I'm not very good on where suse stores it stuff
08:16
you could always updatedb; locate dhcpd.lease
08:16
or find
08:16
<Mathis>
found it
08:17
just removing should help, I guess
08:18
<Appiah>
if you remove the whole file you need to recreate it
08:18
<Mathis>
I guess, I will insert the MAC addresses directly into my /etc/dhcpd.conf
08:18
<Appiah>
and make it writeable
08:18knipwim has quit IRC
08:19knipwim has joined #ltsp
08:20
<Mathis>
thanks alot
08:23_UsUrPeR_ has joined #ltsp
08:32Gadi has joined #ltsp
08:44matttttt has joined #ltsp
08:45
<matttttt>
is there an accepted or preferred way of estimating ltsp server hardware specs needed for a specific # of clients/applications?
08:49
<sbalneav>
matttttt: check the docs
08:49
!docs
08:49
<ltspbot`>
sbalneav: "docs" is For the most current documentation, see http://wiki.ltsp.org/twiki/bin/view/Ltsp/LtspDocumentationUpstream
08:49yoshi has joined #ltsp
08:50yoshi is now known as Guest66090
08:51
<sbalneav>
alkisg: and Ryan52: it won't work in all circumstances
08:51
I've got a better solution, I'll get it into the tree.
08:52
the problem is, any errors on the ssh socket can produce output on the shell line at any time during the login
08:52
we're clearing the output right after login, but if some happens after, the socket won't close.
08:53
I've solved it here by creating a thread after login that just clears out any output on the ssh process, and runs in the background.
08:53
I'll get it into the tree today or tomorrow.
08:53Guest66090 is now known as yoshi
08:53yoshi is now known as Guest39113
08:54alkisg has quit IRC
08:57Guest39113 is now known as yoshi_k
09:00yoshi_k has left #ltsp
09:00yoshi has joined #ltsp
09:01yoshi is now known as Guest99210
09:02Guest99210 is now known as yoshi_
09:02yoshi_ is now known as yoshi_-
09:02yoshi_- is now known as yoshi-
09:03yoshi- is now known as yoshi_kirano
09:03yoshi_kirano is now known as yoshi__
09:04yoshi has joined #ltsp
09:04yoshi is now known as yoshi__
09:04
<sbalneav>
ltspbot`: google sbalneav
09:04
<ltspbot`>
sbalneav: Search took 0.18 seconds: “~ sbalneav /ltsp/ldm-glibc” branch in Launchpad: <https://code.launchpad.net/~sbalneav/ltsp/ldm-glibc>; “~ sbalneav /ltsp/ltsp-docs- sbalneav ” branch in Launchpad: <https://code.launchpad.net/~sbalneav/ltsp/ltsp-docs-sbalneav>; Linux Terminal Server Project Administrator's Reference: <http://www.ltsp.org/~sbalneav/LTSPManual.html>; Ubuntu (2 more messages)
09:16Egyptian[Home] has quit IRC
09:17Egyptian[Home] has joined #ltsp
09:21Lumiere_ is now known as Lumiere
09:29
<sbalneav>
ltspbot`: list
09:29
<ltspbot`>
sbalneav: Admin, Alias, Channel, ChannelLogger, Config, Factoids, Google, Internet, Misc, Owner, Seen, Status, and User
09:32
<Lumiere>
sbalneav: nice supybot :)
09:33
<sbalneav>
Lumiere: Someone in #edubuntu's trying to set one up, I'm just checking some things
09:34yoshi__ has quit IRC
09:34
<sbalneav>
There's only 2 things about bots that are useful, I think
09:34
seen and factoids
09:34
<ltsplogbot>
I don't know who oids is.
09:35ogra has joined #ltsp
09:35yoshi__ has joined #ltsp
09:50alkisg has joined #ltsp
09:50
<Lumiere>
sbalneav: I use one on another network for autoop
09:50
but that's about it
09:51* Gadi liked the translate that nubae's bot had
09:51
<sbalneav>
Where's nubae's bot?
09:52
<Gadi>
dunno where it went
09:52
used to be able to do:
09:52
@help
09:52
and get a response
09:52
must be slacking off
09:52
nubae: where's ur bot?
09:53johnny has joined #ltsp
09:53
<johnny>
neat.. for pulse
09:53
http://webupd8.blogspot.com/2009/05/earcandy-is-smart-pulseaudio-volume.html
09:56
<sbalneav>
Gadi: Hmm, there's a newer version of supybot available, and it comes with a babelfish plugin
09:56
<Gadi>
yeah, I think he was using supybot, come to think of it
09:56
also had a "scholar" feature
09:56
and some others
10:05
<sbalneav>
Wierd, they mention a babelfish plugin in the docs, and relnotes, but it's not actually in the source anywhere
10:06
<alkisg>
sbalneav, would you mind having a look at https://bugs.launchpad.net/ubuntu/+source/ldm/+bug/375278 whenever you have some free time? It's ssh-process-related...
10:07
(07:03:12 πμ) Ryan52: sbalneav: please steal that bug from me and apply the fix if you look at it.
10:07
<sbalneav>
alkisg: yeah, that patch doesn't fully fix it.
10:07
<alkisg>
Really? Can I help somehow?
10:08
<sbalneav>
I've fixed it here. We need to launch a thread that sits in the background and keeps the stdout of the ssh process clean.
10:09
My patch is sorta gross, so I'm going to clean it up a bit today, and I'll patch upstream.
10:09
<alkisg>
My main problem was before the stdout cleanup, because ldm_wait waited for the wrong process...
10:09
<sbalneav>
atm, I'm still knee-deep in sabayon, and don't want to stop on that or I'll lose the thread
10:09
<alkisg>
Thanks
10:09
<stgraber>
that's to solve the cases where your session gets stuck on the wallpaper on logout ?
10:09
<alkisg>
stgraber, yes
10:09
<stgraber>
or is that another ssh process related issue ?
10:09
good, looking forward to that :)
10:17staffencasa has joined #ltsp
10:23bobby_C has quit IRC
10:26
<johnny>
hmm.. i guess i need to figure out another way to run student-control-panel remotely
10:27
silly thing wants gksudo, but when run under ssh -X ... it doesn't complete
10:27
hmm.. i guess i can just modify the sudoers file.. i hope it understands
10:30cliebow has joined #ltsp
10:48
<moldy>
hi
10:48
johnny: ping :)
10:48
<johnny>
hello
10:49
<moldy>
johnny: student-control-panel looks interesting. but it does not show me the logged in clients. do i need to do anything special to see them? do i need to install anything on the clients?
10:49
<johnny>
no
10:49
it worked for me on intrepid just fine
10:49
<moldy>
hmm, weird
10:50
<johnny>
the vnc part didn't work.. but that is known, and should be removed in newer versions
10:51
<moldy>
johnny: where/how do you run the thing?
10:51
can it be run from a client?
10:54
<johnny>
i doubt it
10:54
oh.. probably
10:54
since you have to sudo it
10:54
<ogra>
sure it can
10:55
<moldy>
i did use sudo
10:55
<johnny>
then it should be fine
10:55
<moldy>
but the left part where it says "all users" is empty, even though several people are logged in
10:55
and no error message :-/
10:56
do the users need to be in a special group or something?
11:02
trying to dig through the code right now...
11:05
ugh, the code mixes tabs and spaces?
11:11
ps eaxww|grep "bash -c"|grep "LTSP_CLIENT"|grep PPID|grep -v grep
11:11ogra has quit IRC
11:12
<moldy>
it uses that command to find the logged-in clients, it seems. that grep command is failing at the PPID part
11:27
yep, that grep command is buggy :)
11:30
<Gadi>
take out the grep PPID
11:30
we no longer kill the PPID
11:32
<cliebow>
just as well
11:33
i hate giving away my last cigarette before we kill them
11:43
<laga>
cliebow: :)
11:43
<johnny>
ahh.. so that means student-control-panel doesn't actually work anymore Gadi :)
11:43
ogra needs to pay attention to that :)
11:45
moldy, so does removing the PPID fix it?
11:48* Gadi doesn't think student-control-panel is maintained
11:48
<Gadi>
:)
11:49
<johnny>
Gadi, ogra fixed it up enough
11:49
before the latest release
11:54Lns has joined #ltsp
12:01nubae has quit IRC
12:03nubae has joined #ltsp
12:11Remaille has joined #ltsp
12:32CAN-o-SPAM has joined #ltsp
12:45spectra has joined #ltsp
12:47spectra has quit IRC
12:48spectra has joined #ltsp
12:55artista_frustrad has quit IRC
12:57yoshi___ has joined #ltsp
12:59pmatulis has quit IRC
13:00pmatulis has joined #ltsp
13:14yoshi__ has quit IRC
13:17leio__ has joined #ltsp
13:21leio__ is now known as leio
13:27
<alkisg>
I'm trying to use whiptail to create a collection of scripts to make it easier for teachers to use ltsp. So when I use whiptail --menu, it creates a menu and writes the output to stderr. How can I get that into a shell variable?
13:27
I could use `whiptail --menu ... 2>/tmp/somefile` and then cat the file, but isn't there any other way to capture stderr without temp files?
13:30vagrantc has joined #ltsp
13:32leio_ has quit IRC
13:35michael2 has quit IRC
13:37
<alkisg>
Argh... I hate it when I can find my questions in google without finding the answers :( http://osdir.com/ml/user-groups.linux.dunedin.general/2006-09/msg00017.html
13:39michael2 has joined #ltsp
13:40
<Gadi>
alkisg: in my experience with whiptail, the answer is no
13:40
which begs the question: why are you using a console-based GUI?
13:41
<alkisg>
@#(*$&(@# :)
13:41
<Gadi>
s/GUI/interface/
13:41
<alkisg>
Well I want to make some scripts for the teachers to easily do some common ltsp tasks
13:41
update the chroot is an example
13:41
<Gadi>
zenity?
13:41
gdialog?
13:41
*dialog
13:41
<alkisg>
That would be fine, but I also want them to see the output of the commands
13:42
<Gadi>
you can do that
13:42
have it keep a log
13:42
<alkisg>
So how can I use zenity and have an open terminal (that doesn't pop-up) and be decent?
13:42
<Gadi>
and then they can display the log at the end
13:42
<alkisg>
Some commands may require input from the user, I don't want to mess with screen scraping
13:43
<Gadi>
you have to worry about that with whiptail, too
13:43
<alkisg>
With whiptail I'll just get what they select from the menu, and drop back to the terminal, and let them provide any additional info (if needed)
13:43
With zenity, I won't have a terminal to drop back to
13:44
<Gadi>
I see what you're after
13:45
so, for the menu and such in whiptail, write a function
13:45
myFunction() {
13:46
<alkisg>
...yeah I guess a python script would be required. Or would calling mktemp all the time be enough?
13:46
<Gadi>
TMP=$(mktemp)
13:46
$* 2>$TMP
13:46Treyh has joined #ltsp
13:46
<Gadi>
ANSWER=$(cat $TMP)
13:46
<alkisg>
OK Gadi I got the idea, thanks. Sucks, but usabel :)
13:46
<Gadi>
rm $TMP
13:46
}
13:47
<Treyh>
by default, if you have a usb printer hooked up to a ltsp client, when it boots, it won't have the printer correct?
13:47
<Gadi>
indeed
13:47
<alkisg>
OK. I got it to be plugin based, so when I finish it I'll upload it somewhere, maybe someone will be interested
13:48
Thanks!
13:48
<Treyh>
alkisg: what is that?
13:48
<alkisg>
A collection of scripts for teachers, like "update chroot" "create an example lts.conf" "create an example dhcpd.conf" etc
13:48
<Treyh>
cool
13:49
<Lns>
alkisg: we need to join forces soon :)
13:49
possibly along with jan weber of opensuse/easyLTSP gui
13:50
Treyh: yes, you need to configure the printer via lts.conf in a client specific section
13:51
<alkisg>
Lns, sure. But I'm just looking for a hackish way to make installation/administration easier, while easyLTSP is a more proper solution (which I hope will finally start becoming cross-distro)
13:51
<Treyh>
Lns: thank you
13:51
<Lns>
alkisg: sure...but we all start somewhere
13:51
=)
13:52
Word on the list today is that easyLTSP will try to be cross platform in the newer releases, and is being re-written in python, which would be awesome because tcm-ng is also written in that
13:53
<Treyh>
is easyltsp still using opensuse?
13:54
well I mean does it run on opensuse?
13:55
<alkisg>
Lns, ok, that's a more proper long-term solution, I hope both of them work out. My sch-scripts is a short-term solution, i.e. I intent to finish most of the plugins within a week.
13:55
<Lns>
I haven't used easyltsp at all before, but it looks fair, though incredibly opensuse/kiwi specific
13:56
We're planning for tcm-ng to be extensible through plugins, so hopefully it will be very easy to add your own code and extend the functionality
13:56
along with all of the already awesome code from ogra through ltsp-manager and tcm
13:58Mathis has quit IRC
13:58Treyh has quit IRC
14:10Remaille has quit IRC
14:11Remaille has joined #ltsp
14:13pmatulis has quit IRC
14:15Remaille has quit IRC
14:16nubae has quit IRC
14:17nubae has joined #ltsp
14:41jammcq has joined #ltsp
14:42
<jammcq>
hello friends
14:42
<matttttt>
so i just enabled nxagent
14:42
is there any way to benchmark and see what kind of benefit i'm getting from nx compression?
14:45
<CAN-o-SPAM>
hi jamm
14:46
<sbalneav>
Hey jammcq
14:46
<jammcq>
Scotty !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
14:46
hey Alex
14:51Treyh has joined #ltsp
14:52
<Treyh>
i keep getting a tftp timeout error
14:57
<sbalneav>
Treyh: tftp might not be running, or your dhcp server might not be pointing your TC at the right server
14:58
<Treyh>
sbalneav: i fixed it, had to ltsp-image-update and reboot, strange lol
15:26hanthana has joined #ltsp
15:27bobby_C has joined #ltsp
15:30syn has joined #ltsp
15:42
<Treyh>
I have a couiple clients that keep getting a kernel panic error
15:42
they stop and have a blinking cursor right before LTSP Client should flash on the screen
15:43vagrantc has quit IRC
15:46
<sbalneav>
Treyh: That's going to be real hard to debug without knowing what the clients are :)
15:46
<Treyh>
sbalneav: one example is a dell laptop, d610
15:47
I also have one of their mac addresses
15:47
tried searching through /var/log/syslog and /var/log/messages with no match
15:48
<sbalneav>
Well, setting XSERVER=vesa in the lts.conf file might be a good place to start.
15:48
<Treyh>
so I set that mac to use the Vesa Driver and am updating the image now
15:48
yup just did that
15:48
<sbalneav>
Also, I'd do a memtest on the client.
15:48
<Treyh>
think might be a hardware memory problem?
15:48
that makes sense....
15:48
I didn't think of that
15:51CAN-o-SPAM has quit IRC
15:52
<Treyh>
on ubuntu, after updating lts.conf do I h ave to rebuild the client?
15:52
<sbalneav>
no, just a reboot
15:53
<Treyh>
reboot of server or client
15:53
<sbalneav>
client
15:54
<Treyh>
!pastebot
15:54
<ltspbot`>
Treyh: "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.
15:54
<ltsppbot>
"Treyh" pasted "[default] RDP_OPTIONS = "-a 16" (10 lines) at http://pastebot.ltsp.org/360
15:54
<Treyh>
see anything wrong with that lts.conf ?
15:55
<sbalneav>
off the top of my head, no, but I never use rdesktop, so I don't know if those options are correct.
15:56
gave up windows entirely a decade ago :)
15:56
<Treyh>
:P
15:56
i wish I could
15:56
i'm sure the rdesktop options are correct because they work on all my other clients
15:56johnny has left #ltsp
15:56
<Treyh>
just making sure really the specific mac address entries were correct
15:56
<sbalneav>
seem fine to me
15:57
<Treyh>
ty
15:58
what log would I look at, maybe it will point my in the right direction
15:59
<sbalneav>
No log on the server's going to have anything about a thin client kernel panic
15:59
<Treyh>
May 28 15:56:29 ltsp in.tftpd[5476]: tftp: client does not accept options
15:59
<sbalneav>
if the kernel's actually panicing, then there's something wonky on the client.
16:02
<jammcq>
'client does not accept options' is definately not causing the problem
16:02
that's just an informational message
16:03
<Treyh>
got it
16:03
so do a memtest
16:03
see if it passes or fails
16:03
get memtest from memtest.org
16:05mikkel has quit IRC
16:05
<Treyh>
so if memtest passes
16:05
what would be next?
16:06
<sbalneav>
Dunno.
16:07
We'll burn that bridge when we come to it :)
16:08spectra has quit IRC
16:09
<Treyh>
k
16:09
memtest is running, going good so far
16:09
it's around 50% with no errors yet
16:12
ok it just past 90% with no errors
16:12
i'll let it finish, but probably going to turn out with 0 errors
16:12
darn it, i wanted that to be it lol
16:12
i'm tired of messing with that darn laptop and desktop
16:13
<sbalneav>
how much memory in the desktop?
16:13
<Treyh>
256
16:15
the lowest is 256
16:15
the laptop with the same problem is using 512mb
16:15
<sbalneav>
So amount of ram isn't the problem then.
16:15
<Treyh>
hmmmm, when i specify a default and a mac option in lts.conf
16:16
<sbalneav>
Can you boot, say, a live cd on one of these machines?
16:16
<Treyh>
does the default option get applied to each individual mac also?
16:16
sure
16:17
<sbalneav>
sure, as in, yes it boots, or sure, as in, let me try that ? :)
16:17* Gadi blames all of life's problems on acpi
16:18
<Treyh>
let me try that
16:18
it's booting the live cd now
16:18
it had windows on it before, windows 2000, but I've taken the hard drive out
16:18* alkisg thinks the problems are there because life isn't open source
16:18
<Treyh>
lol
16:18
<sbalneav>
Gadi: You're probably correct. It'll be something along those lines, likely
16:19
<Treyh>
i have about a million of those laptops
16:19
and only a handful don't work with ltsp
16:19* Gadi always looks askance at acpi - he makes the perfect patsy
16:19
<Gadi>
Treyh: that laptop model has been used to define about a million different collections of hardware
16:19
:)
16:19
<sbalneav>
Treyh: so... if you have a million, and only a few dont work....
16:20
<Treyh>
lol
16:20
<sbalneav>
why not just circular file 'em and move on? :)
16:20
<Treyh>
trust me I agree with you
16:20
<sbalneav>
Right, then it's settled.
16:20
<Treyh>
but it's a school district, they need and use all of them on a daily basis
16:20
<matttttt>
i just added a second ltsp server, added the server to the LDM_SERVER list, the second server shows up under preferences\select host now when I pxeboot kiwi-ltsp from the primary server now, but i can't login to the new server, just times out. looks like ssh traffic is the last TC->new/secondary ltsp server traffic i see before LDM restarts.
16:20
<Treyh>
if 5 don't work
16:20
they're 5 short
16:20
<matttttt>
any ideas?
16:21
<Treyh>
sbalneav: so they don't have to work, but if I can get them to work, it would be a great help
16:21
I'm seeing more and more donated stuff with the same problem
16:21
they're good desktops / laptops, just seems like one little thing is off
16:21
<sbalneav>
Treyh: another thing to try would be to look at a WORKING one's bios, and one of the NON working ones, and check for differences
16:22
<Treyh>
sbalneav: have set both back to defaults, also set a working one back to defaults
16:22
<sbalneav>
k, I'm out of ideas then.
16:22
<Gadi>
matttttt: you need to add that server's ssh keys to the chroot's list of known hosts
16:22
matttttt: or cheat and turn StrictHostKeyChecking off
16:22
:)
16:22
<sbalneav>
Anywho, heading home for the day.
16:22
<Gadi>
but nobody likes me when I say that
16:23
<matttttt>
how do i go about doing it the first way? :)
16:23
<sbalneav>
Gadi: I love it when you talk config file ese to me.
16:23
be on later tonight.
16:23
<Gadi>
matttttt: have a look at the contents of: /opt/ltsp/i386/etc/ssh/ssh_known_hosts
16:24
<Treyh>
sbalneav: ty for the help
16:25
<matttttt>
just copy the contents from the ssh_known_hosts on my new server to that file on my primary?
16:25Treyh has quit IRC
16:26
<Gadi>
matttttt: hmm, I don't think you need all of it
16:26
<alkisg>
Gadi: speaking about StrictHostKeyChecking, I think SSH_OPTS support in lts.conf is now broken, can I verify and send a patch?
16:26
<Gadi>
only the ones for that host
16:26
alkisg: you dont need my permission to fix what's broken
16:26
:)
16:27
<alkisg>
Erm, actually I wasn't sure if it was *ever* supported as an lts.conf parameter
16:27
It would be a cool thing, though :)
16:27
<Gadi>
indeed - would you just add it for the SENTINEL?
16:27
it prolly makes most sense for just the SENTINEL connection
16:28
(ie the master socket)
16:28
<alkisg>
No, I want it to avoid updating keys, i.e.  CheckHostIP no   StrictHostKeyChecking no    LogLevel ERROR
16:28
<Gadi>
many opts won't work if its not the master control socket
16:28
<alkisg>
Ah ok
16:28
<Gadi>
so, you may need to get out your C screwdriver
16:28
:)
16:29
<alkisg>
Ouch. I guess I didn't get what you're saying yet, re-reading...
16:29
<matttttt>
ok added the keys from ssh_known_hosts on my new server that referenced itself to the file on my primary, same problem persists. perhaps i need to add the keys for my primary to my secondary?
16:29
<alkisg>
Ah, you mean ldm. Sure, no problem
16:29
<Gadi>
matttttt: did you update the image?
16:30
<matttttt>
hmm, nope. and actually the file I edited was in /srv/tftpboot/KIWI
16:30
<Gadi>
alkisg: yeah, sorry - I am barely coherent at this time of day
16:30
matttttt: ah do whatever kiwi need to update the image
16:31
after you edit the chroot's ssh_known_hosts file
16:31
<alkisg>
So.... would the other devs agree for allowing SSH_OPTS to be an lts.conf parameter? (please? :))
16:31
<Gadi>
alkisg: patch first - ask questions later
16:31
:)
16:31
<alkisg>
Heh ok I'll send a mail to ltsp-devs
16:40vvinet has quit IRC
16:41johnny has joined #ltsp
16:45alkisg has quit IRC
16:58bobby_C has quit IRC
16:58bobbyC has joined #ltsp
17:06
<Lumiere>
johnny: earcandy is totally awesome
17:06
thank you!
17:06vagrantc has joined #ltsp
17:37
<lupine_85>
is there any particularly compelling reason to use ldm over [gkx]dm?
17:39jammcq has quit IRC
17:40ajohnson is now known as ajohnson-afk
17:42lupine_85 has quit IRC
17:46Gadi has left #ltsp
17:52
<Lns>
even though you're not here lupine_85.....security?
17:55bobbyC has quit IRC
18:03vagrantc has quit IRC
18:09vagrantc has joined #ltsp
18:10lupine_85 has joined #ltsp
18:23
<johnny>
lupine_85, uhmm.. because it is required :)
18:23
lupine_85, i assume you like local devices, sound, local apps, etc
18:23
:)
18:24
<lupine_85>
erm, yeah, those things all seem nice :)
18:24
<johnny>
that's why
18:24
<lupine_85>
I didn't realise they were dependent on LDM
18:24
<johnny>
yes
18:24
at least for the moment
18:24
<lupine_85>
right... I should probably prod my work about that too
18:24
<vagrantc>
well, to have it work so easily- you could cobble some of it together with xdmcp
18:24
<lupine_85>
right now it's a trip to the server room if you want to plug in a USB drive;)
18:24
<johnny>
the ldm code is basically glue around an ssh connection :)
18:25
vagrantc, !
18:25
vagrantc, may we meet again someday
18:25
<lupine_85>
I'm all for thin clients, but there's a limit ;)
18:25
<vagrantc>
ldm allows a lot more flexibility, as it allows to run code, hooks, etc. client-side. xdmcp is basically *all* server-side.
18:25
johnny: indeed!
18:26
<johnny>
lupine_85, well.. usb devices should just work right now
18:26
what problems are you having?
18:26
<lupine_85>
you plug them in, you don't see the,
18:27
...m
18:27
(this is with gdm)
18:27
<johnny>
in gnome?
18:27
<lupine_85>
aye
18:27
<johnny>
ah
18:27
yes.. that would be teh case
18:27
<lupine_85>
I suspect the guy who set this up (many moons ago now) didn't know about that effect
18:27
I think we're still using esd for sound too
18:28* lupine_85 has taken it upon himself to make it all better(tm) :)
18:32
<johnny>
uhmm.. just using a new version of ltsp should make it better :)
18:32
<lupine_85>
I think they're using whatever was packaged with hardy
18:32
<johnny>
ahh.. that was fine
18:32
<lupine_85>
everyone's terrified to upgrade it in case it breaks
18:32
<johnny>
i used ltsp with gutsy and hardy
18:32
well.. if they want to have the good stuff, you gotta actually use ltsp
18:32
not a hack
18:37
<Lns>
lupine_85: i'm using hardy at tons of sites and pretty much all of the stuff mentioned "just works"
18:38
well, besides local apps
18:38
<lupine_85>
heh. there's something I'd quite like to get working straight away
18:38
we have a Java app that kills the LTSP server quite horribly while it's running (ILO stuff)
18:40staffencasa has quit IRC
18:40staffencasa has joined #ltsp
18:40staffencasa has quit IRC
18:46elisboa has quit IRC
18:52lucascoala has joined #ltsp
18:54pmatulis has joined #ltsp
19:00Lns has quit IRC
19:08vagrantc has quit IRC
19:25johnny has left #ltsp
19:29i0x73 has joined #ltsp
19:29
<i0x73>
hey guys
19:30
<sbalneav>
Hello
19:31
<i0x73>
doest ltsp have any kind of thin client
19:31
or is it just a server
19:31
<sbalneav>
ltsp is the software to run a thin client
19:31
You'll need a server, and hardware to act as the client
19:32
either an old pc, or a custom built thin client
19:32
<i0x73>
yes i understand that, the reason im asking this is that i need to be able to access local devices from thin client itself
19:33
as in run the thin client that connects to the server and utilizes the local audio card
19:33
something like that
19:34
any ideas ?
19:35
<sbalneav>
ltsp already supports remote audio
19:35
via pulse audio
19:36
as well, we support flash sticks, local hard drives and cdroms
19:36
<i0x73>
how about remote video/audio capture from tuner card
19:36
is the tuner card itself is supported by the linux distro im using
19:38
<sbalneav>
No, not remotely, but you could always try running your capture software as a local app.
19:39
<i0x73>
preety much i just wanna be able to use skype with a tuner card on thin client as a webcam and local mic input
19:39
so would i define the restrictions on the server itself for client to be able to access local devices
19:41
<sbalneav>
Well, none of that's supported out of the box. You could try experimenting around with local apps.
19:41
<i0x73>
alright thanks alot
19:41
can you recommend any specific thin clients to use ?
19:42
<sbalneav>
Well, if you're wanting a tuner card, that pretty much rules out a true thin client. Most of them don't support add-in cards.
19:42
So you'd probably just want a regular desktop, sans hard drive
19:43
<i0x73>
well yeah, i am planing to use an old pc
19:44
and possibly something like thinstation on it
19:44
can you recoment anything better
19:46
<sbalneav>
anything better than what? ltsp?
19:48
<i0x73>
im really new to this, they way i see it is ltsp is just a server soft accepting connecting using RDP, and i can use any RDP client to connect to it ?
19:48
<sbalneav>
no, ltsp doesn't accept connections via rdp, you've got it backwards.
19:48
ltsp is the software that runs on the thin client, served out by the server.
19:49
is uses X either tunneled via ssh, or directly
19:49
although ltsp physically sits on the server, it runs on the client.
19:49
reading the docs would probably help you to understand.
19:49
!docs
19:49
<ltspbot`>
sbalneav: "docs" is For the most current documentation, see http://wiki.ltsp.org/twiki/bin/view/Ltsp/LtspDocumentationUpstream
19:50GGD|sleeping is now known as GGD
19:51
<i0x73>
oooh
19:52
thanks ill read up on iy
19:53
<sbalneav>
afk for a bit.
19:53
back on later
19:54
<i0x73>
kool
19:55GGD has quit IRC
19:56GGD has joined #ltsp
20:05Ahmuck has joined #ltsp
20:05
<Ahmuck>
where r bugs reported?
20:06
where r bugs reported?
20:06
i need to report several bugs. where do i report bugs?
20:08pimpministerp has joined #ltsp
20:08lucascoala_ has joined #ltsp
20:13Ahmuck has quit IRC
20:14lucascoala_ has quit IRC
20:16Ahmuck has joined #ltsp
20:16lucascoala has quit IRC
20:16
<Ahmuck>
where do i report errors for ltsp clients?
20:17
<Ryan52>
the same way as you would report any bug.
20:18
<Ahmuck>
k, here is my bug. after running a client for a bit, i loose sound on the client. then i get gstreamer errors
20:18
any idea what's happening on the client?
20:18
<Ryan52>
I'm confused...
20:18
are you here because you need user support or want to report a bug?
20:19
18:06 < Ahmuck> where r bugs reported?
20:19
18:06 < Ahmuck> i need to report several bugs. where do i report bugs?
20:19
<Ahmuck>
i need to report multiple bugs on ltsp
20:19
<Ryan52>
ok, then report them the same way as you would report any bug.
20:19
<Ahmuck>
the client locked up
20:19
ok, well i report bugs on irc normally
20:19
so i've just reported one
20:19
<Ryan52>
we will not remember to fix a bug because some guy on irc told us about it.
20:19
ok...
20:19
let me phrase it this way...
20:19
<Ahmuck>
so, where do i go, what inet address do i need to navigate to so i can log the bug
20:20
<Ryan52>
report the bug the same way as you would report any other bug in your distro.
20:20
<Ahmuck>
so, ltsp.org does not have bug tracking, it's left up to the distro?
20:20
<Ryan52>
yes.
20:26
Ahmuck: it's not really "left up to the distro", because the fedora maintainers, the debian maintainers, and the ubuntu maintainers are basically all of uptsream ltsp.org.
20:27
<Ahmuck>
now i'm confused
20:27
<Ryan52>
so yes, just file it as an ubuntu bug, and we will take care of it :)
20:41Ahmuck has quit IRC
20:50Ahmuck has joined #ltsp
21:28Ahmuck has quit IRC
21:43i0x73 has quit IRC
21:53alkisg has joined #ltsp
22:00nubae has quit IRC
22:19nubae has joined #ltsp
22:44knipwim has quit IRC
22:48moquist has quit IRC
22:58Lns has joined #ltsp
23:04alkisg has quit IRC
23:12knipwim has joined #ltsp
23:19phantom has joined #ltsp
23:25Lns has quit IRC
23:25yoshi___ has quit IRC
23:25wigwam has quit IRC
23:28wigwam has joined #ltsp
23:32yoshi__ has joined #ltsp
23:38vagrantc has joined #ltsp