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


Channel log from 24 April 2014   (all times are UTC)

00:33gbaman has left IRC (gbaman!~gbaman@host81-134-104-240.in-addr.btopenworld.com, Remote host closed the connection)
01:04gbaman has joined IRC (gbaman!~gbaman@host81-134-104-240.in-addr.btopenworld.com)
01:04gdi2k has joined IRC (gdi2k!~gdi2k@222.127.60.203)
01:05
<gdi2k>
hi all, is there a simple screen lock application that works with ltsp? xscreensaver doesn't work (can't log back in as local auth doesn't work). any workarounds that don't involve ldap etc.?
01:06
<vagrantc>
run it as a remote app on the server.
01:07
then you'll be able to authenticate.
01:07
xscreensaver works fine on thin clients, for example, just not fat clients, because fat clients have no real pam authentication...
01:08
if you wre adventurous, you could try hooking it into libpam-sshauth...
01:11gbaman has left IRC (gbaman!~gbaman@host81-134-104-240.in-addr.btopenworld.com, Ping timeout: 252 seconds)
01:14work_alkisg has left IRC (work_alkisg!~alkisg@plinet.ioa.sch.gr, Ping timeout: 265 seconds)
01:46gbaman has joined IRC (gbaman!~gbaman@host81-134-104-240.in-addr.btopenworld.com)
01:51gbaman has left IRC (gbaman!~gbaman@host81-134-104-240.in-addr.btopenworld.com, Ping timeout: 265 seconds)
02:03FrozenZia has left IRC (FrozenZia!pbrown@evo.paivola.fi, Ping timeout: 250 seconds)
02:04FrozenZia has joined IRC (FrozenZia!pbrown@evo.paivola.fi)
02:16Sean_ has joined IRC (Sean_!43dbe3f5@gateway/web/freenode/ip.67.219.227.245)
02:16
<Sean_>
Hello ANyone around?
02:20
Anyway, I am researching whether or not it is possible to "link" a particular thin-client image to a user account or group of users.. So that I can set a particular thin-client image to particular users?
02:44
<vagrantc>
yes, LDM_USER in lts.conf
02:44
!lts.conf
02:44
<ltsp>
lts.conf: http://manpages.ubuntu.com/lts.conf
02:44
<vagrantc>
Sean_: ^^
03:10
<Sean_>
Oh hey thanks guys that is what I am messing with currently
03:27
Is there a place I can find all the possible commands related to lts.conf ? I have seen everything from User specific declarations to hardware specific declarations... is there any where someone may have posted a list of all possible declarations for use within the lts.conf file?
03:27
Nevermind
03:28
I got distracted before scrolling down.. lol
03:28
<vagrantc>
heh.
03:28
it's not perfect ... some commands are missing, but anything missing should be added.
03:28
er, some variables are missing
03:38
<Sean_>
It still does a very good job of displaying how crucial its use can be..
03:39
for user configuration purposes
03:41
My goal is to have two different 64-bit images, one more useful for standard users, and one more useful for say, computer nerds.. like myself , lots of programming tools, different browsers.. blah blah blah
03:43
and to create a standard user group, and of course a advanced user group, then possibly use lts.conf too boot the image for the particular group
03:43
<vagrantc>
lts.conf won't allow you to select which image gets booted
03:43
but you can log into a different server
03:44
<Sean_>
so say 2X ltsp servers?
03:44
one for each of the 2 groups?
03:45
<vagrantc>
if you only want some programs available to one set of users... all users usually have access to all the installed programs ...
03:46
although you could hide a lot of things with custom menus, but they'd still be able to get at all the other stuff if they wanted
03:46
<Sean_>
hmm.. food for thought
03:47
<vagrantc>
you could have some machines run as fat clients, and some as thin clients, and have different sets of software available that way...
03:47
<Sean_>
via local-apps
03:47
<vagrantc>
fat clients are roughly equivalent to running everything as local apps
03:47
<Sean_>
yeah
03:48
cept the os
03:48
<vagrantc>
not to be confused with local apps, which are typically only used on thin clients
03:48
what do you mean by os?
03:48
all the clients are running an OS, as well as the server...
03:48gbaman has joined IRC (gbaman!~gbaman@host81-134-104-240.in-addr.btopenworld.com)
03:49
<Sean_>
running everything as local apps besides the os
03:50
I guess the thin-client is actually booting a pxe
03:50
it's just not using a HD
03:51
so, fat-client more or less equals hard-disk usage..
03:51
on the client-side
03:51
where thin is using no HD
03:52
<vagrantc>
yes, no hard drive, still has an OS
03:53
but there's no difference there between thin and fat clients, at least in LTSP terminology.
03:53gbaman has left IRC (gbaman!~gbaman@host81-134-104-240.in-addr.btopenworld.com, Ping timeout: 276 seconds)
03:53
<Sean_>
yes, I have gathered this..
03:55
it is a very exciting avenue ..
03:56
The OS you talk of on the thin-client side is a confusing monster to me..
03:56
the thin-client uses an image on the ltsp server
03:57
are you speaking of what handles the PXE boot
03:59
OS meaning you basic input outpt?
04:16Sean_ has left IRC (Sean_!43dbe3f5@gateway/web/freenode/ip.67.219.227.245, Quit: Page closed)
04:46freedomrun has joined IRC (freedomrun!~freedomru@unaffiliated/freedomrun)
04:49gbaman has joined IRC (gbaman!~gbaman@host81-134-104-240.in-addr.btopenworld.com)
04:54gbaman has left IRC (gbaman!~gbaman@host81-134-104-240.in-addr.btopenworld.com, Ping timeout: 252 seconds)
05:12freedomrun has left IRC (freedomrun!~freedomru@unaffiliated/freedomrun, Ping timeout: 252 seconds)
05:25freedomrun has joined IRC (freedomrun!~freedomru@unaffiliated/freedomrun)
05:35work_alkisg has joined IRC (work_alkisg!~alkisg@plinet.ioa.sch.gr)
05:50gbaman has joined IRC (gbaman!~gbaman@host81-134-104-240.in-addr.btopenworld.com)
05:54gbaman has left IRC (gbaman!~gbaman@host81-134-104-240.in-addr.btopenworld.com, Ping timeout: 240 seconds)
06:17flo1546796 has joined IRC (flo1546796!~flo154679@2001:660:5001:156:26be:5ff:fe13:f2db)
06:17flo1546796 has joined IRC (flo1546796!~flo154679@unaffiliated/flo1546796)
06:51gbaman has joined IRC (gbaman!~gbaman@host81-134-104-240.in-addr.btopenworld.com)
06:55vagrantc has left IRC (vagrantc!~vagrant@freegeek/vagrantc, Quit: leaving)
06:56gbaman has left IRC (gbaman!~gbaman@host81-134-104-240.in-addr.btopenworld.com, Ping timeout: 276 seconds)
07:22flo1546796 has left IRC (flo1546796!~flo154679@unaffiliated/flo1546796, Remote host closed the connection)
07:52gbaman has joined IRC (gbaman!~gbaman@host81-134-104-240.in-addr.btopenworld.com)
07:56gbaman has left IRC (gbaman!~gbaman@host81-134-104-240.in-addr.btopenworld.com, Ping timeout: 240 seconds)
08:01bennabiy has left IRC (bennabiy!~Thunderbi@96-37-209-0.dhcp.leds.al.charter.com, Read error: Connection reset by peer)
08:04bennabiy has joined IRC (bennabiy!~Thunderbi@96-37-209-0.dhcp.leds.al.charter.com)
08:15mealstrom has joined IRC (mealstrom!~Thunderbi@46.63.71.254)
08:17freedomrun has left IRC (freedomrun!~freedomru@unaffiliated/freedomrun, Quit: So long and thanks for all the fish.)
08:40lns has left IRC (lns!~lns@pdpc/supporter/professional/lns, Ping timeout: 252 seconds)
08:53gbaman has joined IRC (gbaman!~gbaman@host81-134-104-240.in-addr.btopenworld.com)
08:58gbaman has left IRC (gbaman!~gbaman@host81-134-104-240.in-addr.btopenworld.com, Ping timeout: 255 seconds)
09:25gbaman has joined IRC (gbaman!~gbaman@host81-134-104-240.in-addr.btopenworld.com)
09:50flo1546796 has joined IRC (flo1546796!~flo154679@2001:660:5001:156:b150:cbeb:9dcd:947a)
09:50flo1546796 has joined IRC (flo1546796!~flo154679@unaffiliated/flo1546796)
09:52work_alkisg is now known as alkisg
10:18
<wouter>
Zaphoid: what version of nbd-server?
10:20
ah, nvm
10:20* wouter reads more of backlog
10:20
<wouter>
alkisg: so, if you want, I do have time now :)
10:21
(re: #656258: I'm thinking of dropping support for inetd mode entirely. I have little way of testing it, and stdout really should be for messages)
10:21
<alkisg>
Hi wouter, please give me a few minutes to finish some conversation in #ibus... :-/
10:21
<wouter>
sure :)
10:21lns has joined IRC (lns!~lns@pdpc/supporter/professional/lns)
10:21ogra_ has left IRC (ogra_!~ogra_@p5098ed03.dip0.t-ipconnect.de, Ping timeout: 240 seconds)
10:23ogra_ has joined IRC (ogra_!~ogra_@p5098ed03.dip0.t-ipconnect.de)
10:36bobka has joined IRC (bobka!c22c5d21@gateway/web/freenode/ip.194.44.93.33)
10:45khildin has joined IRC (khildin!~khildin@ip-213-49-85-69.dsl.scarlet.be)
10:58
<Hyperbyte>
"A few minutes" 'eh.
10:58
Next thing you know; you're waiting half an hour!
10:58
<alkisg>
Haha
10:59
Keyboard layout handling is increasingly becoming a nightmare
10:59
We had xkb, and it worked fine for *ages*
10:59
<ogra_>
isnt xkb dead since 12.04 already ?
10:59
<alkisg>
Now we have accountsservice, ubiquity, lightdm, gnome-settings-daemon, unity-settings-daemon, and ibus, that all try to offer a ...better layout switching experience
10:59
<ogra_>
or even earlier
11:00
<alkisg>
And they all just break the layout swithing
11:00
<ogra_>
not for chinese users :P
11:00
<alkisg>
Why oh why do distros accept code that breaks things that already work...
11:00
<ogra_>
just switch your country to chinese and you'll be fine :P
11:00
<alkisg>
Haha
11:01
<ogra_>
(i think many of the 14.04 changes were actually driven by the kylin folks)
11:01
<alkisg>
And ibus is now a hard dependency of ubuntu-desktop... finding workarounds for all that mess is a nightmare
11:03
(not to mention that all these just add a 100 MB RAM per user requirement on LTSP servers, and all they do is break things that already worked... and we can't even remove them without removing ubuntu... :()
11:04
If mint works out of the box, we'll switch to it, completely ignoring any security concerns :D
11:10
<ogra_>
well, assuming your network is firewalled that wouldnt be much of a concern
11:11
possible random breakages because they unconditionally patch libs without bumping the ABI etc would worry me more with mint
11:12
(and nobody who fixes your bugs due to that ... we ignore them in launchpad)
11:16* ogra_ thinks someone should just start an ubuntu mate spinoff using official packages instead
11:19
<ogra_>
(or mint should simply finally start to rebuild the binaries against their patched libs (having a patched libc ot libgtk that has different symbols but the rest of the binaries dont know about it because they just get imported from ubuntu without rebuild is really gross)... use their own bugtracker etc)
11:26alkisg is now known as work_alkisg
11:59Phantomas has joined IRC (Phantomas!~Phantomas@ubuntu/member/phantomas)
12:11telex has left IRC (telex!~telex@freeshell.de, Remote host closed the connection)
12:12telex has joined IRC (telex!~telex@freeshell.de)
12:34
<Zaphoid>
wouter: Thanks for reaching out in the middle of the night. Should probably change my name when I'm asleep.
13:11tregnas has joined IRC (tregnas!5d999d2a@gateway/web/freenode/ip.93.153.157.42)
13:11
<||cw>
please don't. just set the away flag. http://freenode.net/poundfreenode.shtml#considerate
13:12tregnas has left IRC (tregnas!5d999d2a@gateway/web/freenode/ip.93.153.157.42, Client Quit)
13:12
<Zaphoid>
||cw: Ok, I'll remember that, too
13:13tregnas has joined IRC (tregnas!5d999d2a@gateway/web/freenode/ip.93.153.157.42)
13:13
<tregnas>
hi
13:13
<Zaphoid>
||cw: I'm digging into the issues more this morning, and I'm noticing during every boot, the LTSP client attempts to mount a nbd9 (as opposed to nbd0 for root partition). THis always fails.
13:13
<tregnas>
i need a little help
13:13
<Zaphoid>
I do not have nbd swap enabled.
13:14
So I'm not sure what this second mount is supposed to be.
13:14
Do you have any thoughts on this?
13:14Ark74 has joined IRC (Ark74!~Ark74@189.214.42.128.cable.dyn.cableonline.com.mx)
13:20
<tregnas>
I've got two thin clients and LTSP-server based on Ubuntu 12.04 LTS 64x. Also I've got the script, that wake clients, when I need it. But after power outage (I mean at all), Wake-On-LAN function doesn't work. I supposed to turn on and off my clients manually. I need to fix this
13:21
<Zaphoid>
tregnas: What hardware are you using for the thin clients?
13:23
tregnas: And the WOL failure after power failures isn't typically a LTSP issue, but a more general hardware issue.
13:24
<tregnas>
Intel® Core™ i5-3570K CPU @ 3.40GHz × 4 , 16 GB OM, 1TB HDD
13:24
it's for derver
13:25
and for thin clients i've got http://www.tonk.ru/catalog/products/tonkie_klienty_tonk_1500_serii/tonk_1502/
13:25
*server
13:25
<Ark74>
where can i see more about the WOL on ltsp?
13:26
<tregnas>
here https://help.ubuntu.com/community/UbuntuLTSP/AutomatedTCStartup
13:27jhon has joined IRC (jhon!7a3e10cb@gateway/web/freenode/ip.122.62.16.203)
13:27
<Ark74>
thanks
13:27flo1546796 has left IRC (flo1546796!~flo154679@unaffiliated/flo1546796, Ping timeout: 245 seconds)
13:29
<tregnas>
i don't know what to do
13:29flo1546796 has joined IRC (flo1546796!~flo154679@unaffiliated/flo1546796)
13:31tregnas has left IRC (tregnas!5d999d2a@gateway/web/freenode/ip.93.153.157.42, Quit: Page closed)
13:32
<jhon>
I have setup Samba4 server on Ubuntu 12.04 LTS.
13:32
<wouter>
Zaphoid: middle of the night? joker
13:32
<jhon>
On the same host I am running LTSP serve
13:32
<wouter>
15:31 right now :)
13:33
<jhon>
lol
13:33
I am trying to use samba4 user with LTSP thin client
13:33
<Zaphoid>
wouter: Well you goofy Europeans and your goofy not being at the same time as us sensible eastern Americans :P
13:33
<wouter>
Zaphoid: I could say the same thing ;)
13:34
with just a few small word substitutions
13:34
<Zaphoid>
And that is what makes the world go round.
13:34
<jhon>
wow
13:34
<workingcats>
Zaphoid, nah, gravity does that ;)
13:35
<wouter>
workingcats: gravity has nothing to do with it, inertia does
13:35
<workingcats>
wouter, was hoping nobody would notice -.-
13:35
<Zaphoid>
I suppose degrading into a fluid mechanics discussion is better then other directions this could degrade into.
13:35
<wouter>
workingcats: too bad :)
13:35
<workingcats>
isnt it inertia+gravity?
13:36
<wouter>
workingcats: depends on your interpretation of "round"
13:36
<workingcats>
i mean inertia would make as just go in a straight line. sun's gravity turns that into a circle
13:36
<wouter>
if you mean the daily rotation, it's inertia
13:36
if you mean the yearly rotation, it's gravity
13:36
<workingcats>
true
13:37flo1546796 has left IRC (flo1546796!~flo154679@unaffiliated/flo1546796, Ping timeout: 245 seconds)
13:38
<wouter>
of course, business men would like you to believe it's money, but hey
13:38
<Zaphoid>
Well, anyrate.
13:39
wouter: did you have any dazzling thoughts on my predicament last night?
13:40
Or this morning.
13:40flo1546796 has joined IRC (flo1546796!~flo154679@unaffiliated/flo1546796)
13:43jhon has left IRC (jhon!7a3e10cb@gateway/web/freenode/ip.122.62.16.203, Quit: Page closed)
13:48flo1546796 has left IRC (flo1546796!~flo154679@unaffiliated/flo1546796, Ping timeout: 245 seconds)
13:51flo1546796 has joined IRC (flo1546796!~flo154679@unaffiliated/flo1546796)
13:52monkwitdafunk has joined IRC (monkwitdafunk!~AndChat49@24.114.37.3)
13:58flo1546796 has left IRC (flo1546796!~flo154679@unaffiliated/flo1546796, Ping timeout: 245 seconds)
14:01flo1546796 has joined IRC (flo1546796!~flo154679@unaffiliated/flo1546796)
14:05
<wouter>
Zaphoid: was your nbd-server restarted when you got that error message?
14:05
Zaphoid: if so, that's expected. If not, it would be a bug that I'm not aware of
14:06Phantomas has left IRC (Phantomas!~Phantomas@ubuntu/member/phantomas, Quit: Leaving.)
14:08flo1546796 has left IRC (flo1546796!~flo154679@unaffiliated/flo1546796, Ping timeout: 245 seconds)
14:10Rainer_ has joined IRC (Rainer_!50be8d32@gateway/web/freenode/ip.80.190.141.50)
14:10
<Rainer_>
Hi
14:10
I have a problem with a kiosk installation
14:11flo1546796 has joined IRC (flo1546796!~flo154679@unaffiliated/flo1546796)
14:11
<Rainer_>
interestingly only after upgrading from squeeze to wheezy
14:11
and it is onlky broken on a specific client
14:12
xfreerdp works fine
14:12
but as soon as I change to kiosk
14:12
the X server is defunct
14:13
with a message on the console saying No permission writing /var/log/Xorg.7.log
14:13
On another client it just works
14:14
startx just works as well
14:14
I believe it has something to do with the switch user command and xinit
14:14
Can anybody here help?
14:18
I have no idea where to look further at the moment
14:18flo1546796 has left IRC (flo1546796!~flo154679@unaffiliated/flo1546796, Ping timeout: 245 seconds)
14:21flo1546796 has joined IRC (flo1546796!~flo154679@unaffiliated/flo1546796)
14:28flo1546796 has left IRC (flo1546796!~flo154679@unaffiliated/flo1546796, Ping timeout: 245 seconds)
14:34flo1546796 has joined IRC (flo1546796!~flo154679@2001:660:5001:156:b150:cbeb:9dcd:947a)
14:34flo1546796 has joined IRC (flo1546796!~flo154679@unaffiliated/flo1546796)
14:38flo1546796 has left IRC (flo1546796!~flo154679@unaffiliated/flo1546796, Ping timeout: 245 seconds)
14:55yanu has left IRC (yanu!~yanu@lugwv/member/yanu, Quit: leaving)
14:58
<Zaphoid>
wouter: This is post reboot. Typically occurs between 2 and 4 hours after rebooting the LTSP host and related stations.
15:24vagrantc has joined IRC (vagrantc!~vagrant@freegeek/vagrantc)
15:40deeville has joined IRC (deeville!~deeville@38.117.108.108)
15:41jhon has joined IRC (jhon!7a3e10cb@gateway/web/freenode/ip.122.62.16.203)
15:42
<jhon>
Does anyone know much about LTSP and sftp ?
15:42
<vagrantc>
jhon: you might want to be more specific
15:43
<jhon>
i am trying to login with samba user on ltsp thin client
15:43
<vagrantc>
can you ssh to the LTSP server as that user?
15:44freedomrun has joined IRC (freedomrun!~freedomru@unaffiliated/freedomrun)
15:44
<jhon>
but it doesnt whoe me subsytem request for sftp by user
15:45
But when i tried to do that with unix user it works fine
15:45
<vagrantc>
you can ssh in, but not sftp in?
15:45
<jhon>
the only different between both authentication is just this one line that i found in /var/log/auth.conf
15:46
yup
15:46
i can use ssh
15:49
so i was wondering if i can make some changes through which I can use samba users with ltsp as well !!
15:49
<vagrantc>
i didn't think sshfs uses sftp...
15:50
at least, it doesn't use the dedicated sftp port... hrm.
15:50
<jhon>
no it doent
15:50
doesnt
15:51
<vagrantc>
what exactly is not working?
15:52
i mean, throw the protocols out... what are you actually doing that doesn't work?
15:53
<jhon>
Okay I am setting up a server with Ubuntu 12.04 LTS as a platform
15:53
I am running Samba4 as an AD for user authentication and LTSP for thinclient
15:53
both servers are running on the same host machine
15:54
So I want to configure services so that i can use Samba4 AD users with LTSP thin cleint
15:55
when i am logging in with local user i can log in and everything works fine for me
15:55
<vagrantc>
define local user
15:56
i.e. local to where?
15:56
<jhon>
user in /etc/passwd
15:56
<vagrantc>
which /etc/passwd
15:56
<jhon>
local to thin client
15:56
users whose entry i can find in /etc/passwd
15:56
<vagrantc>
normally, you don't have users configured in the thin client
15:57
you add all users to the server
15:57
<jhon>
yup
15:57
but it should work with other services like ldap and samba as well isnt it?
15:57
<vagrantc>
in the server's /etc/passwd, or in the thin client's /opt/ltsp/i386/etc/passwd ?
15:58
<jhon>
in server's /etc/passwd file
15:58
<vagrantc>
so, that's not local to the thin client, that's local to the server :P
15:59
<jhon>
yup local users for server
15:59
sorry that i didn't clarify that :P
16:00
<vagrantc>
so, from the server itself, can you: ssh ADUSER@localhost ? where ADUSER is a user configured in AD ?
16:00
hrm. gotta go...
16:00* vagrantc waves
16:00mealstrom has left IRC (mealstrom!~Thunderbi@46.63.71.254, Ping timeout: 240 seconds)
16:01
<jhon>
yes it is configured in AD
16:01
but I am using Samba4 as a directory service
16:14Phantomas has joined IRC (Phantomas!~Phantomas@ubuntu/member/phantomas)
16:17
<||cw>
wait, sftp just uses the ssh port right?
16:19
<vagrantc>
yup
16:20
well, the sftp implementation used in ltsp, at least
16:20
<||cw>
from what I understand, it uses sftp, and if ssh work, sftp should work
16:20
it uses the fuse sshfs right?
16:20
<vagrantc>
yup
16:22
<||cw>
so on the server side should use /etc/pam.d/sshd...
16:23
<vagrantc>
right
16:24
<||cw>
jhon: so what's the difference again? there's no /var/log/auth.conf...
16:25
jhon: can use use sftp directly?
16:25
<jhon>
so on the server there is /var/log/auth.log entry not the auth.conf entry.
16:26
sorry that was a typo
16:26
i can
16:26
<||cw>
so what's the difference?
16:26
<jhon>
between two log entries?
16:27
<||cw>
pam tracing is annoying, been a while since I did it, but clearly recall it being a lot harder than it should have been
16:27
yes
16:28
<jhon>
for the server's local user it is showing "subsystem request sftp for user username"
16:29
but for the samba user this entry does not exist.
16:29
I am using winbind to manage samba users on server
16:30
<||cw>
on the server, getent passwd {username} works?
16:31
<jhon>
yup it works
16:33
<||cw>
for the ad users what's the difference in the auth.log for ssh vs sftp?
16:36
<jhon>
no log generates regarding ad user either for ssh or sftp
16:39
<||cw>
so it's just not logging AD users
16:39
but ssh work and sftp doens't, is really odd
16:39
should an issue in open-ssh
16:40
<vagrantc>
and that unix users on the server work with sftp ... that's what makes it inscrutible
16:40
otherwise, i'd say the sftp sub-system was maye disabled...
16:41
jhon: so, what exactly isn't working with sftp?
16:41
jhon: the user's homedirs fail to mount? the user can't log in at all?
16:42
jhon: the user can't mount usb sticks?
16:42
these would all be very different problems.
16:42
<jhon>
basically ad users should request for sftp subsystem to fetch "/" system from the LTSP serve
16:42
<vagrantc>
LTSP doesn't *normally* do that...
16:42
<jhon>
so user can authenticate but can't login
16:43
<vagrantc>
so, you're sitting at the GUI login screen (hopefully LDM), and you enter in a username and password, hit enter, and what happens... ?
16:44
<jhon>
it restarts
16:44
<vagrantc>
ok.
16:45
<jhon>
and yes i am using LDM
16:45
<vagrantc>
and in the logs on the server, does it log the user successful or failed to authenticate?
16:45
or nothing at all?
16:46
<jhon>
successful authenicated
16:49
<vagrantc>
ok, is there anything in the user's ~/.xsession-errors on the server?
16:50
<jhon>
for ad user?
16:51
not for the ad user
16:52
<vagrantc>
and a unix user (i.e. one in the server's /etc/passwd) works fine?
16:52
<jhon>
yup
16:52
<vagrantc>
ok... let's enable some debugging options...
16:53
sudo ltsp-config lts.conf
16:53
should create /var/lib/tftpboot/ltsp/i386/lts.conf
16:53
<jhon>
yup
16:53
<vagrantc>
edit that, there might be an example SCREEN_02=shell ... uncomment that, or add that.
16:54
<jhon>
yup
16:54
<vagrantc>
you want to make sure its in the [default] section
16:54
reboot your thin client
16:54
<jhon>
it is under default sectionn
16:54
i have already done that
16:54
<vagrantc>
ok.
16:54
<jhon>
and i can use tty4 for shell under root priviledges
16:55
<vagrantc>
so, when your client gets to the login screen, ctrl-alt-f2
16:55
oh, you used SCREEN_04 ?
16:55
shouldn't matter much
16:55
either way, get to a root shell on the client
16:55
ctrl-alt-f#
16:55
<jhon>
yup
16:56
<vagrantc>
then: ssh user@server
16:56
<jhon>
login successfully
16:58
<vagrantc>
ok, what's the output of: groups
16:58
this is an AD user, yes?
16:59
<jhon>
yes
16:59
id command gives DOMAIN\username
17:00
groups outpur is users
17:00
<vagrantc>
ok, that'll cause problems for localdev later ...
17:01
ok, log out of that shell...
17:02
get back to the root shell on the thin client
17:02
<jhon>
yup
17:02
<vagrantc>
oh, what's the user's homedir?
17:02yanu has joined IRC (yanu!~yanu@178-117-230-250.access.telenet.be)
17:02yanu has joined IRC (yanu!~yanu@lugwv/member/yanu)
17:02
<jhon>
%h/%d/%u
17:03
<vagrantc>
i presume those are substitutions for something?
17:04
<jhon>
home
17:04DanishMan has joined IRC (DanishMan!~kvirc@62-243-156-218-static.dk.customer.tdc.net)
17:04
<jhon>
home/domain/username
17:04
<vagrantc>
ok, that might also be causing a problem
17:04
<jhon>
how
17:05
<vagrantc>
on the server, what the output of: getent passwd user
17:05
it would be very helpful to cut-and-paste that
17:05
it's kind of difficult troubleshooting with theoretical guesses
17:06
<jhon>
it gave me the home directory path and shell
17:06
home directory pathe is as i mentioned above and shell is /bin/bash
17:06
<vagrantc>
could you just cut and paste the line?
17:07
<jhon>
JINENDRA
17:07
<vagrantc>
?
17:07
<jhon>
JINENDRA\tom:*:3000017:100:tom:/home/JINENDRA/tom:/bin/bash
17:08
<vagrantc>
ok.
17:08
so, from the root shell on the thin client
17:09
sshfs tom@server:/home/JINENDRA/tom
17:09
<jhon>
sorry the output that i mentioned was on server
17:09
<vagrantc>
that's fine
17:10
<jhon>
when i ran "getent passwd" that on thiclient root shell it doen't give any output
17:10
<vagrantc>
sure
17:10
well, it should give you the whole client's passwd data
17:10
<jhon>
but it shows me output for getent group
17:10
<vagrantc>
though "getent passwd tom" should produce nothing.
17:11
did you try to configure the thin client to directly support AD?
17:11
or samba, or whatever?
17:11
i.e. did you modify the thin client's pam stack
17:11
<jhon>
no
17:12
<vagrantc>
doh. my sshfs command was wrong anyways
17:12
mkdir -p /home/JINENDRA/tom ; sshfs tom@server:/home/JINENDRA/tom /home/JINENDRA/tom
17:12
does that work?
17:13
<jhon>
that does does exist already
17:13
<vagrantc>
does the sshfs command fail?
17:13
<jhon>
and whenever i add a new user and try to login with a new user it creates a new folder on the server
17:13
with username
17:14
<vagrantc>
i'm asking about from the thin client
17:14
could you run:
17:14
mkdir -p /home/JINENDRA/tom ; sshfs tom@server:/home/JINENDRA/tom /home/JINENDRA/tom
17:14
on the thin client's root shell?
17:14
does that work?
17:17
<jhon>
it didnt gave me any error
17:17
can you please tell me that how can i check whether the command executed correctly or not
17:18
<vagrantc>
are there files in /home/JINENDRA/tom ?
17:18
and do they match the files that are on the server's /home/JINENDRA/tom ?
17:19
<jhon>
yes
17:19
<vagrantc>
ok...
17:20
so, doing what LDM does manually works fine.
17:20
most perplexing.
17:21
<jhon>
okay
17:22
so do i have to rebuild the image again ?
17:22
<vagrantc>
did this work at any point?
17:23
i don't see why you'd need to rebuild the image at this point...
17:23
you still don't know what's wrong.
17:24
<jhon>
no i tried to login again
17:24
but same thing happened
17:24
<vagrantc>
right, but we haven't changed anything that would require rebuilding the image
17:25
unless you've been doing things that you haven't told me about, but that would just be wasting my time...
17:25
<jhon>
yup
17:25
no i havent change anything
17:26
<vagrantc>
so, basically what we just did from the shell mimics parts of what LDM does ...
17:27
and those seemed to work fine.
17:27
so still have no clue about what's wrong.
17:27
ok, next ...
17:27
from the client root shell ... tail -F /var/log/ldm.log
17:28
<jhon>
no. The i have checked every file
17:28
for authentication
17:28
and it seems fine
17:28
<vagrantc>
sounds like you have it under control then.
17:28* vagrantc waves
17:41Phantomas has left IRC (Phantomas!~Phantomas@ubuntu/member/phantomas, Ping timeout: 240 seconds)
17:42jhon has left IRC (jhon!7a3e10cb@gateway/web/freenode/ip.122.62.16.203, Ping timeout: 240 seconds)
17:45freedomrun has left IRC (freedomrun!~freedomru@unaffiliated/freedomrun, Quit: So long and thanks for all the fish.)
17:55Phantomas has joined IRC (Phantomas!~Phantomas@ubuntu/member/phantomas)
18:06khildin has left IRC (khildin!~khildin@ip-213-49-85-69.dsl.scarlet.be, Quit: I'm gone, bye bye)
18:35monkwitdafunk has left IRC (monkwitdafunk!~AndChat49@24.114.37.3, Ping timeout: 264 seconds)
18:45deeville has left IRC (deeville!~deeville@38.117.108.108, Ping timeout: 252 seconds)
19:08stgraber has left IRC (stgraber!~stgraber@ubuntu/member/stgraber, Ping timeout: 246 seconds)
19:10stgraber has joined IRC (stgraber!~stgraber@ubuntu/member/stgraber)
19:19monkwitdafunk has joined IRC (monkwitdafunk!~AndChat49@24.114.45.216)
19:19monkwitdafunk has joined IRC (monkwitdafunk!~AndChat49@24.114.45.216)
19:22
<gbaman>
vagrantc: A question, any suggestion for a way to copy an OS over network to SD card via initrd for Pis?
19:22
Is that even possible with a normal initrd?
19:35Phantomas has left IRC (Phantomas!~Phantomas@ubuntu/member/phantomas, Quit: Leaving.)
19:47
<||cw>
gbaman: nc+dd ?
19:48
<gbaman>
well, that would be one way to do it..
19:49
I was leaning towards a normal file copy, but doing it as an image might be better
19:49
So you suggesting sending it via netcat across the network to build an image on the other side? Or am i understanding wrong ||cw
19:49
<||cw>
pipe the image via netcat, yes
19:50
the image would be pre-built and an nc socket waiting
19:50
<gbaman>
hmm
19:51
<||cw>
basically, clonezilla-lite
19:51
<gbaman>
hmm
19:51
and both are in a normal initrd
19:51
<||cw>
just an idea :)
19:52
<gbaman>
I had initially been looking at rsync, mainly so wouldnt have to copy entire image each time, then discovered it wasnt included in initrd
19:52
<vagrantc>
netcat and dd could work, although any blips in network connectivity might result in a bunk image.
19:52
<gbaman>
yea, that was my only worry
19:52
it being raw
19:53
<vagrantc>
actually, why bother with netcat, use NBD and dd.
19:53
you're already running the NBD server.
19:53
<||cw>
true
19:53
<gbaman>
would be quicker too
19:53
<vagrantc>
and that might handle retransmissions etter
19:54
<gbaman>
I am just thinking though about a non LTSP setup
19:54
<vagrantc>
you're in the wrong channel for that :P
19:54
<gbaman>
true
19:55
hmm
19:55
<||cw>
heh
19:55
<gbaman>
there is no difference us loading an LTSP created image off SD card than off network
19:55
just different kernel parameters, right?
19:55
<||cw>
netcat server side would have to be restarted for each transfer. nbd would be a better solution
19:55
<vagrantc>
gbaman: for the most part, no.
19:56
gbaman: you'll have to make sure it knows what servers to connect to and such that it normally infers from the NBD/NFS server.
19:56monkwitdafunk has left IRC (monkwitdafunk!~AndChat49@24.114.45.216, Ping timeout: 252 seconds)
19:57
<gbaman>
can we point it to server as normal which just points to sd card?
19:58
<mmetzger>
Is the LDM_Server lts.conf option valid in 12.04?
19:59
<vagrantc>
mmetzger: should be.
20:00
<||cw>
mmetzger: what's "man lts.conf" say? :)
20:00
<vagrantc>
mmetzger: you'll need to get the ssh keys into the client image
20:00
gbaman: i don't understand your question...
20:00
gbaman: oh, you mean, dhcp will tell it to use the SD card?
20:00
<gbaman>
no
20:01
well, maybe?
20:01
<vagrantc>
that would be a good way to do it.
20:01
<mmetzger>
vagrantc: Already verified that worked (enabled local root login, ssh'd to the ldm server in question, host key was known)
20:01
<vagrantc>
but it's not really implemented.
20:01
<||cw>
gbaman: you mean have nbd point to an sd card device file instead of the image file?
20:01
<gbaman>
keeping in mind pis still do though have the IP address in the boot partition
20:01
<mmetzger>
||cw: "No manual entry for lts.conf" ;) Seriously though, for some reason that option is undocumented
20:02
<gbaman>
I was meaning, pis boot as usual, they look at NBD server, is there a way we can then from there, tell the pis to look at their own sd card
20:02
so the NBD server actually points them somewhere else?
20:02
<vagrantc>
mmetzger: apt-get install ltsp-docs
20:03
seems documented on my copy of the lts.conf manpage.
20:03
<||cw>
it does seems only vaguely documented
20:03
<vagrantc>
how is that vague?
20:03
it's a list of ip addresses
20:03
or hostnames
20:04
i.e. LDM_SERVER="1.2.3.4 altserver bestserver"
20:04
<||cw>
right, but doens't mention anything about ssh keys or other pre-reqs
20:04
<mmetzger>
vagrantc: Forgive me - the web versions I've seen haven't mentioned it, and it wasn't listed in 10.04 back when I set up this monstrosity.
20:05
<vagrantc>
well, if you're reading 4 year old docmentation...
20:05
<||cw>
I do see that google brings up the 0.99 version as the top hit
20:05
<vagrantc>
but yes, the ssh keys aren't documented as part of that option.
20:06
<||cw>
trick is noticing that and clicking on the new version
20:06
<vagrantc>
1.1 is the most current...
20:06
<mmetzger>
Regardless, pardon the stupidity.
20:08
<vagrantc>
read the manpage for ltsp-update-sshkeys for information on how to update the ssh keys
20:08
<gbaman>
hmm
20:09
vagrantc: werent we at some point able to do a local stored client?
20:09
was pretty sure we did, very early on
20:09monkwitdafunk has joined IRC (monkwitdafunk!~AndChat49@24.114.45.216)
20:11
<||cw>
!local-boot
20:11
<ltsp>
local-boot: If you want LTSP fat clients on a low-speed network, you can put i386.img on e.g. C:\Boot\LTSP\i386.img and use this command line in pxelinux.cfg: APPEND ro initrd=ltsp/i386/initrd.img init=/sbin/init-ltsp root=/dev/sda1 rootflags=ro loop=/Boot/LTSP/i386.img; IPAPPEND 3
20:12
<vagrantc>
that doesn't work on debian
20:12
<gbaman>
found the old guide you wrote vagrantc
20:12
<vagrantc>
you have to implement the loop= handling
20:12
<gbaman>
# FIXME: copy server's public ssh keys from the server to /etc/ssh/ssh_known_hosts
20:13
<||cw>
well, if the local is an sd card partition, you wouldn't need loop
20:13
<gbaman>
http://cascadia.debian.net/~vagrant/rpi-ltsp-howto.txt
20:13
bottom part
20:13
<vagrantc>
true enough.
20:13
gbaman: what's your point?
20:13
<gbaman>
that it is doable
20:13
we can boot it that way, question being how would you get it on?
20:13
<vagrantc>
yes, it's doable, you just have to do it right :)
20:14
<gbaman>
literally just copy it from NBD, then a script that makes the required config changes?
20:15PhoenixSTF has joined IRC (PhoenixSTF!~rudiservo@78.29.155.245)
20:15
<vagrantc>
sure.
20:32mealstrom has joined IRC (mealstrom!~Thunderbi@46.63.63.163)
20:38monkwitdafunk has left IRC (monkwitdafunk!~AndChat49@24.114.45.216, Ping timeout: 264 seconds)
20:54DanishMan has left IRC (DanishMan!~kvirc@62-243-156-218-static.dk.customer.tdc.net, Quit: KVIrc 4.2.0 Equilibrium http://www.kvirc.net/)
20:56monkwitdafunk has joined IRC (monkwitdafunk!~AndChat49@24.114.45.216)
21:08monkwitdafunk has left IRC (monkwitdafunk!~AndChat49@24.114.45.216, Ping timeout: 264 seconds)
21:08gbaman has left IRC (gbaman!~gbaman@host81-134-104-240.in-addr.btopenworld.com, Remote host closed the connection)
21:10gbaman has joined IRC (gbaman!~gbaman@host81-134-104-240.in-addr.btopenworld.com)
21:18monkwitdafunk has joined IRC (monkwitdafunk!~AndChat49@24.114.45.216)
21:27charlie has joined IRC (charlie!32cd2362@gateway/web/freenode/ip.50.205.35.98)
21:27charlie is now known as Guest61551
21:28
<Guest61551>
Does anyone have any interest in helping me troubleshoot an issue?
21:29
<vagrantc>
just describe your issue, and wait patiently for someone to respond
21:29
!question
21:29
<ltsp>
question: if you have a question about ltsp, please go ahead and ask it, and people will respond if they can. please also mention the linux distro and release you're using. :)
21:32
<Guest61551>
Ubuntu 12.04 - i386 Thin Client. i915 Intel Driver is not found when running glxgears. Result is ~22 FPS for glxgears. General result is that the whole windowing system is choppy.
21:34
Alternatively, the amd64 thin client runs about 77 FPS on the more robust laptop I have, which claims the i945 driver is not found when running glxgears. So I do not believe network latency is the issue.
21:35
Ubuntu 12.04.4*
21:38
The troubled i386 thin client I am using now is the 1700 series from disklessworkstations.com
21:48
I have noticed an issue:
21:48
libGL: OpenDriver: trying /usr/lib/x86_64-linux-gnu/dri/tls/i915_dri.so
21:49
that path indicates a 64-bit driver. However, I specified --arch i386 when building the image.
21:52
<vagrantc>
are you running it as a fat client or a thin client?
21:53
<Guest61551>
thin
21:53
<vagrantc>
then you're probably running glxgears on the server.
21:53
so it's using, or trying to use, the server hardware.
21:53
<Guest61551>
I understand. Perhaps I should look into enabling "
21:54
LocalApps"
21:54
Is there any reason why the amd64 thin client i have (which is a more powerful PC) would be running at 3x the framerate though?
21:55
I assumed it was a delay with the Xserver displaying the information on the monitor.
21:56
<vagrantc>
maybe it booted as a fat client and was running locally?
21:58
<||cw>
faster nic?
21:59
<vagrantc>
oh yeah, a gigabit nic, or even a driver with better support could explain a speed improvement.
21:59monkwitdafunk has left IRC (monkwitdafunk!~AndChat49@24.114.45.216, Ping timeout: 276 seconds)
22:00
<Guest61551>
I believe I would have needed to manually specify that the i386 image be a fat client when building (https://help.ubuntu.com/community/UbuntuLTSP/FatClients)
22:01
Let me look into the nic. I know the switch and server I am using are gigabit ethernet....
22:01
<vagrantc>
not necessarily... newer versions autodetect under certain conditions.
22:01
i.e. sufficient ram and presence of a .desktop file in /usr/share/xsessions
22:03
<Guest61551>
ls -al shows an ubuntu.desktop file in /usr/share/xsessions
22:03
<vagrantc>
on the server, or on the client OS ?
22:03
<Guest61551>
However, I believe that /usr/share/xsessions is coming from the server's filesystem. Even though I am running the client.
22:04
<vagrantc>
what about /opt/ltsp/*/usr/share/xsessions
22:04
<Guest61551>
ah yes, that is the location for the client images (where wildcard is i386 or amd64)
22:05
there is no 'xsessions' folder in /opt/ltsp/*/usr/share/
22:05
*/opt/ltsp/i386/usr/share
22:06
nor is there an xsessions folder in /opt/ltsp/amd64/usr/share
22:09
the diskless i386 client has a gigbit nic, however, I'm not sure how to verify that connection... since everything i run in the thin client terminal, responds with hardware information about the server.
22:10
I wondering if this is the problem: Intel® AtomTM N270 1.6 GHz
22:10
and decoding the media stream
22:12
Which is a processor from ~2008
22:12
well thanks for your time. I'm going to take a break and get some food and not think about this for a while. If anyone has any ideas or feedback i started a thread here: http://ubuntuforums.org/showthread.php?t=2219584
22:13
Thanks again for the tips. I think i have some ideas i can try... such as building a fat client image, and verifying some hardware/software settings.
22:13
<vagrantc>
ltsp-localapps xterm
22:13
will give you a local terminal
22:13
<Guest61551>
whoa...
22:14
holy smokes... it worked... this should have been the first thing explained in the docs
22:15
<vagrantc>
we've been looking for documentation writers for years...
22:15
though the current docs are getting rather stale... could really use a refresh
22:16
<Guest61551>
I would gladly give some more details when i get this system up and running for my development team, as i need to document and detail my experience and gotchas anyway
22:18
at this point... if I can get the video smoothed out so its tolerable. My next step will be to integrate our user directory via ldap, and let the developers start breaking things.
22:20
FYI... there is no /usr/share/xession[s] on the thin client ramfs i am now able to access with ltsp-localapps xterm
22:20
But I understand much more about the system. If i wan to run something locally, i need to build the fat client so that the binaries are available to run with the 'ltsp-localapps'
22:22
When i get this all worked out, i'll swing back through here with a real IRC name and look into updating the docs to support ubuntu 12.04... only real gotcha i have found so far is that the nbd-server/client packages v. 2.9 have a bug with i386
22:22
which i solved here http://ubuntuforums.org/showthread.php?t=2219370
22:23
by manually updating the packages inside the chroot
22:23
thanks again.
22:32
<vagrantc>
good luck
22:56monkwitdafunk has joined IRC (monkwitdafunk!~AndChat49@24.114.45.216)
22:58monkwitdafunk has joined IRC (monkwitdafunk!~AndChat49@24.114.45.216)
23:03gdi2k has left IRC (gdi2k!~gdi2k@222.127.60.203, Ping timeout: 252 seconds)
23:04gdi2k has joined IRC (gdi2k!~gdi2k@222.127.60.203)
23:05imox has joined IRC (imox!~imox@p57A97651.dip0.t-ipconnect.de)
23:09zama has left IRC (zama!zama@2604:180::502b:135a, Remote host closed the connection)
23:31ogra_ has left IRC (ogra_!~ogra_@p5098ed03.dip0.t-ipconnect.de, Ping timeout: 276 seconds)
23:49imox has left IRC (imox!~imox@p57A97651.dip0.t-ipconnect.de, Quit: imox)