|00:07||randomuser has joined #ltsp|
how can i get an idea of a client's local hardware utilization vs server-side hardware utilization?
|00:42||alkisg has joined #ltsp|
|01:32||alkisg has quit IRC|
randomuser: Running htop in both?
Are there good instructions for creating kiosk terminals to a LTSP system?
|02:03||ogra__ has quit IRC|
|02:03||ogra__ has joined #ltsp|
|03:00||bobby_C has joined #ltsp|
|03:26||Selveste1 has joined #ltsp|
|03:34||zamba has quit IRC|
|03:40||zamba has joined #ltsp|
|03:46||alexqwesa_ has quit IRC|
|03:48||alexqwesa has joined #ltsp|
|04:59||Selveste1 has quit IRC|
|05:05||bobby_C has quit IRC|
|05:14||morfic has quit IRC|
|05:18||morfic has joined #ltsp|
|05:21||morfic has quit IRC|
|05:21||morfic has joined #ltsp|
|05:27||mikkel has joined #ltsp|
|05:38||alkisg has joined #ltsp|
|06:04||Selveste1 has joined #ltsp|
|06:13||hersonls has joined #ltsp|
|06:18||bobby_C has joined #ltsp|
|06:19||ogra__ has quit IRC|
|06:20||ogra__ has joined #ltsp|
|06:25||aliancemd has joined #ltsp|
|06:26||Selveste1 has quit IRC|
|06:31||bobby_C has quit IRC|
|06:31||Selveste1 has joined #ltsp|
|06:36||aliancemd has left #ltsp|
|06:44||scottmaccal has joined #ltsp|
|06:44||Selveste1 has quit IRC|
|06:50||Selveste1 has joined #ltsp|
|07:02||Selveste1 has quit IRC|
|07:25||ogra has quit IRC|
|07:25||ogra has joined #ltsp|
|07:29||mikkel has quit IRC|
|07:54||pmatulis has joined #ltsp|
|08:14||highvoltage has joined #ltsp|
|08:34||alkisg has quit IRC|
|08:41||Gadi has joined #ltsp|
|08:50||alkisg has joined #ltsp|
|08:53||bobby_C has joined #ltsp|
|09:02||cliebow has joined #ltsp|
|09:14||johnny has joined #ltsp|
_UsUrPeR_: "s" :: Scotty!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
|09:23||CAN-o-SPAM has joined #ltsp|
|09:26||sene has joined #ltsp|
|09:26||F-GT has quit IRC|
|09:28||alkisg has quit IRC|
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:43||F-GT has joined #ltsp|
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.
Is verbage in the lts.conf correct for LOCALDEV_DENY?
|09:59||Selveste1 has joined #ltsp|
|10:03||Selveste1 has quit IRC|
|10:30||staffencasa has joined #ltsp|
|10:47||Faithful has quit IRC|
|11:02||Faithful has joined #ltsp|
|11:43||CAN-o-SPAM has quit IRC|
gadi: I have a sound-specific question for you pertaining to alsactl
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
So it stores the settings just fine
hmm.. shouldn't that stuff magically work with pulseaudio ?
i guess it might on a standard desktop...
_UsUrPeR_: so, the channel is named "Headset"?
gadi: sorry, was distracted
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
sorry, the audio device is named Headset and it has its own controls
and inside there, it reads as follows: alsactl restore 1 -f /var/lib/alsa/asound.state || true
yeah, if it appears as soundcard 1, then the LTSP scripts won't catch it
we have a "-c 0" passed to amixer
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
any suggestions? I actually have this working with a plantronics USB headset in "-c 1"
_UsUrPeR_: currently, on Ubuntu, there are actually 2 things that set sound
the distro has an initscript that uses alsactl and is triggered by udev
then, we have our own amixer commands that are triggered by lts.conf
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
the best thing would likely be to leverage the udev-triggered initscript and store the parameters for the headset in the image
or just continue what you are doing
and call it upon xinit
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.
so I think I may have to look into udev rules
does it work from command line?
Gadi: it does not seem to recognize the card asound.state is referring to when I attempt to "alsactl restore" the headset manually
|12:10||ogra__ is now known as ogra_cmpc|
Gadi: check this out. http://pastebin.com/6ZYK5hVA
is it a naming issue for the headset?
root@ltsp103:~# alsactl restore 1 /var/lib/alsa/asount.state
did you mean asound.state?
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:27||artista_frustrad has quit IRC|
|12:37||mikeshultz has joined #ltsp|
|12:40||artista_frustrad has joined #ltsp|
gadi: I got it. Missing the -f in that
alsactl restore 1 -f /var/lib/alsa/asount.state
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:27||nubae has joined #ltsp|
|13:28||nubae_ has quit IRC|
|13:42||Selveste1 has joined #ltsp|
|13:43||alkisg has joined #ltsp|
|13:48||nubae_ has joined #ltsp|
|13:49||nubae has quit IRC|
|13:54||Lns has joined #ltsp|
|14:24||scottmaccal has quit IRC|
|14:27||staffencasa has quit IRC|
|14:37||staffencasa has joined #ltsp|
|14:40||mgariepy has joined #ltsp|
without s in the end :)
thanks alkisg ;) when i saw that it was empty i removed it ;)
|14:59||pmatulis has quit IRC|
|15:03||sene has quit IRC|
|15:17||staffencasa has quit IRC|
|15:26||staffencasa has joined #ltsp|
|15:41||ogra_cmpc has quit IRC|
|15:54||ogra_cmpc has joined #ltsp|
|16:02||hersonls has quit IRC|
|16:09||mgariepy has quit IRC|
|16:25||gpilotti has quit IRC|
|16:30||Egyptian[Home] has quit IRC|
|16:44||Egyptian[Home] has joined #ltsp|
|16:57||Gadi has left #ltsp|
sbalneav: ping? (socket related... :))
|17:15||vagrantc has joined #ltsp|
|17:17||bladernr has joined #ltsp|
|17:17||bobby_C has quit IRC|
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
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?
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
in my experience it's best to remove network-manager and dhcp3-client from the server, too
and even after removing dhcp3-client, you have to manually kill the process otherwise it'll keep trying to override your settings
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...
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
bladernr: do you have 2 NICs or just 1?
You need to put the appropriate ip ranges in /etc/ltsp/dhcp.conf
Then, sudo service dhcp3-server force-reload
That should be all...
Ah, and if you're planning to logon on some thin clients, then you might need to update your ssh keys and your image
hrmmm... ok, that file is fine, it's got a range on the 192.168 typical C network...
(that's needed every time the server ip changes)
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?
bladernr: if dhcp3-server isn't starting, there's something wrong with dhcpd.conf
Can you upload it to pastebin, along with your ip?
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
How did you install dhcp3-server?
As an ltsp dependency?
heh... no idea... it's the default installation in Ubuntu 10.04 when you choose the LTSP Server option during install
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|
bladernr: ok, then you shouldn't have this problem, /etc/dhcp3 shouldn't be used at all by default
Can you see any error messages in syslog or daemon.log?
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
yeah, it's complaining about not having any ranges assigned (e.g., it's reading the wrong dhcpd.conf file)
stgraber, any clues? ^^^
make sure the right file is getting sourced..
read the init script
make sure it's sourcing the ltsp one at the top
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
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....|
hrmmm.... Lns that's what I was missing...
bladernr: did dhcp3-server got upstartified?
it hsould be sourcing the ltsp dhcpd file if it exists 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)
Tell ya what, I'm gonna go for now, and then flatten and redo the install just in case I messed something up
bladernr, multiple re-installs always helps iron out the inconsistencies with first time installs =)
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?
Lns: indeed it does
mikeshultz: yes it can but you need a 32bit chroot
so after I try again, I'll come back and let y'all know what happened... now its dinner time.
ltsp-build-client --arch=i386 or something like that
alkisg: thank you.
|17:38||alkisg has quit IRC|
|17:49||shamino has quit IRC|
|17:56||Lns has quit IRC|
|18:07||mikeshultz has quit IRC|
|18:22||nubae has joined #ltsp|
|18:22||shamino has joined #ltsp|
|18:23||nubae_ has quit IRC|
|18:48||staffencasa has quit IRC|
|19:18||roy_hobbs has joined #ltsp|
Is this document http://sourceforge.net/projects/ltsp/files/Docs-Admin-Guide/LTSPManual.pdf/download updated for LTSP 5?
vagrantc: "docs" :: For the most current documentation, see https://sourceforge.net/apps/mediawiki/ltsp/index.php?title=Ltsp_LtspDocumentationUpstream
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.
well, a lot of information is still relevent
Ok, but does this document describe xdmcp/gdm/tarball/nfs or ssh/LDM/native/nbd...
My distribution is without LTSP support and I want to have a go at it.
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.
the source code for ltsp and ldm is: https://code.launchpad.net/~ltsp-upstream
ltsp5 builds the ltsp environment out of the host distro's packages, so the bulk of the work is significantly different for each distro
there are only a few actual binaries/scripts that are ltsp specific
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?
i wrote a wiki page a long time ago that documented the basic process for setting it up for your distro...
don't know if that made it to the new wiki after the great wiki crash of 09
long time ago meaning pre-5 mentality?
the muekow -> ltsp5 transition phase, probably
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
ltsp-build-client should build a basic chroot and install the ltsp-client/ldm/ltspfsd packages.
so you'll need to build ltsp-client, ldm and ltspfsd packages...
and install them in the chroot...
ldm and ltspfs should pretty much build with autotools, but ltsp-client needs to be assembled from ltsp-trunk/client bits...
what's arch like, anyways?
i.e. based on rpm, deb or something else?
Sorry, I was trying to nav through launchpad following the paths you gave me
I love arch
packaging are just tar.gz which contain the files for a particular package and some minor metadata
the installer basically unpacks the package onto / and runs and options post-install script
so you'll just need to run an installer that installs into a chroot rather than / somehow...
yes, there's an install path option which defaults to /
is it generally a bad idea to bind /usr and /bin into the ltsp chroot?
you looes the ability to really do any sort of package management, then...
i think it's really a good idea to see the LTSP chroot environment as essentially an entire OS of it's own...
well, a particular instance of an OS, that is...
ok, we'll i'll read through this PDF first before I do anything else
that manual is a little out of date, but not much.
it's definitely ltsp5, though.
yeah i searched for things like NBD
fairly trivial changes since then
Just out of curiosity, what is the relationship with disklessworkstations.com? as opposed to any other thin client provider?
disklessworkstations.com was started by the founder(s) of LTSP ... so they've definitely been supportive of LTSP over the years.
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
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.
but all i need is a bios that supports PXE?
well, network card more than bios
thanks for push
|20:05||pmatulis has joined #ltsp|
|20:23||pmatulis has quit IRC|
|21:43||vagrantc has quit IRC|
|21:44||roy_hobbs has quit IRC|
|22:36||vagrantc has joined #ltsp|
|22:57||daya has joined #ltsp|
|23:24||bladernr has quit IRC|
|23:31||daya has quit IRC|
|23:32||daya has joined #ltsp|