00:17 | Ark74 has joined IRC (Ark74!~Luis@189.220.253.111.cable.dyn.cableonline.com.mx) | |
00:40 | yanu has left IRC (yanu!~yanu@178-116-58-90.access.telenet.be, Ping timeout: 260 seconds) | |
01:15 | yanu has joined IRC (yanu!~yanu@178-116-58-90.access.telenet.be) | |
01:53 | danau11 has joined IRC (danau11!~durban@66.251.57.114) | |
01:54 | PeperPots____ has left IRC (PeperPots____!sid1218@gateway/web/irccloud.com/x-ftbxjrjswopcmtjk, Ping timeout: 264 seconds) | |
01:55 | PeperPots____ has joined IRC (PeperPots____!sid1218@gateway/web/irccloud.com/x-bmcigpwkjoivwtun) | |
01:57 | danau11 has left IRC (danau11!~durban@66.251.57.114, Ping timeout: 250 seconds) | |
02:06 | cyberorg has left IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg, Ping timeout: 240 seconds) | |
02:56 | Aaron has joined IRC (Aaron!4a4919d5@gateway/web/freenode/ip.74.73.25.213) | |
02:57 | Aaron is now known as Guest68224 | |
02:58 | <Guest68224> anybody home?
| |
02:59 | ghost town
| |
02:59 | <vagrantc> !ask
| |
02:59 | <ltsp`> ask: Don't ask to ask a question, simply ask it, and if someone knows the answer, they'll respond. Please hang around for at least a full hour after asking a question, as not everybody constantly monitors the channel.
| |
03:00 | Guest68224 has left IRC (Guest68224!4a4919d5@gateway/web/freenode/ip.74.73.25.213) | |
03:28 | <Ark74> that boot is really useful sometimes :)
| |
03:34 | Ark74 has left IRC (Ark74!~Luis@189.220.253.111.cable.dyn.cableonline.com.mx, Quit: Saliendo) | |
03:35 | Ark74 has joined IRC (Ark74!~Luis@189.220.253.111.cable.dyn.cableonline.com.mx) | |
03:36 | Ark74 has joined IRC (Ark74!~Luis@189.220.253.111.cable.dyn.cableonline.com.mx) | |
04:43 | cyberorg has joined IRC (cyberorg!~cyberorg@opensuse/member/Cyberorg) | |
04:55 | bennabiy has left IRC (bennabiy!~bennabiy@unaffiliated/bennabiy, Remote host closed the connection) | |
06:17 | work_alkisg is now known as alkisg | |
07:21 | mikkel has joined IRC (mikkel!~mikkel@mail.dlvs.dk) | |
07:22 | ricotz has joined IRC (ricotz!~ricotz@p5B2A818C.dip0.t-ipconnect.de) | |
07:22 | ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz) | |
07:35 | sutula has left IRC (sutula!~sutula@207.118.162.188, Ping timeout: 245 seconds) | |
07:41 | alkisg is now known as work_alkisg | |
08:05 | vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving) | |
08:16 | uXus has left IRC (uXus!~uXus@217.77.222.72, Remote host closed the connection) | |
08:19 | sutula has joined IRC (sutula!~sutula@207-118-160-27.dyn.centurytel.net) | |
08:20 | uXus has joined IRC (uXus!~uXus@217.77.222.72) | |
09:16 | lbssousa has joined IRC (lbssousa!~laercio@177.143.0.126) | |
09:17 | robb_nl has joined IRC (robb_nl!~robb_nl@ip-213-49-85-168.dsl.scarlet.be) | |
10:12 | Ark74 has left IRC (Ark74!~Luis@189.220.253.111.cable.dyn.cableonline.com.mx, Quit: Saliendo) | |
10:41 | Faith has joined IRC (Faith!~paty_@unaffiliated/faith) | |
10:46 | work_alkisg is now known as alkisg | |
10:50 | Softeisbieger has joined IRC (Softeisbieger!~Softeisbi@dsl37-152-183.pool.bitel.net) | |
10:58 | danau11 has joined IRC (danau11!~durban@66.251.57.114) | |
11:04 | danau11 has left IRC (danau11!~durban@66.251.57.114) | |
11:48 | lied has joined IRC (lied!c8979fe6@gateway/web/freenode/ip.200.151.159.230) | |
12:09 | Faith has left IRC (Faith!~paty_@unaffiliated/faith, Ping timeout: 272 seconds) | |
12:09 | Faith has joined IRC (Faith!~paty_@200.144.182.219) | |
12:20 | Faith has left IRC (Faith!~paty_@200.144.182.219, Ping timeout: 272 seconds) | |
12:36 | Faith has joined IRC (Faith!~paty_@143.107.231.49) | |
13:03 | alkisg is now known as work_alkisg | |
13:25 | mikkel has left IRC (mikkel!~mikkel@mail.dlvs.dk, Quit: Leaving) | |
14:37 | <m3741> alkisg: Sorry for falling off of the face of the earth. i'd like to reboot/shutdown a thin client manually and remotely. for example if i apply updates to the image for local apps that i want to push out but no one is around to do a reboot...
| |
14:37 | work_alkisg is now known as alkisg | |
14:37 | <alkisg> !epoptes
| |
14:37 | <ltsp`> epoptes: Epoptes is a computer lab administration and monitoring tool. It works on Ubuntu and Debian based labs with LTSP or non-LTSP servers, thin and fat clients, standalone workstations, NX clients etc. More info: http://www.epoptes.org
| |
14:37 | <alkisg> See that ^ tool we developed
| |
14:38 | <m3741> heh, fine. :) i saw it but seemed like overkill for what i wanted to do. i'll go give it a shot. thanks as always!
| |
14:39 | also, thanks for fixing the shutdown_time bug 604908
| |
14:39 | <alkisg> m3741: it's designed to only need 1 mb ram on the clients, so it's as small as it gets
| |
14:39 | <m3741> alkisg: hmm, good to know. that is pretty tiny.
| |
14:39 | <alkisg> Nah, that was vagrantc that did it
| |
14:40 | I just closed the bug report once it got released
| |
14:40 | <m3741> ah, well in that case thanks to vagrantc!
| |
14:40 | are there coding guidelines for ltsp? do you accept patches? i'd like shutdown_time to have a day option as well instead of happening every day.
| |
14:41 | <alkisg> Sure, we accept patches
| |
14:41 | !ltsp-source
| |
14:41 | <ltsp`> ltsp-source: at http://bazaar.launchpad.net/~ltsp-upstream/ltsp/ltsp-trunk/files
| |
14:41 | <alkisg> Somewhere in the sources there's a small text about guidelines, but it's not a big deal
| |
14:42 | <m3741> sounds good. thx!
| |
14:42 | <alkisg> You're welcome
| |
14:55 | ben_roose has joined IRC (ben_roose!~roose@roose.cs.wichita.edu) | |
15:17 | gp has joined IRC (gp!~gp@104-14-168-137.lightspeed.rcsntx.sbcglobal.net) | |
15:23 | <Softeisbieger> Hey guys... I planning to buy a new pc and wonder about the following: Do people use LTSP in a 'private' (small) environment? In my case I'd like to put the server in the basement and have 2-3 clients around the house. Workload would be the usual web browsing, watching movies and I do some programming where I need some more computational power. So does LTSP make sense in such a setting?
| |
15:34 | Dlkauf has joined IRC (Dlkauf!4ada5522@gateway/web/freenode/ip.74.218.85.34) | |
15:35 | <Dlkauf> Hi there guys. I have a small problem that I havent seemed to be able to fix
| |
15:36 | My clients will see my LTSP server and go to the splash screen to log in, but it will not allow anyone to log in. If I use putty to go into the server it will allow me to use my creds, or if i go to the physical server it will allow me to use my creds
| |
15:38 | <||cw> Softeisbieger: sure, that wouldn't be too hard to setup. would also allow using older low RAM systems. but unless you have gigE you'll likely want to use the "fat client" mode
| |
15:38 | <Softeisbieger> I'd setup gigE...
| |
15:39 | <||cw> which will likely need a NIC upgrade for older clients
| |
15:39 | <Softeisbieger> what about the 'multimedia' experience? I read online that e.g. video playback sometime is not the best?
| |
15:40 | this would then be my buisness and spare-time rig, so...
| |
15:46 | is it possible to have a multi-monitor setup with ltsp?
| |
15:47 | <Hyperbyte> Softeisbieger, yes it is.
| |
15:49 | <||cw> video playback is limited by bandwidth, and unless the video player supports offloading to the client via xv or whatever it'll stream it raw uncompressed. adobe's flash player is one that doesn't offload.
| |
15:49 | <Hyperbyte> Video playing using LTSP is fine. You have to realize though that with thin clients, the media player runs on the server, and transmits picture to the client. At HD resolution, this is an uncompressed picture of 1920x1080, with X frames per second. You do the maths... bandwith usually becomes bottle neck, if not the CPU processing all the data.
| |
15:49 | <||cw> this is why fat client is often better. you get a lot of the same advantages of a thin client, but programs run on the local CPU
| |
15:50 | <Hyperbyte> This is not a problem with mediaplayers that support xvideo, those transmit the compressed data across the network and only unfold it on the receiving client.
| |
15:50 | <||cw> and with later P4/core and early core2 systems going for under $50, they make great fat clients
| |
15:51 | Hyperbyte: yes, but it is a problem with video from the web
| |
15:51 | <Hyperbyte> ||cw, depends. Firefox has a nice xvideo plugin for HTML5 video.
| |
15:51 | <Softeisbieger> mhmhm... concerning fat client: as i understand only certain programs are run on the client? I read e.g. about some firefox mod!?
| |
15:51 | <Hyperbyte> ||cw, whether that's enough for you or not, depends on your use case.
| |
15:51 | <||cw> there's still a LOT of flash video out there
| |
15:52 | Softeisbieger: fat client run all client side, from the server's disk
| |
15:52 | <Softeisbieger> ok
| |
15:52 | <||cw> thin can be configured to run certain programs client side (localapps) but it's awkward
| |
15:52 | <Softeisbieger> I see...
| |
15:54 | <||cw> Softeisbieger: I believe by default the server will automatically choose fat or thin client based on the clients ram. it's rather easy to switch and test the difference
| |
15:55 | especially if you use ltsp-pnp
| |
15:56 | <Softeisbieger> in my case I do programming/data mining stuff, so when using a fat client these program run on the client?
| |
15:56 | <||cw> yes
| |
15:56 | <Softeisbieger> because actually part of my motivation is to put the beefy machine away, to have silence...
| |
16:01 | robb_nl has left IRC (robb_nl!~robb_nl@ip-213-49-85-168.dsl.scarlet.be, Remote host closed the connection) | |
16:03 | <Hyperbyte> Softeisbieger, in our office in Rotterdam, I use thin clients everywhere. Don't even run the browsers locally, to have no noise and minimal heat generation in the workplaces/offices.
| |
16:03 | This creates a much more relaxed and productive working environment.
| |
16:04 | <Softeisbieger> k, thanks for the input. I guess I'll simply try it to see if i like it...
| |
16:04 | <Hyperbyte> It's functioning perfectly on a gigabit network with 3GB uplink from server and ~15 clients. The downside is, yes, playing flash video sucks. But we don't use that for office purposes. Plus, it only sucks when playing fullscreen. Otherwise it performs fine.
| |
16:06 | The framerate drops the more bandwith it requires. Same for gaming, for example. The server can handle it easily, but there's just not enough available bandwith in 1 gigabit per second to transfer HD video live across the network with full framerate.
| |
16:06 | But if you have smaller video playback window, there's less bandwith used.
| |
16:07 | <Softeisbieger> makes sense
| |
16:07 | <Hyperbyte> If you're not using 1920x1080 but lower resolution you could even play video fullscreen.
| |
16:09 | robb_nl has joined IRC (robb_nl!~robb_nl@ip-213-49-85-168.dsl.scarlet.be) | |
16:18 | vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc) | |
16:29 | gp has left IRC (gp!~gp@104-14-168-137.lightspeed.rcsntx.sbcglobal.net, Quit: Leaving) | |
16:48 | Faith has left IRC (Faith!~paty_@143.107.231.49, Ping timeout: 256 seconds) | |
16:48 | Faith has joined IRC (Faith!~paty_@143.107.231.49) | |
17:26 | <quinox> we want to use TOTP on all our servers
| |
17:26 | but the LTSP login probably doesn't like that right
| |
17:27 | * quinox looks into getting PAM to only require TOTP for non-LAN connections | |
17:58 | <alkisg> Dlkauf: try this:
| |
17:58 | !screen_02
| |
17:58 | <ltsp`> screen_02: To get a root shell on an Ubuntu thin client: https://help.ubuntu.com/community/UbuntuLTSP/ClientTroubleshooting#Using_a_shell_SCREEN
| |
17:59 | <alkisg> In that terminal, try: `ssh user@server`
| |
17:59 | Replace user with an existing username, but leave "server" exactly as "server", don't put another hostname or ip
| |
17:59 | See if you can log in that way
| |
18:07 | quinox: if you can use it with ssh, it will work with ltsp
| |
18:08 | ltsp just uses ssh to login to the server, that's all
| |
18:08 | <quinox> but how does the GUI work then?
| |
18:09 | right now you have a username and password field
| |
18:09 | (fat clients)
| |
18:09 | or you mean I should look into teaching LDM about it
| |
18:09 | <alkisg> it screen-scrapes ssh
| |
18:09 | No, ldm is a gui that runs ssh in the back end
| |
18:10 | It doesn't even use a library, it actually runs the ssh executable
| |
18:10 | <quinox> cool
| |
18:10 | uXus has left IRC (uXus!~uXus@217.77.222.72, Remote host closed the connection) | |
18:10 | <quinox> I still don't understand how it could work, but I can give it a try
| |
18:11 | <alkisg> Do you know how "ls | grep file" works?
| |
18:11 | Or "read x < file" ?
| |
18:11 | It's simple redirection of stdio between ldm and ssh
| |
18:11 | <quinox> so it will pop up another input box?
| |
18:12 | <alkisg> No, ldm reads the password from you via the gui, and then passes it to the ssh socket
| |
18:12 | ...to the ssh stdin
| |
18:12 | <quinox> yesh, but with TOTP I need to provide 2 pieces of information
| |
18:12 | the password and the TOTP
| |
18:12 | <alkisg> How would that work with ssh?
| |
18:13 | <quinox> it's part of the login process
| |
18:13 | the server can send queries to the client, and the client can respond
| |
18:13 | <alkisg> So ssh asks 3 things? username, then password, then totp?
| |
18:13 | robb_nl has left IRC (robb_nl!~robb_nl@ip-213-49-85-168.dsl.scarlet.be, Remote host closed the connection) | |
18:13 | <quinox> yes
| |
18:13 | <alkisg> Hmm ldm does show the ssh messages, but I'm not sure if it can handle the 3rd input
| |
18:14 | It could be patched to support it, but I'm afraid that it currently won't be able to handle it
| |
18:14 | Give it a try though
| |
18:14 | I think it was patched to handle password expiry
| |
18:14 | I.e. "your password has expired, enter a new one..."
| |
18:14 | <quinox> ah, it's very similar to that
| |
18:14 | <alkisg> So it might have some support for additional input
| |
18:15 | <quinox> it's probably at the same level in the protocol actually
| |
18:18 | danau11 has joined IRC (danau11!~durban@66.251.57.114) | |
18:19 | danau11 has left IRC (danau11!~durban@66.251.57.114) | |
18:20 | <quinox> I see http://sourceforge.net/p/ltsp/mailman/message/29868837/ which suggest it won't be possible until at least LTSP6
| |
18:22 | <alkisg> It's just stdio, I'm sure it can be patched to support it even before ltsp 6 where ldm will be dropped
| |
18:24 | Hehe, put up a bounty if you want :D
| |
18:24 | !bounties
| |
18:24 | <ltsp`> Error: "bounties" is not a valid command.
| |
18:25 | <alkisg> !learn bounties as You can ask an LTSP developer to implement new features or fix hard bugs by offering a bounty: http://wiki.ltsp.org/wiki/Bounties
| |
18:25 | <ltsp`> The operation succeeded.
| |
18:26 | <quinox> I think I can teach PAM to not ask for TOTP for LAN IPs
| |
18:26 | <Dlkauf> OK I was away from my desk. Yes I can use the SSH into the server via IP address from Putty. But When I try to log in on the Login screen it will not accept my login and password
| |
18:27 | <quinox> From my research it looks like PAM is a bit annoying as you can't have two separet SSHd running that use different PAM setups
| |
18:28 | but, with the right mix of require/requisite settings I think I can hook up a script that uses the IP address to skip TOTP
| |
18:28 | Having TOTP inside LDM would be pretty sweet though
| |
18:29 | <alkisg> And password expiry handling too
| |
18:29 | I don't think it would need a big patch there, just couple stdio with the input box
| |
18:30 | <quinox> the simple (most robust) implementation would simply show whatever the server sends back with an input field until the login is done
| |
18:30 | <alkisg> Dlkauf: do try what I suggested, it's a lot different from putty, e.g. it checks your ssh keys in the ltsp client that way
| |
18:30 | quinox: yup
| |
18:31 | <quinox> the ssh client knows when the auth phase is completed, but I don't know how you can determine that by scraping the output
| |
18:31 | <alkisg> We run `ssh server echo LTSPROCKS` and check when we see that LTSPROCKS sentinel
| |
18:32 | !ltsprocks
| |
18:32 | <ltsp`> Error: "ltsprocks" is not a valid command.
| |
18:32 | <quinox> ah, exellent
| |
18:32 | <alkisg> Meh :D
| |
18:44 | alkisg is now known as work_alkisg | |
18:46 | robb_nl has joined IRC (robb_nl!~robb_nl@ip-213-49-85-168.dsl.scarlet.be) | |
18:59 | lbssousa has left IRC (lbssousa!~laercio@177.143.0.126, Quit: lbssousa) | |
19:11 | <Dlkauf> ok am I going to have to do this from the server itself?
| |
19:35 | Faith has left IRC (Faith!~paty_@143.107.231.49, Quit: Leaving) | |
19:45 | flip_ has joined IRC (flip_!027fd6d0@gateway/web/freenode/ip.2.127.214.208) | |
19:46 | <flip_> wow, i wasn't expecting so many people
| |
19:49 | <gehidore> all 48 of us?
| |
19:49 | <flip_> ; )
| |
19:50 | I was wondering if anyone here has experience using ltsp for 'high end' gaming
| |
19:51 | when i say high end... around 1gb gddr5
| |
20:07 | <vagrantc> almost certainly want fat clients
| |
20:07 | probably not with sshfs homedirs, although that may depend on if the game hits the homedir a lot
| |
20:18 | <||cw> does sshfs not cache well?
| |
20:30 | <vagrantc> it's got encryption overhead, network overhead ... depending on what kind of performance you need/want, it may not be the best bet
| |
20:31 | a local tmpfs would give the best performance, if you've got the ram for it
| |
20:31 | and don't need data persistance
| |
20:36 | <flip_> ok, thanks, I'll work on find out more info before coming back
| |
20:36 | *finding
| |
20:41 | flip_ has left IRC (flip_!027fd6d0@gateway/web/freenode/ip.2.127.214.208, Ping timeout: 252 seconds) | |
20:45 | Softeisbieger has left IRC (Softeisbieger!~Softeisbi@dsl37-152-183.pool.bitel.net, Remote host closed the connection) | |
20:59 | ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving) | |
21:06 | robb_nl has left IRC (robb_nl!~robb_nl@ip-213-49-85-168.dsl.scarlet.be, Remote host closed the connection) | |
21:35 | gp has joined IRC (gp!~gp@104-14-168-137.lightspeed.rcsntx.sbcglobal.net) | |
22:14 | ben_roose has left IRC (ben_roose!~roose@roose.cs.wichita.edu, Remote host closed the connection) | |
23:27 | gp has left IRC (gp!~gp@104-14-168-137.lightspeed.rcsntx.sbcglobal.net, Quit: Leaving) | |