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


Channel log from 7 April 2010   (all times are UTC)

00:07randomuser has joined #ltsp
00:08
<randomuser>
how can i get an idea of a client's local hardware utilization vs server-side hardware utilization?
00:42alkisg has joined #ltsp
01:32alkisg has quit IRC
01:34
<elias_a>
randomuser: Running htop in both?
01:35
Are there good instructions for creating kiosk terminals to a LTSP system?
02:03ogra__ has quit IRC
02:03ogra__ has joined #ltsp
03:00bobby_C has joined #ltsp
03:26Selveste1 has joined #ltsp
03:34zamba has quit IRC
03:40zamba has joined #ltsp
03:46alexqwesa_ has quit IRC
03:48alexqwesa has joined #ltsp
04:59Selveste1 has quit IRC
05:05bobby_C has quit IRC
05:14morfic has quit IRC
05:18morfic has joined #ltsp
05:21morfic has quit IRC
05:21morfic has joined #ltsp
05:27mikkel has joined #ltsp
05:38alkisg has joined #ltsp
06:04Selveste1 has joined #ltsp
06:13hersonls has joined #ltsp
06:18bobby_C has joined #ltsp
06:19ogra__ has quit IRC
06:20ogra__ has joined #ltsp
06:25aliancemd has joined #ltsp
06:26Selveste1 has quit IRC
06:31bobby_C has quit IRC
06:31Selveste1 has joined #ltsp
06:36aliancemd has left #ltsp
06:44scottmaccal has joined #ltsp
06:44Selveste1 has quit IRC
06:50Selveste1 has joined #ltsp
07:02Selveste1 has quit IRC
07:25ogra has quit IRC
07:25ogra has joined #ltsp
07:29mikkel has quit IRC
07:54pmatulis has joined #ltsp
08:14highvoltage has joined #ltsp
08:34alkisg has quit IRC
08:41Gadi has joined #ltsp
08:50alkisg has joined #ltsp
08:53bobby_C has joined #ltsp
09:00
<_UsUrPeR_>
morning all
09:02cliebow has joined #ltsp
09:14johnny has joined #ltsp
09:17
<sbalneav>
Morning all
09:22
<_UsUrPeR_>
!s
09:22
<ltspbot`>
_UsUrPeR_: "s" :: Scotty!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
09:23CAN-o-SPAM has joined #ltsp
09:26sene has joined #ltsp
09:26F-GT has quit IRC
09:28alkisg has quit IRC
09:34
<_UsUrPeR_>
I'm having some issues with LOCALDEV_DENY. entering LOCALDEV_DENY="DEVTYPE:disk" does not do anything. Am I using something incorrectly? I want to disable flash drive mounting on clients, while still keeping functionality of a USB headset.
09:43F-GT has joined #ltsp
09:49
<_UsUrPeR_>
it's strange because "LOCALDEV_DENY_USB = true" works properly. When listing properties with "udevadm info -q env -n /dev/sda" (that points to the USB drive on the client), if comes up with a couple identifying marks, but none of them work to actually block it from mounting.
09:49
Is verbage in the lts.conf correct for LOCALDEV_DENY?
09:59Selveste1 has joined #ltsp
10:03Selveste1 has quit IRC
10:30staffencasa has joined #ltsp
10:47Faithful has quit IRC
11:02Faithful has joined #ltsp
11:43CAN-o-SPAM has quit IRC
11:48
<_UsUrPeR_>
gadi: I have a sound-specific question for you pertaining to alsactl
11:48
<Gadi>
shoot
11:49
<_UsUrPeR_>
I am working with a logitech headset that comes us as "state.Headset" when I save it's config file w/ alsactl store 1 -f /var/asound.state
11:49
So it stores the settings just fine
11:49
<johnny>
hmm.. shouldn't that stuff magically work with pulseaudio ?
11:49
i guess it might on a standard desktop...
11:50
<Gadi>
_UsUrPeR_: so, the channel is named "Headset"?
11:51
<_UsUrPeR_>
gadi: sorry, was distracted
11:52
ok, so right now, I have set up a script to pull the config. It goes in /opt/ltsp/i386/usr/share/ltsp/xinitrc.d
11:52
<Gadi>
sorry, the audio device is named Headset and it has its own controls
11:53
<_UsUrPeR_>
and inside there, it reads as follows: alsactl restore 1 -f /var/lib/alsa/asound.state || true
11:53
<Gadi>
yeah, if it appears as soundcard 1, then the LTSP scripts won't catch it
11:53
<_UsUrPeR_>
D:
11:53
ok
11:53
<Gadi>
we have a "-c 0" passed to amixer
11:54
<_UsUrPeR_>
hmm
11:54
<Gadi>
you will need to do it the way you are doing OR you can just save the asound.state with just the headset info in it to the usual Ubuntu place
11:54
<_UsUrPeR_>
any suggestions? I actually have this working with a plantronics USB headset in "-c 1"
11:55
<Gadi>
_UsUrPeR_: currently, on Ubuntu, there are actually 2 things that set sound
11:56
the distro has an initscript that uses alsactl and is triggered by udev
11:56
then, we have our own amixer commands that are triggered by lts.conf
11:57
most likely, if you see any inconsistencies with custom scripts, it will be due to a race condition with the ubuntu initscript triggered by udev
11:58
the best thing would likely be to leverage the udev-triggered initscript and store the parameters for the headset in the image
11:59
or just continue what you are doing
11:59
and call it upon xinit
12:00
<_UsUrPeR_>
unfortunately, with this particular USB headset from logitech, what I am doing is not working. It works for the plantronics one I have, but not the USB one we're testing.
12:00
so I think I may have to look into udev rules
12:02
<Gadi>
does it work from command line?
12:06
<_UsUrPeR_>
Gadi: it does not seem to recognize the card asound.state is referring to when I attempt to "alsactl restore" the headset manually
12:10ogra__ is now known as ogra_cmpc
12:11
<_UsUrPeR_>
Gadi: check this out. http://pastebin.com/6ZYK5hVA
12:11
is it a naming issue for the headset?
12:12
<Gadi>
root@ltsp103:~# alsactl restore 1 /var/lib/alsa/asount.state
12:12
did you mean asound.state?
12:14
<_UsUrPeR_>
Gadi: actually that is a spelling issue, but the name of the file stands. That's what I have written to the chroot for the moment :)
12:27artista_frustrad has quit IRC
12:37mikeshultz has joined #ltsp
12:40artista_frustrad has joined #ltsp
12:45
<_UsUrPeR_>
gadi: I got it. Missing the -f in that
12:45
alsactl restore 1 -f /var/lib/alsa/asount.state
12:45
OR, if asount.state was spelled correctly, -f would not have been required
12:46_gentgeen_ has joined #ltsp
12:47_gentgeen_ has quit IRC
13:27nubae has joined #ltsp
13:28nubae_ has quit IRC
13:42Selveste1 has joined #ltsp
13:43alkisg has joined #ltsp
13:48nubae_ has joined #ltsp
13:49nubae has quit IRC
13:54Lns has joined #ltsp
14:24scottmaccal has quit IRC
14:27staffencasa has quit IRC
14:37staffencasa has joined #ltsp
14:40mgariepy has joined #ltsp
14:40
<mgariepy>
/join #ubuntu-meetings
14:41
sorry
14:41
<alkisg>
without s in the end :)
14:58
<mgariepy>
thanks alkisg ;) when i saw that it was empty i removed it ;)
14:59pmatulis has quit IRC
15:03sene has quit IRC
15:17staffencasa has quit IRC
15:26staffencasa has joined #ltsp
15:41ogra_cmpc has quit IRC
15:54ogra_cmpc has joined #ltsp
16:02hersonls has quit IRC
16:09mgariepy has quit IRC
16:25gpilotti has quit IRC
16:30Egyptian[Home] has quit IRC
16:44Egyptian[Home] has joined #ltsp
16:57Gadi has left #ltsp
17:09
<alkisg>
sbalneav: ping? (socket related... :))
17:15vagrantc has joined #ltsp
17:17bladernr has joined #ltsp
17:17bobby_C has quit IRC
17:18
<bladernr>
Hey... I have a dumb question... I just installed the LTSP server option in Ubuntu (Lucid) and at the time didn't have the ethernet device configured with static IP
17:18
so I fixed that, but I got a message about having to add my ethernet dev to dhcpd.conf or something... sigh... where do I need to add it?
17:19
<Lns>
bladernr, make sure your ethernet card is activated with the right static IP first.. edit /etc/default/dhcp3-server file to reflect which interface to listen on, and make sure /etc/ltsp/dhcpd3.conf is set up right as well
17:20
in my experience it's best to remove network-manager and dhcp3-client from the server, too
17:20
and even after removing dhcp3-client, you have to manually kill the process otherwise it'll keep trying to override your settings
17:22
<alkisg>
Lns, sudo service networking stop && gedit /etc/network/interfaces && sudo server networking start, should stop dhcp3-client from trying to mess with your addresses - no need to remove it...
17:22
*service
17:23
<bladernr>
hrmm.. ok, so after that, how do I start ltsp (this is the first time I've ever tried, and to be honest, I'm only doing it for Lucid ISO testing
17:23
<alkisg>
bladernr: do you have 2 NICs or just 1?
17:23
<bladernr>
just one
17:24
<alkisg>
You need to put the appropriate ip ranges in /etc/ltsp/dhcp.conf
17:24
Then, sudo service dhcp3-server force-reload
17:24
That should be all...
17:24
Ah, and if you're planning to logon on some thin clients, then you might need to update your ssh keys and your image
17:25
<bladernr>
hrmmm... ok, that file is fine, it's got a range on the 192.168 typical C network...
17:25
<alkisg>
(that's needed every time the server ip changes)
17:27
<bladernr>
alkisg: ok... cool... though dhcp3-server isn't starting... do I need a line in dhcp3/dhcpd.conf to load the LTSP dhcpd.conf file?
17:27
<alkisg>
bladernr: if dhcp3-server isn't starting, there's something wrong with dhcpd.conf
17:28
Can you upload it to pastebin, along with your ip?
17:28
<bladernr>
the problem is that /etc/dhcp3/dhcpd.conf does not have any ranges added. They exist in /etc/ltsp/dhcpd.conf, but starting dhcp3 seems to not be reading the correct dhcpd file for ltsp
17:29
<alkisg>
How did you install dhcp3-server?
17:29
As an ltsp dependency?
17:29
<bladernr>
heh... no idea... it's the default installation in Ubuntu 10.04 when you choose the LTSP Server option during install
17:29
<mikeshultz>
Can an amd64 ltsp server serve to 32-bit machines?
17:29* bladernr is a QA guy at canonical and is testing Lucid right now
17:30
<alkisg>
bladernr: ok, then you shouldn't have this problem, /etc/dhcp3 shouldn't be used at all by default
17:30
Can you see any error messages in syslog or daemon.log?
17:30
<bladernr>
right, that's what I was wondeirng... let me pastebin the ltsp one... though it's the default one that comes with the Ubuntu packages
17:30
yeah, it's complaining about not having any ranges assigned (e.g., it's reading the wrong dhcpd.conf file)
17:31
<alkisg>
Hrm...
17:31
stgraber, any clues? ^^^
17:31
<johnny>
make sure the right file is getting sourced..
17:31
read the init script
17:31
make sure it's sourcing the ltsp one at the top
17:31
<Lns>
I know this is the case in debian if you manually install ltsp-server-standalone..you either have to manually add an 'include' stanza in /etc/dhcp3/dhcpd.conf or manually symlink /etc/ltsp/dhcpd.conf to /etc/dhcp3
17:32
but on ubuntu i hadn't had to worry about that for some time
17:32* alkisg is on Lucid but doesn't use dhcp3-server - he uses dnsmasq....
17:33
<bladernr>
hrmmm.... Lns that's what I was missing...
17:33
<alkisg>
bladernr: did dhcp3-server got upstartified?
17:34
<johnny>
it hsould be sourcing the ltsp dhcpd file if it exists bladernr
17:35
<bladernr>
it's not... and I think I've got other problems anyway... the system can't get to the internet either... plus all this mess. And I'm hungry (should have waited till after dinner to get into this one)
17:36
<alkisg>
Uh
17:36
<bladernr>
Tell ya what, I'm gonna go for now, and then flatten and redo the install just in case I messed something up
17:36
<Lns>
bladernr, multiple re-installs always helps iron out the inconsistencies with first time installs =)
17:36
<mikeshultz>
I'd just like to know before I start putting in work... Can an amd64 ltsp server serve to 32-bit machines? Is there special config?
17:36
<bladernr>
Lns: indeed it does
17:36
<alkisg>
mikeshultz: yes it can but you need a 32bit chroot
17:36
<bladernr>
so after I try again, I'll come back and let y'all know what happened... now its dinner time.
17:36
<alkisg>
ltsp-build-client --arch=i386 or something like that
17:36
<mikeshultz>
alkisg: thank you.
17:37
<alkisg>
yw
17:37
<Lns>
cool
17:38alkisg has quit IRC
17:49shamino has quit IRC
17:56Lns has quit IRC
18:07mikeshultz has quit IRC
18:22nubae has joined #ltsp
18:22shamino has joined #ltsp
18:23nubae_ has quit IRC
18:48staffencasa has quit IRC
19:18roy_hobbs has joined #ltsp
19:20
<roy_hobbs>
Is this document http://sourceforge.net/projects/ltsp/files/Docs-Admin-Guide/LTSPManual.pdf/download updated for LTSP 5?
19:20
<vagrantc>
!docs
19:20
<ltspbot`>
vagrantc: "docs" :: For the most current documentation, see https://sourceforge.net/apps/mediawiki/ltsp/index.php?title=Ltsp_LtspDocumentationUpstream
19:21
<roy_hobbs>
Yeah, that's where I got the link from. That doesn't quite answer my question though because there seems to be major changes in LTSP5, but a lot of info about 4 is still around.
19:22
<vagrantc>
well, a lot of information is still relevent
19:23
<roy_hobbs>
Ok, but does this document describe xdmcp/gdm/tarball/nfs or ssh/LDM/native/nbd...
19:24
My distribution is without LTSP support and I want to have a go at it.
19:25
<vagrantc>
what distro?
19:25
<roy_hobbs>
Arch
19:27
I'm willing to invest time and money into this (I want to buy a new desktop and a handful of thin-clients) but my first impressions of ltsp are that it all seems quite fragmented.
19:27
<vagrantc>
the source code for ltsp and ldm is: https://code.launchpad.net/~ltsp-upstream
19:28
and ltspfs...
19:29
ltsp5 builds the ltsp environment out of the host distro's packages, so the bulk of the work is significantly different for each distro
19:29
there are only a few actual binaries/scripts that are ltsp specific
19:30
<roy_hobbs>
Is this guide all I need to know to fully understand what LTSP actually is and how I can set it up for any distro?
19:31
<vagrantc>
i wrote a wiki page a long time ago that documented the basic process for setting it up for your distro...
19:31
don't know if that made it to the new wiki after the great wiki crash of 09
19:32
<roy_hobbs>
long time ago meaning pre-5 mentality?
19:32
<vagrantc>
the muekow -> ltsp5 transition phase, probably
19:34
the basic jist is make an ltsp-server package from ltsp-trunk/server/ltsp-build-client and the plugins in ltsp-trunk/server/plugins/ltsp-build-client/$DISTRO
19:34
ltsp-build-client should build a basic chroot and install the ltsp-client/ldm/ltspfsd packages.
19:35
so you'll need to build ltsp-client, ldm and ltspfsd packages...
19:35
and install them in the chroot...
19:36
ldm and ltspfs should pretty much build with autotools, but ltsp-client needs to be assembled from ltsp-trunk/client bits...
19:37
what's arch like, anyways?
19:38
i.e. based on rpm, deb or something else?
19:38
<roy_hobbs>
Sorry, I was trying to nav through launchpad following the paths you gave me
19:38
I love arch
19:38
packaging are just tar.gz which contain the files for a particular package and some minor metadata
19:39
packaging is*
19:39
the installer basically unpacks the package onto / and runs and options post-install script
19:40
<vagrantc>
so you'll just need to run an installer that installs into a chroot rather than / somehow...
19:40
<roy_hobbs>
yes, there's an install path option which defaults to /
19:42
is it generally a bad idea to bind /usr and /bin into the ltsp chroot?
19:42
nvm
19:43
<vagrantc>
you looes the ability to really do any sort of package management, then...
19:45
i think it's really a good idea to see the LTSP chroot environment as essentially an entire OS of it's own...
19:45
well, a particular instance of an OS, that is...
19:46
<roy_hobbs>
ok, we'll i'll read through this PDF first before I do anything else
19:47
well*
19:48
<vagrantc>
that manual is a little out of date, but not much.
19:49
it's definitely ltsp5, though.
19:50
<roy_hobbs>
yeah i searched for things like NBD
19:50
<vagrantc>
fairly trivial changes since then
19:50
<roy_hobbs>
Just out of curiosity, what is the relationship with disklessworkstations.com? as opposed to any other thin client provider?
19:51
<vagrantc>
disklessworkstations.com was started by the founder(s) of LTSP ... so they've definitely been supportive of LTSP over the years.
19:52
<roy_hobbs>
Are they just hardware or do they come with any particular software that's not part of the ltsp - I'd like to at least try and use and old POS box as a 'thin' client for testing
19:54
<vagrantc>
some of them are genuine thin clients and just network boot whatever the network tells them ... but some might have a little OS on them.. not sure.
19:54
<roy_hobbs>
but all i need is a bios that supports PXE?
19:55
<vagrantc>
yeah
19:55
well, network card more than bios
19:55
but yeah.
19:56
<roy_hobbs>
great
19:56
thanks for push
20:05pmatulis has joined #ltsp
20:23pmatulis has quit IRC
21:43vagrantc has quit IRC
21:44roy_hobbs has quit IRC
22:36vagrantc has joined #ltsp
22:57daya has joined #ltsp
23:24bladernr has quit IRC
23:31daya has quit IRC
23:32daya has joined #ltsp