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


Channel log from 27 October 2010   (all times are UTC)

00:07_UsUrPeR_ has quit IRC
00:13_UsUrPeR_ has joined #ltsp
00:21alkisg has joined #ltsp
00:39alkisg has quit IRC
00:59
<map7>
I'm trying to put a cron job in my lts.conf but it's not accepting it on the client side. I'm using 'CRONTAB_01="56 16 * * * /sbin/halt"'
01:00
I'm using Ubuntu 10.04 and I've set the time on my client the same as my server
01:00
the cron job never runs
01:00
I can see it when I boot my ltsp client though in /etc/cron.d/ltsp
01:43alkisg has joined #ltsp
02:08gorkhaan has joined #ltsp
02:11jimjimovich has joined #ltsp
02:13
<jimjimovich>
hi everyone. I was wondering if there is a way to show the progress of files being written to USB flash drives ... or a way to safely remove them from a thin client
02:14
<johnny>
safe way is wait 10 seconds and take it out
02:14
it auto unmounts
02:14
or maybe it's just 2 seconds, i can't remember
02:18
<jimjimovich>
johnny: the problem seems to be with big files
02:18
it takes quite a while for them to be written to the drive from the server
02:21otavio has quit IRC
02:27
<johnny>
not muh can be done until the 2 systems can communicate better i think
02:27otavio has joined #ltsp
02:27otavio has joined #ltsp
02:29
<jimjimovich>
If I knew a bit more about how the system worked, perhaps I could write a little indicator app for it or something. I'll have to look into it.
03:06Da-Geek has joined #ltsp
03:38Uzzi has joined #ltsp
04:54
<Hyperbyte>
Hmm
04:54
I have 3 thin clients here... one with ATI graphics, one with NVidia graphics and one with Intel graphics
04:55
The one with ATI graphics seems to be using the "radeon" kernel module, the NVidia & Intel one uses a standard "video" kernel module
04:55
All three thin clients had a little sluggish performance, until I put X_COLOR_DEPTH=16 in lts.conf
04:56
Since then the ATI one has been performing wonderful. Couldn't tell remote apps apart from running on localhost.
04:58
Now I guess I'm wondering if anyone could tell me if installing proper kernel modules for the thin client graphics would solve all problems or not...
05:01
Or maybe if there are better things to try...
05:01
<alkisg>
nvidia and intel are using the "video" kernel module? Not nouveau and intel?
05:01
i915 or whatever?
05:02
<Hyperbyte>
Hrm
05:02
Intel said "video" i915
05:02
<alkisg>
lspci -nn -k
05:02
<Hyperbyte>
And nvidia said "video" nouveau I think yeah
05:02
You want the output of that from the three thin clients?
05:03
<alkisg>
That's the command that will tell you which modules are used
05:03
<Hyperbyte>
Hmmm
05:03
Ok, just used lsmod before.
05:03
<alkisg>
E.g. in mine shows: $ lspci -nn -k | grep -A 2 VGA
05:03
01:00.0 VGA compatible controller [0300]: nVidia Corporation G84 [GeForce 8600M GT] [10de:0407] (rev a1)
05:03
Kernel driver in use: nvidia
05:03
Kernel modules: nvidia-current, nvidiafb, nouveau
05:03
So no "video" module there
05:18
<Hyperbyte>
No, you're right
05:18
<-- not 100% here today
05:19
So yeah, ATI one is using radeon, NVidia one nouveau and nvidiafb (sp?) and the intel one i915
05:19
So I guess then the question is... how come X_COLOR_DEPTH=16 fixed all my performance issues on the thin client with the ATI chipset and not on the other two?
05:20
Sorry I don't have a more specific question. =) Looking for some pointers to further debug this
05:26mistik1 has quit IRC
05:27mistik1 has joined #ltsp
05:37
<alkisg>
Hyperbyte: Are they about the same in terms of CPU power?
05:37
Do you have ldm_directx=true in lts.conf?
05:38
Try running "iftop" on the server to watch the traffic, and then try a youtube video on each of the terminals separately, to see for network bottlenecks. At the same time run a "top" *locally* on the clients to watch for cpu problems.
05:39
<Hyperbyte>
alkisg, I'll do that now. LDM_DIRECTX=True is in lts.conf and they should all three be sufficient in CPU power... the Intel one is an LTSP terminal from Disklessworkstations, the Nvidia one is actually just a regular PC using PXE boot
05:40
<alkisg>
Also check (with ps -ef|grep compiz) if the ati one is using composition
05:41
!localxterm
05:41
<ltspbot`>
alkisg: "localxterm" :: while sitting on a thin client, open a gnome terminal. In that, run: ltsp-localapps xterm. An xterm will open. That xterm runs locally, so any commands you enter there are executed directly on the client.
05:46
<jimjimovich>
anyone have a tip or link to info that would help me to better understand how the removable drives work on an ltsp thin client? How can I tell if the drive is currently in use?
05:48
<Hyperbyte>
alkisg: no output with the ps -ef | grep compiz
05:49
<pod2>
jimjimovich: usually the light on the usb drive flashes lots when it's reading/writing. not much use, I know.
05:49
<Hyperbyte>
alkisg: no CPU problems as well, doesn't even get above 10% CPU usage... network traffic on the server seems to hang somewhere around 50 megabits per second while playing a youtube video. It's connected to a gigabit cisco switch, so it should be able to go even much higher than that if needed
05:50
Thin clients are also running gigabit mode... can't find anything with CPU or network that would cause this
05:50
<alkisg>
Hyperbyte: full screen youtube?
05:50
<Hyperbyte>
Thing is, YouTube video's a dead giveaway that two of the clients have performance problems, but the whole interface is more sluggish
05:50
<alkisg>
That should go way more than 50mbps / 10%cpu
05:51
<jimjimovich>
pod2: yeah, I know, but my users don't seem to understand. I'm looking into writing a small app that'll show if they can safely remove the drive or not. I get people who copy big files and immediately remove the drive, then they can't figure out why the file is zero bytes :)
05:51
<Hyperbyte>
alkisg: well, it's 10% CPU on a computer with a 2.2ghz processor... so...
05:52
Plus I'm not running fullscreen, somehow the fullscreen button doesn't work... seems to crash the plugin
05:52
<alkisg>
There's another button that "extracts" the video to a different window
05:52
...and you could then resize that window to fit most of the screen
05:53
<Hyperbyte>
Hm, well I just zoomed in my browser to have the youtube video cover most of the screen
05:53
<alkisg>
gigabit + good cpu on the clients etc => it doesn't make much sense then to have sluggish behavior
05:53
<Hyperbyte>
It's now at 270 megabit. =)
05:53
That's on the good thin client
05:53
<pod2>
jimjimovich: can't really help any more with that. I'm stuck trying to get local drives working at all with rdesktop and a 2008r2 server :(
05:53
<Hyperbyte>
I'll see what the nvidia one does.
05:54
<jimjimovich>
pod2: that doesn't sound fun at all!
05:57
<pod2>
it works fine with win 2003 server, but not 2008r2
06:08alkisg has quit IRC
06:21alkisg has joined #ltsp
06:25
<Hyperbyte>
alkisg: hmm... apparently only the ATI thin client seems to be able to get the terminal server above 270 mbit/s...
06:25
The other two stick at 50, 60 mbit/s
06:25
<alkisg>
Hyperbyte: run top on a localxterm to see if it's a cpu problem
06:25
!localxterm
06:25
<ltspbot`>
alkisg: "localxterm" :: while sitting on a thin client, open a gnome terminal. In that, run: ltsp-localapps xterm. An xterm will open. That xterm runs locally, so any commands you enter there are executed directly on the client.
06:26
<alkisg>
l8r...
06:26
<Hyperbyte>
It's not a CPU problem
06:26
<alkisg>
Did you run top on a gnome-terminal on the client?
06:26
That runs on the server...
06:26
<Hyperbyte>
localapps-xterm, top
06:27
Only pulseaudio and X eating CPU, but nothing spectacular.
06:27* alkisg can't chat right now, bb in a while...
06:28
<Hyperbyte>
I think it -could- be network related. I have a gigabit network... the ati one seems to be able to pull 1.10 gbit/sec, the other ones "only" 500 mbit/s... should be enough, but it might indicate some underlying problem
06:28
Sure, no worries. :)
06:45F-GT has quit IRC
06:50mgariepy has joined #ltsp
06:53hughessd has joined #ltsp
06:53
<hughessd>
howdy folks,
06:53MorningSon has joined #ltsp
06:54
<hughessd>
im in kind of a bind. i just tried to update my server and clients and now the thin clients won't boot
06:54
does anyone feel like lending a hand (or ear)?
06:57
i am at a loss. even when i tried to roll back to a previously saved img, i run into snags
06:58
<muppis>
Do you have any idea where it hangs?
06:58
<hughessd>
well, it boots, makes a dhcp request, then seems to be loading the img
06:59
when it gets to the point where it supposed to load the GUi login,.... it doesn't
06:59
the last thing on the tty8 is
07:00
udhcpc (v0.9.9-pre) started
07:00
udhcpc: sending discover
07:00
* Setting up LTSP client
07:00
* Setting up console font and keymap
07:00
* Starting LTSP client
07:01
tty= /dev/tty8
07:01
<and then it just gives me the root prompt for the client>
07:01F-GT has joined #ltsp
07:01
<hughessd>
muppis: thank you for the response btw
07:03
<pmatulis>
hughessd: what OS?
07:04
<hughessd>
ubuntu
07:04
<pmatulis>
hughessd: you updated how?
07:04
<hughessd>
i was trying to upgrade from 10.04 to 10.10
07:04
<pmatulis>
hughessd: oh, upgrade
07:04
<hughessd>
but before i tried that, i updated
07:05
i didn't get to the dist-upgrade, just upgrade
07:05
then I did ltsp-update-image
07:06
<jimjimovich>
does Ogra still hang out in here sometimes?
07:07
<pmatulis>
hughessd: don't understand the update, upgrade, dist-upgrade stuff, sorry. explain again?
07:10
<hughessd>
the howtos i was following said that before trying to upgrade to a different release of ubuntu, i should update to the latest software
07:10
so and update just grabs the latest list of available sw
07:10
upgrade actually gets the sw
07:10
<pmatulis>
hughessd: yes, that mean 'apt-get update; apt-get dist-upgrade'
07:10
<hughessd>
yeah
07:10
hahah
07:11
sorry my bad
07:11
<pmatulis>
haha?
07:11
<hughessd>
i was trying to explain something that you obviously knew
07:12
<pmatulis>
hughessd: then to upgrade to the next release you did what?
07:12
<hughessd>
i didn't get to the next release
07:12
<pmatulis>
hughessd: ok, you're still on 10.04
07:13
<hughessd>
after i did "apt-get upgrade" on the LTSP server, I tried to make a new client image
07:13
<pmatulis>
hughessd: i said it's 'apt-get dist-upgrade'
07:13
<hughessd>
and then test to see if it went ok.
07:13
it didn't ....
07:13gentgeen__ has quit IRC
07:13gentgeen__ has joined #ltsp
07:14
<hughessd>
yes i know that 'upgrade' and 'dist-upgrade' are different. i was going to do a dist upgrade but didn't get that far
07:14
<pmatulis>
hughessd: not sure why. do it now
07:14
<hughessd>
my LTSP stopped working just after the regular upgrade
07:14
a dist-upgrade would take an hour if not more
07:15
<pmatulis>
hughessd: why?
07:15
<hughessd>
i just want to get it working off the old img
07:15
why would it take an hour?
07:15
<pmatulis>
hughessd: yeah
07:15
<hughessd>
because that's how long it takes to download and install all the changes i guess
07:15
how long does it usually take for you?
07:16alkisg has quit IRC
07:17alkisg has joined #ltsp
07:17
<pmatulis>
hughessd: you're mixed up. can you pastebin the output to 'sudo apt-get -s dist-upgrade' ?
07:17
<hughessd>
i really don't think im mixed up
07:17
<pmatulis>
hughessd: ok, bye
07:18
<hughessd>
really
07:20
it says 0 to upgrade
07:21
<pmatulis>
hughessd: fine. so it's not an hour
07:21
<hughessd>
ok not an hour
07:21
<pmatulis>
hughessd: 0 minutes actually
07:22
<hughessd>
i just thought that because i just dist-upgraded a laptop and it took that long
07:22
but yes
07:22
0 minutes for this
07:22
<pmatulis>
hughessd: i suggest you rebuild the client image, looking out for any errors
07:23
hughessd: did you update/upgrade the client chroot as well?
07:23Uzzi has quit IRC
07:23
<hughessd>
yes
07:23Uzzi has joined #ltsp
07:24
<pmatulis>
hughessd: so go ahead and update the image
07:24
<alkisg>
hughessd: dist-upgrade means "update 10.04", not "go to 10.10".
07:25
<hughessd>
alkisg: im an idiot
07:25
but in any case, both server and client are still 10.04, but updated to latest
07:25
i ran 'ltsp-update-image'
07:25
<alkisg>
Maybe some new xorg driver makes your client fail. What graphics card?
07:26
And also, after the update, did you run ltsp-update-kernels?
07:26
<hughessd>
the thinClients have built in video cards
07:26
<alkisg>
Which ones?
07:26
<hughessd>
i did run 'ltsp-update-kernels'
07:27
the thin clients are MSI, but i don't have the video cards specs on hand
07:27
<alkisg>
Try putting SCREEN_027=shell in lts.conf
07:28
...that will give you no X, plain console
07:28
There you can run lspci -nn -k | grep -A 2 VGA
07:28
...to see the model + driver used
07:28
*SCREEN_02, not 27....
07:28
sorry, I meant SCREEN_07. Bah.
07:28
<hughessd>
ok, thank you. hang on a sec while i try that.
07:29
quick question:
07:29
<Hyperbyte>
alkisg: you have time for another riddle? =)
07:29
<hughessd>
after changing lts.conf, do i have to run 'ltsp-update-image'?
07:30
or just go ahead and try to reboot the client...
07:30
?
07:30
<alkisg>
Hyperbyte: I'll be on and off for a while, but shoot, if I can't answer I'm sure someone else will
07:30
hughessd: just reboot
07:30
<Hyperbyte>
Okay! :-) Here it comes.
07:30
Since I couldn't get the nvidia thin client (the sluggish one) above 50, 60 mbit/s I decided to test the network.
07:31
Now it's a gigabit network, with decent switches, intel network cards in the servers, shielded cat 6 cables in the walls... decent everything.
07:31
It can easily pull full gigabit capacity, as witnessed by knoppix liveCD and ipref:
07:31
http://secondary.recreatie-zorg.nl/jan/iperf-knoppix.txt
07:32
<alkisg>
You can test iperf directly from the thin client prompt
07:32
No need to use knoppix
07:32
This way you also test for any driver problems
07:32
<Hyperbyte>
alkisg: that's what I did first, but I used knoppix to double-check.
07:32
See, the LTSP client gives completely different results:
07:32
http://secondary.recreatie-zorg.nl/jan/iperf-ltsp.txt
07:32
<hughessd>
alkisg: still the same result
07:33
<alkisg>
hughessd: can you put your /var/lib/tftpboot/ltsp/i386/lts.conf to pastebin?
07:33
!pastebot
07:33
<ltspbot`>
alkisg: "pastebot" :: The LTSP pastebot is at http://ltsp.pastebin.com. Please paste all text longer than a line or two to the pastebot, as it helps to reduce traffic in the channel. Don't forget to paste the URL of the text here.
07:33bobby_C has joined #ltsp
07:33
<Hyperbyte>
So, the thin client only transmits as half the speed of gigabit, yet I can't see any reason why it would do that.
07:33
*at
07:35
<alkisg>
Hyperbyte: which driver? r8169?
07:35
<Hyperbyte>
forcedeth
07:36
<alkisg>
Never seen that, it could be a driver issue. But still you should be able to exceed 100mbps easily.
07:36
<Hyperbyte>
Well, I can.
07:36
Just not 500mbps. =)
07:36
<alkisg>
By playing videos etc, not with iperf
07:36
<Hyperbyte>
Oh, yeah
07:36
Well that I can't.
07:37
Video stutters.
07:37
<alkisg>
Hyperbyte: so something else is limiting your client
07:37
<hughessd>
http://ltsp.pastebin.com/ETrtuzWG
07:37
<alkisg>
It's possible that it is the driver, for nouveau, but it shouldn't be the driver for the intel one
07:37
hughessd: remove SCREEN_07=ldm
07:38
<Hyperbyte>
Plus, the intel one isn't using forcedeth
07:38
<alkisg>
hughessd: Also remove MODULE_01 and LOCAL_MEDIA, are those really needed?
07:38
<hughessd>
alkisg: i really appreciate you taking the time to try and help. ive gone ahead and posted the lts.conf
07:38
it's pretty basic
07:39
<alkisg>
hughessd: see my comment above about removing the ldm line
07:39
<hughessd>
ok
07:39
the MODULE_01 and LOCAL_MEDIA are needed for certain parts of my network.
07:39
but i'll take them out for now and see how things work. just a sec.
07:40
<alkisg>
hughessd: there's no "LOCAL_MEDIA" option in ltsp
07:40
Maybe you read some obsolete documentation?
07:41
<hughessd>
that is possible, but i didn't set up this LTSP network. my predecessor did. which is why im having all sorts of trouble trying to learn to administer it.
07:41
<alkisg>
You can safely remove it, no ltsp script uses a LOCAL_MEDIA option
07:42
<hughessd>
also, can you think of a reason that a thin client would come up with squashfs errors when issued a reboot command?
07:43
i have been having to hard cycle the power on the thin client, when usually i can just issue a 'shutdown -r' or 'reboot' or something...
07:43
<alkisg>
hughessd: which ubuntu version?
07:43
10.04? it shouldn't do that...
07:43
Unless your chroot is 9.10...
07:45
<hughessd>
don't think it is. i watched the old IT guy update everything
07:45
a few months ago....
07:45
oh yeah, yes, 10.04
07:46
<alkisg>
hughessd: grep RELEASE /opt/ltsp/i386/etc/lsb-release
07:46
<hughessd>
another strange symptom: there is a "Connection Refused" error taht flashes after the boot splash, then the screen goes black. no cursor even.
07:47
ummm....
07:47
hm
07:47
you are pretty amazing
07:47
<alkisg>
9.10? :)
07:48
<hughessd>
DISTRIB_RELEASE=9.10
07:48
wow
07:48
ok
07:48
<alkisg>
So delete that chroot and rebuild it
07:48
<hughessd>
...
07:48
<alkisg>
Any troubleshoting comes AFTER that :)
07:48
<hughessd>
to be honest
07:48
im am scared
07:48
but ive got back ups
07:48
so....
07:48
ok
07:48
here goes
07:48
<alkisg>
sudo mv /opt/ltsp /opt/ltsp.910
07:48
That way you don't lose anything
07:48
<hughessd>
and then just run 'ltsp-build-client'?
07:49
<alkisg>
Right
07:49
i386 server
07:49
?
07:49
or amd64?
07:49
<hughessd>
i686
07:49
<alkisg>
dpkg --print-architecture
07:49
<pmatulis>
hughessd: i asked you whether you upgraded the chroot and you said 'yes'
07:49
<hughessd>
i386
07:49
i was going off /proc/version
07:49
oops
07:50
<alkisg>
hughessd: go ahead and call ltsp-build-client
07:50
Chroot upgrades aren't recommented, the proposed way is to rebuild
07:50
dist-upgrade on the other hand just updates it, it doesn't go to a newer version
07:52
ltsp-build-client does some magic while building the chroot, which might be lost on release-upgrades
07:52
<hughessd>
i wonder what other problems this has been causing....
07:52
alkisg: thanks again.
07:52
<alkisg>
np
07:52
<hughessd>
regardless of if this works
07:53
i have been trying to figure this out for a few hours now
07:53
<alkisg>
We'll troubleshoot it if it doesn't, don't worry :)
07:53
<hughessd>
its almost 6am. and im just glad to have someone to talk to.
07:53
<alkisg>
4pm here :D
07:53
<hughessd>
europe?
07:53
which country?
07:54
<alkisg>
Greece
07:54
<hughessd>
ah nice. never been there though.
07:54
<alkisg>
You? US?
07:55
<hughessd>
Yes, US, on the west coast
07:55
Portland, Oregon
07:57
how do you know so much about ltsp?
07:57
do you do this for work?
07:58
<alkisg>
I'm an IT teacher, but I liked LTSP so I got in a ministry team that wants to push LTSP to greek schools
07:58
<hughessd>
i had never heard of LTSP before 6 months ago.
07:59
now its a major part of my job.
07:59
and i have such a poor understanding of it....
07:59
one of the reasons why my distro is so out of date. i was too uncomfortable with trying to fix it.
07:59
<alkisg>
It's worth the trouble learning about it :)
07:59
<hughessd>
i think so.
08:00jimjimovich has left #ltsp
08:00
<hughessd>
i just wish it wasn't a "trial by fire" like this.
08:00
<alkisg>
There's no need to upgrade to 10.10 if everything works fine with 10.04 for you
08:00
10.04 is an LTS release so it can be directly upgraded to 12.04 when the time comes
08:00
<hughessd>
yeah,
08:01
after this experience i am just going to not touch it, if it's working
08:04
the image is finished. i rebooted and it dropped me into 'root@ltsp250:/#'
08:05
<alkisg>
hughessd: nice. run an "lspci -nn -k | grep -A 2 VGA" there to see the graphics card,
08:05
...and then remove "SCREEN_02=shell" to test it it's working without doing anything
08:07
<hughessd>
VGA compatible controller [0300]: intel corp. 82945G/GZ integrated graphics controller
08:07* Hyperbyte shivers
08:07
<Hyperbyte>
=)
08:07
<hughessd>
kernel driver in use: i915
08:07
kernel modules: i915
08:07
!!!!
08:07
<ltspbot`>
hughessd: Error: "!!!" is not a valid command.
08:07
<hughessd>
oops
08:07
I just ctrl+alt+f7 and i got the login!
08:08
now, i just have to figure out how to make it go to that by default....
08:09
<Hyperbyte>
hughessd: SCREEN_01=ldm and remove all other SCREEN_* lines
08:09
<hughessd>
is there no need for a shell terminal?
08:09
<Hyperbyte>
It's for debugging
08:10
<alkisg>
hughessd: just remove ALL SCREEN_xx lines from lts.conf
08:10
<Hyperbyte>
You don't want it on by default, because then everyone can have a root login on the thin client by pressing ctrl+alt+fN
08:10
<alkisg>
It defaults to giving you an ldm prompt
08:10
<Hyperbyte>
Ah. :)
08:10
<hughessd>
ah ok
08:10
<alkisg>
hughessd: also, for speed reasons, some time read about LDM_DIRECTX in lts.conf
08:11
!directx
08:11
<ltspbot`>
alkisg: "directx" :: If you want to turn off encryption to the workstation, which will speed up performance at the cost of security, you need to specify LDM_DIRECTX=True in your lts.conf file. Type !docs in IRC to get a link to the current documentation
08:11
<Hyperbyte>
alkisg: question! In my config it says LDM_DIRECTX=yes... does that matter?
08:11
(instead of True, it says 'yes')
08:12
<alkisg>
I think they're equivalent
08:12_UsUrPeR_ has quit IRC
08:12
<Hyperbyte>
Thought so... since that's default config, except I removed a # in front of the DIRECTX line. :-)
08:14
<hughessd>
hm
08:15
ive removed all SCREEN lines but it still drops me into a tty8 console
08:18
<alkisg>
hughessd: upload your /var/lib/tftpboot/ltsp/i386/lts.conf directory again. Also check if you have a /srv/tftp directory on your server.
08:18
*file, not directory
08:19
*for the lts.conf sentence :D
08:19
<Hyperbyte>
alkisg: I figured it out!
08:19
And I'm pleased to say it's entirely my own stupid fault.
08:19
<hughessd>
[default]
08:19
MODULE_01=usbkbd
08:19
[00:24:21:7d:c3:0f]
08:19
LOCAL_APPS=true
08:20
<Hyperbyte>
Still, you know... heh.
08:20
There was some script running in the ltsp chroot that set the network card's MTU as high as possible... don't ask me how that got there, major screw-up.
08:21
Anyway... two of the thin clients (the nvidia and intel ones) supported high mtu, so set their mtu to 7200 thus bogging down the network interface without causing network traffic... call it invisible-slowdown.
08:21
The ati thin client network card doesn't support mtu higher than default.
08:21
...
08:21
So, ehm...
08:21* Hyperbyte hangs his head in shame
08:22
<Hyperbyte>
Let the ridiculing commence. =)
08:23
<hughessd>
ok
08:23
ok
08:23
ok
08:23
(not with the ridiculing)
08:23
im just relieved. it worked!
08:24
i guess the new ltsp check /var/lib/tftpboot and not /opt/ltsp
08:24
<alkisg>
hughessd: that was the case since at least ubuntu 7.04 :)
08:25
Hyperbyte: thanks for the feedback, I'll know not to mess with MTU in the future :D
08:25
<Hyperbyte>
lol
08:25
At least not for thin clients. ;-)
08:25
<hughessd>
hmmmm.. then htf was my server working before?!?
08:25_UsUrPeR_ has joined #ltsp
08:25
<hughessd>
gah im terrible at my job
08:26
hyperbyte: glad you solved your problem too
08:26
alkisg: thankyouthankyouthankyou
08:26
<alkisg>
(04:28:37 PM) hughessd: gah im terrible at my job ==> don't worry ltsp gets some months to get used to :)
08:26
<hughessd>
alkisg: i hate to just ask you questions and then run off, but it's waaaaaaay past my bed time.
08:27
so i think im going to get going
08:27
<Hyperbyte>
hughessd: you can always come back tomorrow. ;-)
08:27
<alkisg>
G'night
08:27
<hughessd>
ill try to stop in here more often.
08:27
try to pick up some more good tricks.
08:27
thank again for the help.
08:27
be seeing you 'round!
08:27
<Hyperbyte>
Glad you got yours working too. =)
08:27hughessd has quit IRC
08:28
<Hyperbyte>
See, I use a higher MTU for all server<->server traffic because they usually talk big. ;-)
08:29
I adapted a script I use on the servers for some startup stuff...
08:29
Et voila. LTSP screwed. :)
08:39alkisg has quit IRC
08:47bobby_C has quit IRC
09:00bobby_C has joined #ltsp
09:04alexqwesa_ has quit IRC
09:06alexqwesa_ has joined #ltsp
09:42
<Uzzi>
problems with integrate webcam on clients?
09:48alkisg has joined #ltsp
10:02alkisg has quit IRC
10:17komunista has joined #ltsp
10:18Da-Geek has quit IRC
10:27* Kyle__ frowns
10:27
<Kyle__>
I compleetly forgot where I altered my old server to not use nbd-proxy
10:36
Ah foudn it, nevermind.
10:43Uzzi has quit IRC
10:54jhutchins_lt has joined #ltsp
10:56mikkel has joined #ltsp
11:00gavmac has joined #ltsp
11:13alkisg has joined #ltsp
11:31alkisg has quit IRC
11:47ogra_ac has joined #ltsp
11:59mgariepy has joined #ltsp
12:03Lumiere has quit IRC
12:13Lumiere has joined #ltsp
12:17amonthoth has joined #ltsp
12:38ogra_ac has quit IRC
13:19ogra has joined #ltsp
13:24amonthoth has quit IRC
13:30Gadi has joined #ltsp
13:32mistik1 has quit IRC
13:33mistik1 has joined #ltsp
13:45ogra_ac has joined #ltsp
13:45ogra has quit IRC
13:59ogra_ac has quit IRC
14:12Lns has joined #ltsp
14:14ogra_ac has joined #ltsp
14:20jhutchins_lt has quit IRC
14:30
<Ghidorah>
does anyone know how to configure smb printing to use kerberos?
14:33
<buffalosolja>
nope but I can look in my Administrator book right quick to see if I see anything
14:35
just briefly goes over it doesn't tell how to set it up sorry
15:09Gadi has left #ltsp
15:11Ghidorah has quit IRC
15:24ogra_ac has quit IRC
15:24ogra_ac has joined #ltsp
15:29gavmac has quit IRC
15:33mgariepy has quit IRC
15:42alkisg_web has joined #ltsp
15:44jhutchins_lt has joined #ltsp
15:46alkisg_web has quit IRC
15:58Gadi has joined #ltsp
16:15Gadi has quit IRC
16:16F-GT has quit IRC
16:17ogra_ac has quit IRC
16:21alkisg has joined #ltsp
16:32F-GT has joined #ltsp
16:35pmatulis_ has joined #ltsp
16:46mikkel has quit IRC
16:48Lns has quit IRC
16:48
<shamino>
how do i use debconf-seeds option in ltsp-build-client? i am trying to install sun-java6 packages to client-root with debconf seeding so that it auto-accepts the license agreements.
16:51
i have a configuration file for ltsp-build-client which installs extra packages to client-root with late-packages option but java packages doesn't seem to want to install in late-packages because licencse agreement information is missing.
16:53
i am new with debconf preseeding but this is what my seed-file looks like http://ltsp.pastebin.com/SjUvA6RG
16:54hughessd has joined #ltsp
16:55komunista has quit IRC
16:57cliebow_ has joined #ltsp
16:57cliebow has joined #ltsp
16:59
<shamino>
and here's the configuration file for ltsp-build-client http://ltsp.pastebin.com/XnQcM1Tw
17:05
<alkisg>
!fatclients
17:05
<ltspbot`>
alkisg: "fatclients" :: You may find some info about the Ubuntu/LTSP implementation of fat clients at https://help.ubuntu.com/community/UbuntuLTSP/FatClients
17:05
<alkisg>
shamino: see the debconf seeds I put in that wiki page
17:08jhutchins_lt has quit IRC
17:08
<shamino>
ok. thanks!
17:18johnny has left #ltsp
17:31johnny has joined #ltsp
17:39jhutchins_lt has joined #ltsp
17:40bobby_C has quit IRC
17:51alkisg has quit IRC
17:55hughessd has left #ltsp
18:08mgariepy has joined #ltsp
18:20
<cliebow>
mistik1:we'll miss you at bts...
18:32jhutchins_lt has quit IRC
18:35jhutchins_lt has joined #ltsp
18:40staffencasa has quit IRC
19:01jhutchins_lt has quit IRC
19:03chupacabra has quit IRC
19:03chupacabra has joined #ltsp
19:05sweetpi has joined #ltsp
19:05mgariepy has quit IRC
19:13Mobe_ has quit IRC
19:35vagrantc has joined #ltsp
19:39hughessd has joined #ltsp
19:43litlebuda has joined #ltsp
19:53hughessd has quit IRC
20:09M4gic5t0rM has joined #ltsp
20:10litlebuda has quit IRC
20:13M4gic5t0rM has quit IRC
20:14M4gic5t0rM has joined #ltsp
20:32cyberorg has quit IRC
20:39cyberorg has joined #ltsp
21:12cliebow has quit IRC
21:19M4gic5t0rM has quit IRC
21:24vagrantc has quit IRC
21:25M4gic5t0rM has joined #ltsp
21:27vagrantc has joined #ltsp
21:57vagrantc has quit IRC
22:45MorningSon has quit IRC
23:01johnny has left #ltsp
23:25johnny has joined #ltsp