|00:10||staffencasa has left IRC (firstname.lastname@example.org, Ping timeout: 240 seconds)|
|00:52||Phantomas has joined IRC (Phantomas!~Phantomas@ubuntu/member/phantomas)|
|01:16||Selveste1 has left IRC (Selveste1!~Selveste1@static-5-103-136-165.seas-nve.net, Ping timeout: 250 seconds)|
|01:21||Selveste1 has joined IRC (Selveste1!~Selveste1@static-5-103-136-165.seas-nve.net)|
|01:32||Selveste1 has left IRC (Selveste1!~Selveste1@static-5-103-136-165.seas-nve.net, Read error: Operation timed out)|
|01:32||Selveste1 has joined IRC (Selveste1!~Selveste1@static-5-103-136-165.seas-nve.net)|
|02:10||Phantomas has left IRC (Phantomas!~Phantomas@ubuntu/member/phantomas, Quit: Leaving.)|
|02:30||mattcen has joined IRC (email@example.com)|
|02:54||Fenuks has joined IRC (Fenuks!~Fenuks@184.108.40.206)|
|03:02||alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg)|
Do you think we should start mounting /tmp as a tmpfs on the clients, as most distros do nowadays? (btw what do wheezy/jessy do with /tmp?)
I don't know if the problem is only with ssh or if it affects all sockets in /tmp.... if it does, gnome-keyring, pulseaudio etc are also affected
Hmmm wheezy doesn't, ok
it's an optional feature in wheezy
dunno if there are new plans for jessie
i often configure my setups too use tmpfs on /tmp
Anyways, for libpam-sshauth we should change the socket to /var
err, /var/run or /run
yeah, /var/run or /run would be fine
|03:49||* alkisg assumes that aufs doesn't have the same problem as overlayfs, since vagrantc and sbalneav didn't experience it...|
although we'd need to create a subdir in /run that was owned by the user to create the user-owned socket, yes?
There's a trend for user-owned dirs in /run/user, e.g.: $ echo $XDG_RUNTIME_DIR
Too bad that mktemp doesn't use it yet
http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html, Lennart Poettering etc
mktemp -d /run/user/BLAH
mktemp -d /run/user/BLAH/tmpfile-XXXX ?
Sure, or setting TMPDIR
many programs ignore tempdir intentionally
I think the spec says that a program should prefer XDG_RUNTIME_DIR first, then honour TMPDIR etc
vagrantc: maybe for ltsp we could create /run/tmp and dynamically symlink /tmp to it?
Or are there any issues if /tmp is a symlink?
and then http://lists.freedesktop.org/archives/xdg/2010-November/011709.html
|04:05||* vagrantc wonders how many applications will follow those specs, though|
Hmmm so if /tmp is a tmpfs, maybe we shouldn't be putting nbd-swap there, but to /var/tmp instead?
|04:33||alexqwesa has left IRC (firstname.lastname@example.org, Ping timeout: 264 seconds)|
|05:27||gdi2k has joined IRC (email@example.com)|
alkisg, Thanks for your assistance the other day with the strange audio issues I was having (frequencies being cut, causing voice quality issues on VOIP). Turns out the headsets are "optimized" and cut off at less than 10 khz. This, combined with linphone cutting the higher again for ulaw resulted in bad clarity. We've switched to wideband speex16 on the clients and let Asterisk do the conversion to ulaw, and now things are fine
(sound on ltsp itself is fine)
gdi2k: good to hear :)
I have 10 thin clients on my server now, and load is around 6 - 7 when all are doing work. This is on a quad core with no HT. Time to upgrade?
I do not know about 'fatclient', but I do know about these similar topics: 'fatclients', 'fatclient-printers'
fatclients: You may find some info about the Ubuntu/LTSP implementation of fat clients at https://help.ubuntu.com/community/UbuntuLTSP/FatClients
I'm familiar with fat clients but our machines are crusty old antiques, running something like firefox locally would drive people nutty. We do run skype and linphone local though
run a lighter desktop?
we use XFCE, which isn't bad - much lighter and I worry about usability
dunno how LXDE compares, but i think it's even lighter and comprable useability, depending on what you're using
|05:40||* alkisg was suggesting that instead of spending money on a better server you could spend them on new clients instead|
is fat clients the way to go these days if adding new clientds?
arguably ... many applications behave badly on thin clients
seems like I can put together a current-gen celeron for $200, which will probably be faster than the server (Phenom X4 955)
gdi2k: you're running with LDM_DIRECTX=true ?
vagrantc: so, about the user-owned ssh socket, remoteapps etc, can we just depend on socat which can bind a user-owned socket with the ssh socket, and also supports multiple connections with it (forking), and call it a day? :)
That way keys would also still work
alkisg: i'm ok with that :)
Nice, thanks :)
alkisg: it doesn't have many dependencies we don't already have installed, doesn't increase the image size significantly, and is code we don't have to maintain :)
And we can reuse it in many places
|05:43||* vagrantc assumes socat is commonly available in multiple distros|
I think it's even available in windows... :D
maybe atsp too
|05:45||* vagrantc hasn't worked on dgkfbsdtsp for a couple years|
|05:46||* vagrantc threatened to work on dghtsp at one point|
|05:47||* alkisg is reading a _presentation_ of vagrantc about dgkfbsdtsp and wonders why it isn't written in plain text... :D|
|05:48||alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Remote host closed the connection)|
on a fat client set up, the server doesn't do much aside from serving up boot images and file systems for the clients right? As long as it has good disks and network, it doesn't have to be a monster right?
|06:27||work_alkisg is now known as alkisg|
alkisg, nice, so at this point, as I have no more thin clients and the server is at its limit, my best approach to adding would be to just add fat clients and perhaps a new fast-disk'd "server" just for those fat clients. reasonable?
gdi2k: sure, and you probably don't even need the faster disk
alkisg, sounds good, thanks for your help
vagrantc: proof of concept: pam) ssh -NMS /tmp/s guest@localhost
ltsp-remoteappsd) socat UNIX-LISTEN:/tmp/soc,fork EXEC:"ssh -S /tmp/s guest@localhost"
ltsp-remoteapps) socat - UNIX-CONNECT:/tmp/soc
...and now ltsp-remoteapps can get output from the server AND are able to run in parallel :)
|06:38||freedomrun has joined IRC (freedomrun!~freedomru@unaffiliated/freedomrun)|
(or EXEC:"ssh -XCS /tmp/s guest@localhost" to get a display too)
...-XC is needed on both the EXEC line and on the ssh line
vagrantc: currently, remoteapps always use the ssh socket, regardless of the LDM_DIRECT value, right?
I mean, they don't do the xhost magic, but run ssh -Y...
alkisg: don't remember
looking at the reverse dependencies for socat, all sorts of cool projects use it.
maybe ltsp will be cooler when we switch to using it.
If I run `ssh -MS` as user, I can then just go ahead and reuse it with `ssh -S` as root
If I run `ssh -MS` as root and then chown the socket, I can't reuse it with `ssh -S` as user...
|07:13||* alkisg asks in #openssh if that should be possible somehow, which would save us from all the trouble...|
Meh... the filesystem again, tmpfs behaves differently than ext4
Ah, seteuid might do it
well, have fun with that! :)
|07:21||vagrantc has left IRC (vagrantc!~vagrant@freegeek/vagrantc, Quit: leaving)|
|07:35||freedomrun has left IRC (freedomrun!~freedomru@unaffiliated/freedomrun, Ping timeout: 260 seconds)|
|07:51||freedomrun has joined IRC (freedomrun!~freedomru@unaffiliated/freedomrun)|
|08:00||staffencasa has joined IRC (firstname.lastname@example.org)|
|08:07||staffencasa has left IRC (email@example.com, Ping timeout: 260 seconds)|
|08:13||vmlintu has joined IRC (firstname.lastname@example.org)|
|08:15||alexqwesa has joined IRC (email@example.com)|
|09:03||bennabiy has left IRC (bennabiy!~Thunderbi@24-181-55-79.dhcp.gnvl.sc.charter.com, Read error: Operation timed out)|
|09:04||freedomrun has left IRC (freedomrun!~freedomru@unaffiliated/freedomrun, Quit: So long and thanks for all the fish)|
|09:04||bennabiy has joined IRC (bennabiy!~Thunderbi@24-181-55-79.dhcp.gnvl.sc.charter.com)|
Yey, libpam-sshauth works for me too! :D
|09:19||Gremble has joined IRC (Gremble!~Ben@cpc35-aztw23-2-0-cust207.18-1.cable.virginm.net)|
|09:19||Gremble is now known as Guest33252|
|10:16||workingcats has joined IRC (firstname.lastname@example.org)|
|11:01||staffencasa has joined IRC (email@example.com)|
|11:07||staffencasa has left IRC (firstname.lastname@example.org, Ping timeout: 240 seconds)|
|11:11||Fenuks has left IRC (Fenuks!~Fenuks@220.127.116.11, Read error: Operation timed out)|
|11:45||willianmazzardo has joined IRC (email@example.com)|
|11:47||alexqwesa has left IRC (firstname.lastname@example.org, Ping timeout: 245 seconds)|
|11:57||alexqwesa has joined IRC (email@example.com)|
|12:38||alkisg has left IRC (firstname.lastname@example.org, Quit: Leaving.)|
|12:42||work_alkisg has joined IRC (email@example.com)|
|12:45||work_alkisg has left IRC (firstname.lastname@example.org, Client Quit)|
|12:45||work_alkisg has joined IRC (email@example.com)|
|12:48||work_alkisg has joined IRC (firstname.lastname@example.org)|
|12:49||work_alkisg is now known as alkisg|
|12:49||brunolambert has joined IRC (brunolambert!brunolambe@nat/revolutionlinux/x-klutklhhjxctmdjq)|
|13:01||cliebow has left IRC (cliebow!~cliebow@WatchGuard.ellsworth-hs.ellsworth.k12.me.us, Ping timeout: 272 seconds)|
|13:09||vmlintu has left IRC (email@example.com, Read error: Connection reset by peer)|
|13:14||cliebow has joined IRC (cliebow!~cliebow@WatchGuard.ellsworth-hs.ellsworth.k12.me.us)|
|13:41||freedomrun has joined IRC (freedomrun!~freedomru@unaffiliated/freedomrun)|
|13:49||Guest33252 has left IRC (Guest33252!~Ben@cpc35-aztw23-2-0-cust207.18-1.cable.virginm.net, Quit: I Leave)|
|13:52||knipwim has left IRC (firstname.lastname@example.org, Quit: leaving)|
|15:18||mgariepy has left IRC (mgariepy!mgariepy@ubuntu/member/mgariepy, Quit: Leaving)|
|15:20||mgariepy has joined IRC (mgariepy!mgariepy@ubuntu/member/mgariepy)|
|15:40||staffencasa has joined IRC (email@example.com)|
|15:47||staffencasa has left IRC (firstname.lastname@example.org, Ping timeout: 240 seconds)|
|15:49||staffencasa has joined IRC (email@example.com)|
|16:14||Phantomas has joined IRC (Phantomas!~Phantomas@ubuntu/member/phantomas)|
|16:18||staffencasa has left IRC (firstname.lastname@example.org, Ping timeout: 240 seconds)|
|16:22||vagrantc has joined IRC (vagrantc!~vagrant@freegeek/vagrantc)|
|16:32||alkisg1 has joined IRC (alkisg1!~alkisg@ubuntu/member/alkisg)|
|16:42||Phantomas has left IRC (Phantomas!~Phantomas@ubuntu/member/phantomas, Quit: Leaving.)|
|16:45||alkisg has left IRC (email@example.com, Ping timeout: 248 seconds)|
|16:46||work_alkisg has joined IRC (firstname.lastname@example.org)|
|16:51||alkisg1 is now known as alkisg|
|16:52||gdi2k has left IRC (email@example.com, *.net *.split)|
|16:52||alexqwesa has left IRC (firstname.lastname@example.org, Ping timeout: 264 seconds)|
|16:55||gdi2k has joined IRC (email@example.com)|
|16:58||gdi2k has left IRC (firstname.lastname@example.org, *.net *.split)|
|17:04||gdi2k has joined IRC (email@example.com)|
|17:09||gdi2k has left IRC (firstname.lastname@example.org, *.net *.split)|
vagrantc: I managed to get libpam-sshauth/lightdm and libpam-sshauth/logind working!
So, just to make sure, the plan now is to write an ldm in shell that uses libpam-sshauth, and drop ldm.c/ssh.c etc, right?
...but keep using our greeter...
|17:15||gdi2k has joined IRC (email@example.com)|
vagrantc: and the next step after that, would be to merge ltspdm/ldminfod/gtkgreeter to ltsp-trunk, and drop ldm-trunk?
alkisg: i think it should still be a separate project
vagrantc: the greeter?
alkisg: at least
alkisg: not killing off ldm-trunk, but maybe changing what's there.
still not clear on the need to rewrite in shell...
OK, I don't mind at all, as long as ldm-trunk is just the greeter, it doesn't even receive a lot of updates...
It's just much easier, I think it's overengineered now, with plugins etc
It's much harder to test/debug, to add features in it, it needs more ram... i don't see any benefits at all in having it in .c
The greeter, sure. libpam-sshauth, sure. But ldm.c is just a wrapper to run shell scripts...
For example, it'll take me longer to write ldm/pam.c than to rewrite ldm from scratch in shell...
There's a regression potential, ok, but it's there anyway since we're switching to pam
and the reason to do this rewrite rather than switch to lightdm is we don't think we'll be able to run enough of the ldm hooks from lightdm?
The rewrite should take e.g. a week, then we can progressively start modifying the code so that any dm is supported
But lightdm has a lot of bugs, e.g. it messes up the keyboard layout so people using it can't type greek after login if they don't go to gnome control center and manually add the keyboard layout,
there are problems with accountsservice etc etc... it's quite buggy
Many bug reports were filed years ago but noone seems to care
well, that's a shame.
Also, moving to lightdm will require a lot of changes, I don't think we can do them in a single run
and we'll lose a lot of functionality, e.g. we won't be able to select a server or a backend easily
alkisg: are these lightdm issues things that haven't gotten fixed at all, or are we talking about backportability?
They're not fixed at all
regarding the server/backend selection ... those could be implemented as session types...
but that gets pretty ugly.
Yeah, imagine 10 servers and 3 backends... :D
most of my setups have been 2-4 servers with 1 backend...
and 2-5 session types
I think the most significant part is that with ldm (in shell or c, that doesn't matter) we'll be able to move forward progressively, we'll have something that still works in any commit in ltsp-trunk
Then we'll have enough time to think on how to properly implement the session types, where to put the hooks etc...
with getting ldm using libpam-sshauth, we're talking about something that could work in parallel with lightdm support
so those who didn't need features could still use *dm, but default would still be the next-gen ldm
Yup I think we agree on everything _but_ the need to rewrite ldm in shell
Your main objections are regressions and security, right?
yeah. regressions are likely to happen no matter which route we go though.
maybe even more likely with lightdm/libpam-sshauth
With ldm in shell we're supposed to keep all the existing functionality without changing anything in ltsp, while with lightdm we'll have to rewrite all the hooks, rename all the LDM* lts.conf variables etc etc
vagrantc: why did you use pam-mkhomedir instead of mounting it with sshfs ia the ssh socket?
libpam-sshauth does give us a hook that runs as root, right?
|17:49||freedomrun has left IRC (freedomrun!~freedomru@unaffiliated/freedomrun, Quit: So long and thanks for all the fish)|
|17:49||staffencasa has joined IRC (firstname.lastname@example.org)|
alkisg: i just followed sbalneav's instructions and turned it into a package
maybe tweaked a few things
alkisg: i think you need the homedir to actually mount, and may as well use pam_mkhomedir?
vagrantc: the idea there is to run sshfs as the user/
EXTRAMOUNTS won't work that way...
...meh, not even /home/username can be mounted that way, the user has no rights there
alkisg: root or user, you need the directory to mount on top of
But why use pam when we can do it with mkdir?
alkisg: why *not* use the pam_mkhomedir?
We already have scripts that do all that.. I think the first steps forward should involve as little changes to our existing scripts as possible, to avoid regressions
Well, to prevent installing a whole package and putting it to the pam stack just to avoid an existing mkdir...
|17:59||* alkisg tries to organize his thoughts:|
The move to lightdm will need a lot of time, I don't think it can be done for e.g. 14.04, and I doubt it can be ready for jessie,
it doesn't require an additional package
so that means ldm/pam.c or ldm.sh need to be implemented in order to have something releaseable for them...
And, I think I'd want to invest in those three options in this order: 1) ldm.sh, 2) lightdm, 3) ldm/pam.c
|18:02||bennabiy has left IRC (bennabiy!~Thunderbi@24-181-55-79.dhcp.gnvl.sc.charter.com, Ping timeout: 265 seconds)|
I don't mind going with (2), but I fear that ltsp-trunk won't be in a releaseable state for 14.04/jessie
|18:03||* alkisg can work-around most of the lightdm bugs with sch-scripts, e.g. automatically fix the keyboard layout after lightdm breaks it on login etc|
is gdm any better?
I don't remember if lightdm works in 16 bit color mode or not
it does on debian
gdm 2 was fine, gdm 3 was broken for as long as ubuntu had it, I don't know if they fixed it recently
|18:05||bennabiy has joined IRC (bennabiy!~Thunderbi@24-181-55-79.dhcp.gnvl.sc.charter.com)|
I suppose all the LDM* variables should go away from lts.conf before releasing ltsp 6, if we decide that we want to completely drop ldm, right?
So yup I don't think we can drop ldm in time for 14.04/jessie with our currently limited time/manpower etc
...so maybe it's time to hit a pause button, focus on bug fixing etc, and continue with the big plans for the next big releases... :)
|18:09||* vagrantc 's next big release is in 2015, freeze end of 2014|
but i guess there's always backports...
|18:12||Phantomas has joined IRC (Phantomas!~Phantomas@ubuntu/member/phantomas)|
What we _could_ do at this time, is to introduce the replacement of the LDM* variables, and support both of them until ltsp 6...
E.g. LDM_PRINTER_LIST could become LTSP_PRINTER_LIST, and be implemented for both ldm and *dm...
|18:17||* vagrantc notes there are still some LTSP 4.x compatibility variables in code|
I wonder if we can have code that renames all the LDM_* environment variables to LTSP_* variables, so that then the new code only checks for LTSP_*...
LTSP_AUTOLOGIN, LTSP_DIRECTX, LTSP_SSHOPTIONS, LTSP_SESSION... do those names make sense?
would need to make sure the compatibility layer was available...
i.e. versioned depends/breaks and such
but that doesn't sound too hard.
We can duplicate the variables instead of renaming them
Nah it doesn't make sense, if we're going to move scripts from ldm to ltsp then we don't want the ldm scripts to do the same tasks twice
ah, only new code will use the new vars... got it
yeah, don't move that code into LTSP.
We will move it in the future, right?
You just don't want to move it yet?
only when you completely are rid of LDM...
I failed to express it correctly, but the idea above ^ was to move the scripts first, so that the "getting rid of ldm" was much easier later on
...while ltsp-trunk/ldm-trunk were still in a releaseable state at any time
moving scripts from ldm-trunk to ltsp-trunk will create really crazy interdependencies
I feel that the "start with getting rid of ldm" equals to "have ltsp broken for 6 work-months",
i don't think that's possible as an incremental step
...that's why I was trying to find ways to do it progressively, either with ldm/pam.c or with that ^ idea...
but i don't think it's good to move the ldm hooks out of ldm.
OK, yeah that's reasonable too, even though ldm doesn't really work without ltsp...
i had ldm workinng without LTSP at one point...
just as a proof of concept
Wait, maybe I missed something... are you saying that we can rename the variables to LTSP_* currently, and just leave the scripts in the ldm package?
Or are you also saying "don't rename the variables yet"?
i'm saying don't move scripts.
(it's not just about renaming, it's also about finding dm-agnostic ways to do things)
i *think* variable renaming could still happen even with scripts in LDM
|18:31||workingcats has left IRC (email@example.com, Quit: Leaving)|
...so there's work to do before dropping ldm, nice :)
basically, can either update LDM to use LTSP_* vars, and have a compatibility layer that sets LTSP_* from LDM_* (if LTSP_* is unset)
or leave LDM as is, and set up the compatibility layer to set LDM_* from LTSP_* (if LDM_* is unset).
for the dm-agnostic stuff ... we could have hook dirs that copy some of the functionality in LDM into LTSP directly, but LDM wouldn't use them. but that's kind of ugly to maintain forked code.
or LDM could be rewritten to check both vars every time...
Let's see an example
Currently: LDM_SSHOPTIONS, SSH_OVERRIDE_PORT
Future: PAM_SSHAUTH_HOST, PAM_SSHAUTH_PORT
|18:41||staffencasa has left IRC (firstname.lastname@example.org, Ping timeout: 245 seconds)|
...no SSHOPTIONS there
So, we could implement those from init-ltsp.d by modifying /etc/ssh/*config,
or we could ask Scotty to implement them in libpam_sshauth, if we need them
And then ok the compatibility scripts would do the appropriate renames...
|18:48||alexqwesa has joined IRC (email@example.com)|
OK, I'm convinced. When we do decide to move forward, the way to do is to duplicate ltsp-trunk to ltsp-old, start breaking :P things in ltsp-trunk, and just backport relevent stuff to ltsp-old until ltsp-trunk is releaseable... :D
|19:26||staffencasa has joined IRC (firstname.lastname@example.org)|
|19:37||willianmazzardo has left IRC (email@example.com, Ping timeout: 250 seconds)|
|19:44||staffencasa has left IRC (firstname.lastname@example.org, Ping timeout: 272 seconds)|
|19:47||Phantomas1 has joined IRC (Phantomas1!~Phantomas@ubuntu/member/phantomas)|
|19:48||Phantomas has left IRC (Phantomas!~Phantomas@ubuntu/member/phantomas, Ping timeout: 250 seconds)|
|19:53||staffencasa has joined IRC (email@example.com)|
|20:11||vagrantc has left IRC (vagrantc!~vagrant@freegeek/vagrantc, Quit: leaving)|
|20:20||Phantomas1 has left IRC (Phantomas1!~Phantomas@ubuntu/member/phantomas, Ping timeout: 264 seconds)|
|20:32||alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Remote host closed the connection)|
|20:38||Phantomas has joined IRC (Phantomas!~Phantomas@ubuntu/member/phantomas)|
|21:02||freedomrun has joined IRC (freedomrun!~freedomru@unaffiliated/freedomrun)|
|21:48||brunolambert has left IRC (brunolambert!brunolambe@nat/revolutionlinux/x-klutklhhjxctmdjq, Quit: Leaving.)|
|21:53||willianmazzardo has joined IRC (firstname.lastname@example.org)|
|23:12||alexqwesa has left IRC (email@example.com, Ping timeout: 245 seconds)|
|23:21||Phantomas has left IRC (Phantomas!~Phantomas@ubuntu/member/phantomas, Remote host closed the connection)|
|23:24||telex has left IRC (firstname.lastname@example.org, Read error: Connection reset by peer)|
|23:28||telex has joined IRC (email@example.com)|