|00:13||M4gic5t0rM has quit IRC|
|01:22||alkisg has joined #ltsp|
|01:23||feinbein_fred has joined #ltsp|
|02:04||map7_ has quit IRC|
|02:57||maslak has quit IRC|
|03:01||Da-Geek has joined #ltsp|
|03:30||biomorph_ has joined #ltsp|
|03:36||biomorph_ has quit IRC|
|03:36||biomorph_ has joined #ltsp|
|03:38||biomorph_ has quit IRC|
anyone hear about itcan?
|04:59||alkisg has quit IRC|
|04:59||alexqwesa has quit IRC|
|05:29||alkisg has joined #ltsp|
|06:06||alkisg has quit IRC|
|06:11||ogra_ac has quit IRC|
|06:12||ogra_ac has joined #ltsp|
|06:16||alkisg has joined #ltsp|
|06:23||pmatulis has joined #ltsp|
|06:28||ogra_ac has quit IRC|
|06:28||ogra_ac has joined #ltsp|
|07:10||MorningSon has joined #ltsp|
|07:39||mgariepy has joined #ltsp|
ok, what am i doing wrong now.. i am trying to build kiosk-enviroment with command ltsp-build-client --chroot i386kiosk-new --kiosk and it builds normal desktop environment.
|07:53||mikkel has joined #ltsp|
|07:54||wwx has quit IRC|
|07:58||tomak has joined #ltsp|
Hi to everyone
does anyone use K12 Fedora ?
|08:01||* Appiah watches tumbleweed fly across the #ltsp channel|
|08:07||Gadi has joined #ltsp|
|08:20||wwx has joined #ltsp|
|08:29||pthsWork has quit IRC|
|08:31||Da-Geek has quit IRC|
|08:31||ogra_ac has quit IRC|
|08:35||ogra_ac has joined #ltsp|
|08:37||CrypTom has joined #ltsp|
Hi all, I've installed a kubuntu maverick server, installed the ltsp-server package (not standalone as we already have a dhcp server), i built the client, but when I boot the client, it always hangs
I changed /var/lib/tftpboot/ltsp/i386/pxelinux.cfg/default (I removed quiet and splash) and the client hangs after
* Starting LTSP client......
|08:39||alexqwesa has joined #ltsp|
after two minutes or so I get further lines telling me that "task lsb_release:xyz blocked for more than 120 seconds"
|08:40||komunista has joined #ltsp|
a bit higher up, I see a line: "[ 38.359132] nbd0:Hangup"
Ugh, sounds like nbd-proxy...
and later "unknown partition table"
alkisg: ok, I'm reading, thanks
alkisg: I've got no file named /usr/share/initramfs-tools/scripts/ltsp_nbd
on the server
CrypTom: that's in the chroot
After you apply the patch, run sudo chroot /opt/ltsp/i386 update-initramfs -u && sudo ltsp-update-kernels
just add the option nbd_proxy=false in /var/lib/tftpboot/ltsp/i386/pxelinux.cfg/default
Ah my code is in maverick, right :D
Forgot about that, still in 10.04... ;)
pfft so outdated
Long time no ...read
How are your ARMs?
pandaboard.org is up ...
and i just registered an ltsp spec for UDS
(i hope i dont collide with anything stgraber was planning, i searched but couldnt find anything)
alkisg, i'm currently trying to debug nbd-proxy, but with the debugging, it doesn't fall into the same raise condition, my thin client has been rebooting for like 12 hours successfully...
ok thanks, so I'm not using the patch, just the nbd_proxy=false
mgariepy: yeah I know I haven't been able to reproduce that here either, but I've heard many teachers having the same problem so we completely disabled nbd_proxy in Greece so I don't have any feedback about it anymore...
i know, in the office, we have like 20 or so thin client and on a mass reboot 2 of them failed to boot.
I've seen "negotiation errors", "squashfs errors" etc, all solved after removing nbd-proxy
alkisg, also http://ograblog.wordpress.com/2010/09/30/ubuntu-on-arm-the-best-since-sliced-bread/ :)
ogra_ac, any netbooks we can buy with ARM? Or is it only for thin clients / embedded stuff etc?
with the version of nbd-proxy i have for debugging, it gives me like 800k of data per boot but doens't fail at all.
Oooh funky blog theme :P
alkisg, you can buy the ac100 and install ubuntu on it
mgariepy: try rsync -an /rofs /tmp after you boot a client
(thats what i'm typing on atm)
And check syslog for errors
(fat clients work better for this, bigger images)
-an ==> read but not write
ok i see
doing it right now :)
thanks, it worked!!!
mgariepy: also try re-enabling compression, I think it makes the problem more obvious (compression doesn't give problems to clients without nbd-proxy, in my experience, only to those with nbd-proxy)
CrypTom: if you please, report the nbd_proxy=false workaround for maverick+
(in the bug report)
i don't use compression here.
mgariepy: yes, that makes problems *less* frequent, that's why I'm suggesting to reenable it...
|09:07||CrypTom has quit IRC|
|09:11||vongrippen has joined #ltsp|
|09:18||ogra_ac has quit IRC|
|09:19||ogra_ac has joined #ltsp|
|09:19||Uzzi has joined #ltsp|
alkisg, ok i'm starting to tests with the compression on.
mgariepy: isn't it possible to send a patch to upstream nbd-client for whatever feature nbd-proxy adds to it?
I think the maintainer is very cooperable, he already implemented the "multiple roots" option we asked him...
i will discuss that with julien an stgraber on monday, but anyway atm the code is not working relaibly enough
mgariepy: what's the main feature of nbd-proxy? Reconnect on disconnect? Multiple trasmits?
(i mean if the first transmission fails)
Or changing servers for ltsp-cluster?
|09:35||* alkisg has no clue about what nbd-proxy actually does..|
nbd-proxy implement, reconnection on disconnect after several minutes, and put the FS in iowait when disconnected
Doesn't nbd-client -persist support the reconnection part?
and resume transfert of fs access on reconnexion
if you pkill the process it will reconnect
but if it take 20 second it will fail
OK, both sound like they would be welcomed upstream, as much as I can tell... at least with a --root-file-system switch or something like that
And maybe the developer there could help with any current issues nbd-proxy has
and every file that is accessed on the thin client when disconnected will have a squashfs error and you need to clear the cache for those files.
we used nbd-proxy because nbd is a kernel module and the time would have been too long to have it upstream
Understandable, but now that there's no time pressure, it'd be good to have 1 tool for nbd connection instead of needing 2 of them
Better speed (no localhost transfers), lower memory usage, maybe even easier bug fixing because it would be 1 app instead of 2 etc...
yeah but there is always time presure ;) we do not want to maintain a kernel module for 2 years
There is an nbd maintainer, you would just send a feature request / patch... imho...
Anyway, bye all :)
|09:47||alkisg has quit IRC|
|09:49||ogra_ac has quit IRC|
|09:53||ogra_ac has joined #ltsp|
|09:53||Sorinan has joined #ltsp|
Why an app like "VirtualBox Manager" running on server would crash only on one terminal, and not on all others? There's no difference in the config...
|09:55||jhutchins_lt has joined #ltsp|
|10:06||jhutchins_lt has quit IRC|
|10:09||jhutchins_lt has joined #ltsp|
|10:13||Sorinan has quit IRC|
|10:18||alkisg has joined #ltsp|
|10:45||[GuS] has joined #ltsp|
|10:45||[GuS] has joined #ltsp|
|10:46||Uzzi has quit IRC|
|10:47||vongrippen has quit IRC|
|10:52||vongrippen has joined #ltsp|
mgariepy: are the nbd-server/nbd-client in the same source tree as the nbd kernel module? I think they're separate, userland tools... http://nbd.git.sourceforge.net/git/gitweb.cgi?p=nbd/nbd;a=shortlog
So even if the nbd-server/client maintainer doesn't accept the reconnection patches (I don't see why he wouldn't), couldn't those be maintained as ubuntu specific patches in a debian/patch directory, for cpu / speed / memory / stability reasons, instead of maintaining a wrapper tool?
|11:05||kusanagi has quit IRC|
(another handy patch would be to have a named "swap" export, so that we could merge nbdswapd and nbdrootd and use the IANA assigned port for nbd-server)
|11:08||sweetpi has joined #ltsp|
|11:29||alkisg has quit IRC|
|11:40||Mava has joined #ltsp|
Ahh drat, alk just left.
Anyone here using NFS4 on fat clients?
|12:06||feinbein_fred has quit IRC|
|12:38||wwx has quit IRC|
|12:38||wwx has joined #ltsp|
|12:38||[GuS] has quit IRC|
|12:51||sweetpi has quit IRC|
|12:59||vagrantc has joined #ltsp|
|13:30||vagrantc has quit IRC|
|13:31||heru has joined #ltsp|
i was wondering if anyone was familiar with a kernal panic issue on the Dell Optiplex 755 and 760
we are actually using 4.2 so forgice us
we run optiplex 2x0, but we're on Ubuntu w/ LTSP5.x
heru, forgive is one thing.. but getting help for that is nearly impossible
few people around here have ever used ltsp 4.2
might wanna post on the mailing list instead
yeah i figured.... have you had any driver issues with the network card?
on the optiplex 755
|13:52||vongrippen has quit IRC|
still out of scope for this chan
not gonna guess the nic chipset; at the least it would make sense to post what lspci says
heru: what type of kernel panaick? Can you give us a snippet of the log?
heru: I had an issue with my fat clients on optiplex gx620s.
|14:26||bobby_C has joined #ltsp|
it posted that it could not determine the type of nic
it advises us to add the info "option-129" in the dhcpd.conf
heru: Oh. Well if it can't find the type of nic, then it sounds more like a kernel/driver issue than anything else, but I'm not sure really.
that is what i thought.... so we need to determine the driver/chipset for this machine
heru: what does lspci show you?
|14:38||heru has quit IRC|
Humm, it appears to have shown him the futility of his ways....
abeehc: You're right, it was out of scope, but still may have been fun to dig into/help fix.
|14:43||* Kyle__ has a perverse sense of fun.|
|14:44||* Gadi puts money on intel nic with e1000e driver that never existed back in LTSP 4.2 days|
|14:45||pmatulis has quit IRC|
|14:45||mistik1 has quit IRC|
I never had the money, or worked with places that would spend the money, for a good enough card to be on the unsupported list in the days 4.2 would have been used.
well, it wasn't an unsupported list - 4.2 had a niclist of what it could figure out on its own
Kyle__, no kidding. back then, was happy to be able to buy $15 3com SOHO NICs and not make do with used NICs.
4.2 was very minimal
it had a "niclist" in the initramfs that served as its lookup table
(4.2 predated udev by and large)
|14:49||* Kyle__ still remembers being happy about finnaly getting rid of the last ISA nics he had to deal with.|
|14:50||mistik1 has joined #ltsp|
|14:53||mgariepy has quit IRC|
Is there an easy or at least streightforward way to enable an autologut/timeout for clients?
read lts.conf manpage
|15:08||mgariepy has joined #ltsp|
some variables there
assuming you've installed the ltsp-docs package =)
i've not seen anything in lts.conf that will acheive that, Kyle__
sounds like it should be a function of gnome-session i dunno
I must have missed them.
johnny: My version only lists some things abut an LDM timeout, to auto-login if no one has logged in yet.
oh.. logout .. i think alkisg had something for that
i only saw "autolog" hah
|15:21||rad4christ has joined #ltsp|
Hey guys, hope I can get a really quick bit of help
Well, honestly I have two logout issues. one I need something that will stop/kill a session that's gone on too long, and two, I need it to run a specific script as part of the logout (to cleanly shutdown a running virtualbox session(.
I have 10.10 installed iwth an LTSP server, all is working, except I've installed Firefox and flash locally. when I try to run it, I get an error that Firefox is already running
And BTW stgraber, very awesome work on this!
rad4christ: Well is the same user already running firefox on a different station? Either that, or firefox crashed leaving aroudn it's lock file.
Kyle__: this is the first the users have been logged in.
And each station (2 at the moment) are under different logons
rad4christ: If (big if), there is nothing important in that users firefox config, blow it away, and re-run firefox. See how it goes.
IT's a test box, I'm looking to roll it tonight, so there's no info I'm worried to lose.
rad4christ: If your users will be logging into multiple sessions at once, know that this could be an issue. google-chrome has a --temp-profile option, which is useful for simultanious login issues.
rad4christ: test box? Then rm -rf ~/.mozilla and try and launch it again :)
Kyle__: autologout would be up to the desktop environment to handle - so, I would have a look into gnome, if that is what you use
Gadi: OK, I'll dig through it.
Gadi: I'm not a huge fan of how gnome tries to take over the system, but I guess it makes sense in this one situation :)
Kyle__, don't get me started on the whole black-box DBUS mess.
Kyle__: Worked! Thanks!
|15:29||* Kyle__ hates dbus|
Flash isn't working, though, doggonit.
|15:29||* Kyle__ loves linux, and hates ubuntu& gnome...but ends up using them anyway.|
|15:40||rad4christ has quit IRC|
|15:59||Gadi has left #ltsp|
|16:21||gentgeen__ has quit IRC|
|16:21||gentgeen__ has joined #ltsp|
|16:22||mgariepy has quit IRC|
|16:27||tomak has left #ltsp|
|16:49||mikkel has quit IRC|
|17:05||M4gic5t0rM has joined #ltsp|
|17:27||jhutchins_lt has quit IRC|
|17:30||komunista has quit IRC|
|17:31||ogra_ac has quit IRC|
|17:44||ogra_ac has joined #ltsp|
|17:46||johnny has left #ltsp|
|17:48||bobby_C has quit IRC|
|17:56||alkisg has joined #ltsp|
Kyle__: for cleaning up after logout, see the xexit program that sbalneav made, it's much better than gnome-watchdog
(in his ppa)
|18:06||cliebow has joined #ltsp|
|18:06||cliebow_ has joined #ltsp|
|18:14||ltspbot` has joined #ltsp|
|18:15||jhutchins_kc has quit IRC|
|18:15||jhutchins_kc has joined #ltsp|
|18:28||mistik1 has quit IRC|
|18:39||mistik1 has joined #ltsp|
|18:54||alkisg has quit IRC|
|19:08||staffencasa has quit IRC|
|19:14||cliebow has quit IRC|
|19:27||Lumiere has quit IRC|
|19:35||Lumiere has joined #ltsp|
|19:39||pmatulis has joined #ltsp|
|20:18||jhutchins_lt has joined #ltsp|
|20:24||litlebuda has joined #ltsp|
|20:40||jhutchins_lt has quit IRC|
|20:43||litlebuda has quit IRC|
|21:18||heru has joined #ltsp|
|21:22||leio_ has joined #ltsp|
|21:25||vvinet_ has joined #ltsp|
|21:25||wwx has quit IRC|
|21:25||vvinet has quit IRC|
|21:25||leio has quit IRC|
|21:26||wwx has joined #ltsp|
has anyone had problems with network cards dropping configuration
|21:34||sweetpi has joined #ltsp|
|21:59||M4gic5t0rM has quit IRC|
|22:03||M4gic5t0rM has joined #ltsp|
|22:15||ogra has quit IRC|
|22:23||vagrantc has joined #ltsp|
|22:29||ogra has joined #ltsp|
|22:31||vagrantc has quit IRC|
|22:37||heru has quit IRC|
|22:52||MorningSon has quit IRC|
|23:56||cfkane has quit IRC|