00:15 | GodFather has left IRC (GodFather!~rcc@47.33.250.142, Remote host closed the connection) | |
00:16 | GodFather has joined IRC (GodFather!~rcc@47.33.250.142) | |
01:01 | GodFather has left IRC (GodFather!~rcc@47.33.250.142, Remote host closed the connection) | |
01:03 | GodFather has joined IRC (GodFather!~rcc@47.33.250.142) | |
01:07 | GodFather has joined IRC (GodFather!~rcc@47.33.250.142) | |
01:12 | GodFather has joined IRC (GodFather!~rcc@47.33.250.142) | |
01:39 | GodFather has left IRC (GodFather!~rcc@47.33.250.142, Remote host closed the connection) | |
01:42 | GodFather has joined IRC (GodFather!~rcc@47.33.250.142) | |
01:53 | Statler_ has joined IRC (Statler_!~Georg@p579FEC8C.dip0.t-ipconnect.de) | |
01:54 | GodFather has left IRC (GodFather!~rcc@47.33.250.142, Remote host closed the connection) | |
01:57 | Statler has left IRC (Statler!~Georg@p579FEB6B.dip0.t-ipconnect.de, Ping timeout: 255 seconds) | |
01:57 | <dragon788> have you guys looked at using the Ubuntu cloud images as the base @vagrantc ?
| |
01:58 | <vagrantc> would make it hard to use Debian :P
| |
01:59 | GodFather has joined IRC (GodFather!~rcc@47.33.250.142) | |
01:59 | <vagrantc> likely to move things towards ltsp-pnp chrootless installs being the default/recommended method for installing LTSP in the future
| |
02:00 | to bring it in sync with practice of the recommendations we've been making it
| |
02:01 | but there are some use-cases for chroots like alternate architectures (e.g. i386 and/or armhf clients, amd64 server), so we'll want to have some documentation showing how to support something like that
| |
02:08 | GodFather has left IRC (GodFather!~rcc@47.33.250.142, Quit: Ex-Chat) | |
02:08 | GodFather has joined IRC (GodFather!~rcc@47.33.250.142) | |
02:14 | GodFather has left IRC (GodFather!~rcc@47.33.250.142, Ping timeout: 260 seconds) | |
02:22 | <dragon788> lol, this is true, are there Debian cloud images?
| |
02:22 | is there a roadmap on the site that shows the intended workflows?
| |
02:24 | <vagrantc> roadmap would be ambitious
| |
02:25 | http://wiki.ltsp.org/wiki/Dev:LTSPPamNotes
| |
02:25 | that's for the "kill off LDM" part
| |
02:26 | there are also plans to replace lts.conf with ltspd ...
| |
02:26 | <dragon788> hmmm
| |
02:26 | <vagrantc> and goodbye ltsp-build-client
| |
02:26 | vervelak has left IRC (vervelak!~vervelak@139.91.200.185, Ping timeout: 252 seconds) | |
02:26 | <dragon788> any reason you couldn't build an image in Docker and then export the tar, other than it's probably missing some essentials bits like drivers unless you make a "fat" docker?
| |
02:28 | <vagrantc> the whole point of the new approach is you can build the image any way you want
| |
02:28 | <dragon788> having never used LTSP other than probably through a fork or whatever "NoTouch" has done to make a similar thin client solution
| |
02:28 | oh nice!
| |
02:28 | <vagrantc> the default basically being that you install your server with whatever applications you want available to the clients, and then build the image out of the server's install
| |
02:28 | <dragon788> I'd probably end up using Packer to output some sort of image then, I really like "infrastructure as code"
| |
02:28 | <vagrantc> sanitizing some things, of course
| |
02:29 | container tools might likely miss some key things needed for full-blown OS images, like you mentioned
| |
02:30 | <dragon788> I mostly fell in here because of my interest in PiNet, but I also volunteer at a tech camp where the kids have laptops but could also utilize more powerful machines for some tasks if there was an easy way to set things up (LTSP ftw)
| |
02:30 | <vagrantc> thin clients tend to be pretty underwhelming, these days
| |
02:31 | software just isn't written in a way that makes it work anymore
| |
02:31 | and "just web browsing" is a full multi-media platform these days.
| |
02:31 | <dragon788> yeah, and really Chromebooks ARE thin clients, the server just happens to be the webb
| |
02:32 | <vagrantc> so, LTSP fat clients by default for the future ... which really reduces the server load
| |
02:32 | <dragon788> the main place I'd see the thin client model still working is in classrooms where you want all the students to have the same resources and have it easy to reset, though Clonezilla/DRBL make that pretty quick work with even small SSDs anymore
| |
02:32 | <vagrantc> and any hardware produced in the last 5-7 years will probably perform better as a fat client anyways
| |
02:33 | dragon788: that's still feasible with LTSP fat clients
| |
02:33 | dragon788: they're still network booted off of a single OS image
| |
02:33 | i *thought* pinet defaulted to fat clients
| |
02:34 | <dragon788> yeah, I haven't set it up yet but I got the impression it loads the OS to RAM or local cache rather than being a true "thin" client
| |
02:34 | <vagrantc> there are some ideas kicking around to also cache the image to local media, and update it as-needed.
| |
02:34 | dragon788: i'm pretty sure they use LTSP's fat client support.
| |
02:36 | <dragon788> ahh yeah, Novell Zenworks has an option like that for reimaging machines, they maintain a small "maintenance" partition that holds the image that you can use to refresh the OS, you can choose whether to just blow away the OS or only update the imaging partition when you run operations against a system
| |
02:42 | vervelak has joined IRC (vervelak!~vervelak@139.91.200.185) | |
02:44 | <vagrantc> biggest problem is just getting enough free time to implement all this stuff, of course
| |
02:44 | we've gotten a lot of stuff proof-of-concepted ... but haven't spent the time to take it much past that
| |
03:20 | lucascastro has joined IRC (lucascastro!~lucas@186.227.186.18) | |
03:31 | lucascastro has left IRC (lucascastro!~lucas@186.227.186.18, Ping timeout: 240 seconds) | |
03:32 | lucascastro has joined IRC (lucascastro!~lucas@186.227.186.18) | |
04:18 | Freejack has left IRC (Freejack!~Freejack@unaffiliated/freejack, Ping timeout: 255 seconds) | |
04:23 | Freejack has joined IRC (Freejack!~Freejack@unaffiliated/freejack) | |
04:25 | ricotz has joined IRC (ricotz!~ricotz@p5B2A90DF.dip0.t-ipconnect.de) | |
04:25 | ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz) | |
04:36 | Statler_ has left IRC (Statler_!~Georg@p579FEC8C.dip0.t-ipconnect.de, Quit: Leaving) | |
04:37 | Statler has joined IRC (Statler!~Georg@p579FEC8C.dip0.t-ipconnect.de) | |
05:10 | alkisg has joined IRC (alkisg!~alkisg@srv1-dide.ioa.sch.gr) | |
05:10 | alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg) | |
05:26 | vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving) | |
06:06 | jgee has left IRC (jgee!~jgee@200.118.140.142, Remote host closed the connection) | |
06:39 | mikkel has joined IRC (mikkel!~mikkel@mail.dlvs.dk) | |
08:06 | Statler has left IRC (Statler!~Georg@p579FEC8C.dip0.t-ipconnect.de, Remote host closed the connection) | |
08:37 | Statler has joined IRC (Statler!~Georg@mail.lohn24.de) | |
10:01 | markus_e92 has left IRC (markus_e92!~markus_e9@80-121-123-122.adsl.highway.telekom.at, Ping timeout: 240 seconds) | |
10:04 | markus_e92 has joined IRC (markus_e92!~markus_e9@91-115-153-12.adsl.highway.telekom.at) | |
10:09 | NecTal has joined IRC (NecTal!c27e6a95@gateway/web/freenode/ip.194.126.106.149) | |
10:18 | NecTal has left IRC (NecTal!c27e6a95@gateway/web/freenode/ip.194.126.106.149, Ping timeout: 260 seconds) | |
10:28 | GodFather has joined IRC (GodFather!~rcc@96-92-43-9-static.hfc.comcastbusiness.net) | |
11:21 | markus_e92 has left IRC (markus_e92!~markus_e9@91-115-153-12.adsl.highway.telekom.at, Ping timeout: 252 seconds) | |
11:24 | markus_e92 has joined IRC (markus_e92!~markus_e9@91-115-153-12.adsl.highway.telekom.at) | |
11:49 | gp has left IRC (gp!~gp@104-14-168-137.lightspeed.rcsntx.sbcglobal.net, Quit: Leaving) | |
13:11 | ZAJDAN has left IRC (ZAJDAN!4d30954b@gateway/web/freenode/ip.77.48.149.75, Ping timeout: 260 seconds) | |
13:51 | GodFather has left IRC (GodFather!~rcc@96-92-43-9-static.hfc.comcastbusiness.net, Ping timeout: 260 seconds) | |
13:52 | Faith has joined IRC (Faith!~paty_@unaffiliated/faith) | |
13:55 | ben_roose has joined IRC (ben_roose!~roose@roose.cs.wichita.edu) | |
14:02 | mikkel has left IRC (mikkel!~mikkel@mail.dlvs.dk, Quit: Leaving) | |
14:05 | GodFather has joined IRC (GodFather!~rcc@75-145-237-204-Michigan.hfc.comcastbusiness.net) | |
15:41 | eu^dyndsl-092-25 has joined IRC (eu^dyndsl-092-25!5cfc4816@gateway/web/freenode/ip.92.252.72.22) | |
15:41 | <eu^dyndsl-092-25> hi.
| |
15:41 | anybody here?
| |
15:45 | need some help with epoptes ...
| |
15:54 | <alkisg> eu^dyndsl-092-25: what help?
| |
16:03 | lucas_ has joined IRC (lucas_!~lucas@186.227.186.18) | |
16:04 | lucascastro has left IRC (lucascastro!~lucas@186.227.186.18, Ping timeout: 240 seconds) | |
16:05 | Statler has left IRC (Statler!~Georg@mail.lohn24.de, Remote host closed the connection) | |
16:19 | <eu^dyndsl-092-25> I want epoptes to run like this: epoptes-client starts and STILL runs when a user has logged off
| |
16:19 | it doesn't work here...
| |
16:19 | ben_roose has left IRC (ben_roose!~roose@roose.cs.wichita.edu, Ping timeout: 240 seconds) | |
16:23 | <eu^dyndsl-092-25> it's like this: the process "/usr/bin/python /usr/bin/twistd --pidfile /var/run/epoptes.pid --logfile /var/log/epoptes.log epoptes" runs as root and keeps running
| |
16:24 | but the process "socat -T 60 openssl-connect: ..." stops running when a User logs off. So I cant use epoptes to run remote commands any more ... no connection any more
| |
16:29 | <alkisg> eu^dyndsl-092-25: twistd is the epoptes server
| |
16:29 | But you're talking about epoptes client
| |
16:29 | So I don't understand what is it that you want...
| |
16:30 | There are 2 epoptes-client processes. One for the system, which runs even before login
| |
16:30 | And one for the session (user), which runs after login and exits at logout
| |
16:31 | So, you are supposed to have access to all the clients through the root epoptes-client process, even if they have logged out
| |
16:31 | Are you running LTSP (netbooted clients)?
| |
16:40 | * alkisg notices there's a half an our lag between replies... :D | |
16:40 | <alkisg> *hour
| |
16:42 | <gehidore> such is the world of IRC
| |
16:59 | GodFather has left IRC (GodFather!~rcc@75-145-237-204-Michigan.hfc.comcastbusiness.net, Ping timeout: 260 seconds) | |
17:03 | markus_e92 has left IRC (markus_e92!~markus_e9@91-115-153-12.adsl.highway.telekom.at, Ping timeout: 258 seconds) | |
17:05 | markus_e92 has joined IRC (markus_e92!~markus_e9@91-115-153-12.adsl.highway.telekom.at) | |
17:16 | Faith has left IRC (Faith!~paty_@unaffiliated/faith, Quit: Leaving) | |
17:57 | Statler has joined IRC (Statler!~Georg@p579FEC8C.dip0.t-ipconnect.de) | |
18:07 | <eu^dyndsl-092-25> ok. we are talking about the epoptes-clients, you're right. I heard about a way to control the clients from the "master-client" even if no user is logged in. And that does not work here...
| |
18:08 | and no: there's no LTSP running here
| |
18:09 | (sorry, ... of course no lag but simply afk :))
| |
18:11 | lucas_ has left IRC (lucas_!~lucas@186.227.186.18, Remote host closed the connection) | |
18:12 | <eu^dyndsl-092-25> and you're right: the process which keeps running is twistd ...
| |
18:14 | but I nevertheless can't control any client as soon as no user is logged in any more. The icon of these client change to something like a "switched off" sign
| |
18:30 | <alkisg> eu^dyndsl-092-25: see this image: http://ts.sch.gr/mediawiki/images/b/b3/0.5.7_epoptes_startup.png
| |
18:30 | Logged on clients show thumbnails
| |
18:30 | Logged of clients are green (thin clients), blue (fat clients) or red (standalone clients)
| |
18:30 | If your don't see red "monitors" when they're logged off, your setup is wrong
| |
18:30 | <eu^dyndsl-092-25> no, here it looks like this: https://ask.linuxmuster.net/uploads/default/original/1X/a858f90d17f8bafcf77365671382fec842f10018.png
| |
18:31 | <alkisg> I don't see logged of clients there
| |
18:31 | !vnc-edide
| |
18:31 | <ltsp> vnc-edide: To share your screen with me, open Epoptes → Help menu → Remote support → Host: srv1-dide.ioa.sch.gr, and click the Connect button
| |
18:31 | <alkisg> If you want, share your screen with me to see why.
| |
18:32 | <eu^dyndsl-092-25> the 3 clients at the beginning are STILL running ... but epoptes thinks that they are switched OFF
| |
18:32 | <alkisg> It might be a bug or it might be a misconfiguration
| |
18:32 | I can take a look if you want
| |
18:33 | <eu^dyndsl-092-25> no possible from here. the setup does not run ... it's a school
| |
18:33 | <alkisg> I maintain 1000+ schools, but I don't understand what "the setup does not run" mean
| |
18:33 | <eu^dyndsl-092-25> sorry, no client is running at the moment
| |
18:33 | <alkisg> If you mean that you don't have access now, then come some other time when you do have access
| |
18:34 | Do you have access to the server?
| |
18:34 | <eu^dyndsl-092-25> only via ssh
| |
18:35 | ah, you mean the epoptes-"main-"client now, right?
| |
18:35 | the one from where to control the rest? no that one is switched off as well at the moment
| |
18:35 | <alkisg> The epoptes server is the main pc which runs the epoptes GUI
| |
18:35 | <eu^dyndsl-092-25> ok, in that case: NO.
| |
18:35 | <alkisg> OK, then come back when you have access there
| |
18:36 | <eu^dyndsl-092-25> where are you? any time-shift to germany?
| |
18:36 | <alkisg> Greece, 2 hours difference
| |
18:36 | <eu^dyndsl-092-25> ok. no problem then.
| |
18:37 | should th process "socat ..." still run when a user has logged out?
| |
18:37 | maybe that's the problem?!
| |
18:37 | <alkisg> There are 2 socat processes
| |
18:37 | One runs as root, one as user
| |
18:37 | So the one as root is supposed to run, yes
| |
18:37 | <eu^dyndsl-092-25> ok, then that's the problem
| |
18:38 | here's just one
| |
18:38 | <alkisg> Which distro/version is that?
| |
18:38 | <eu^dyndsl-092-25> ubuntu 16.04 LTS
| |
18:38 | <alkisg> Maybe you have misconfigured networking
| |
18:38 | <eu^dyndsl-092-25> and the root process should be there when the system starts, right?
| |
18:38 | <alkisg> And your network only runs after login
| |
18:38 | This is a setting in network manager, unrelated to epoptes
| |
18:39 | <eu^dyndsl-092-25> network works fine as the clients are booting via DHCP --> PXE --> LINBO --> UBUNTU
| |
18:39 | <alkisg> What is linbo/
| |
18:39 | ?
| |
18:39 | Maybe that's the one that has issues...
| |
18:40 | Because you say "it works fine", and i hear "it breaks if-up events"
| |
18:41 | <eu^dyndsl-092-25> it's a software to repair clients over the net ... I'm quite sure that it has nothing to do with that
| |
18:41 | <alkisg> Does it manage networking?
| |
18:41 | <eu^dyndsl-092-25> yes, it's online ... IP is correct
| |
18:41 | <alkisg> OK, then that's the problem
| |
18:41 | It breaks the network if-up events
| |
18:41 | LTSP had that issue too until I fixed it
| |
18:42 | (LTSP also manages the network)
| |
18:42 | Epoptes runs from if-up, so because of limbo bugs, it never runs
| |
18:42 | The bug is in linbo
| |
18:42 | <eu^dyndsl-092-25> but after linbo the "normal" ubuntu kernel is booting ... and the network connection is made again via ubuntu
| |
18:42 | <alkisg> Do the clients have local disks?
| |
18:42 | <eu^dyndsl-092-25> yes
| |
18:43 | normal clients with ssd hdd
| |
18:43 | <alkisg> What is the output of `cat /etc/network/interfaces`?
| |
18:44 | <eu^dyndsl-092-25> "nothing" ... just # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback
| |
18:44 | <alkisg> Is that on a client, or on the server?
| |
18:45 | <eu^dyndsl-092-25> it's a client. nothing configured there. but as the server ist the same image it will be the same there
| |
18:45 | <alkisg> And you're certain that linbo doesn't write to that file/
| |
18:45 | ?
| |
18:46 | A second question would be, what is the output of `ls /etc/NetworkManager/system-connections/` ?
| |
18:46 | <eu^dyndsl-092-25> no. I'm sure. linbo is using its own kernel
| |
18:47 | ls /etc/NetworkManager/system-connections/ --> nothing
| |
18:47 | <alkisg> Then you don't have a network before login
| |
18:47 | Are you using network manager?
| |
18:48 | <eu^dyndsl-092-25> ok, that's possible. Often the connection is made when lightdm is already there ... ... a little icon on the top right corner ...
| |
18:48 | two arrows when connected
| |
18:49 | <alkisg> The epoptes-client root process runs from /etc/network/if-up.d
| |
18:49 | Network manager calls that when it gets online
| |
18:49 | To have networking before login, you need to check the "allow connection for all users" or something
| |
18:49 | (in the connection dialog)
| |
18:49 | This then writes the connection to /etc/NetworkManager/system-connections
| |
18:50 | <eu^dyndsl-092-25> ok. so the problem is on ubuntu-side, ja?
| |
18:50 | <alkisg> The result is that the client always has a connection, even when it's logged out, and you can see it in epoptes
| |
18:50 | I believe so. Client access would be required to verify it.
| |
18:50 | <eu^dyndsl-092-25> Ok! I will try this, ok? maybe it helps
| |
18:51 | otherwise I'll reconnect and we can try it with a remote-admin-session, ok?
| |
18:52 | <alkisg> Those check boxes: https://farm8.staticflickr.com/7776/17325199982_801290e172_z.jpg
| |
18:52 | Sure, if you find me available...
| |
18:52 | <eu^dyndsl-092-25> ok. thank you for support
| |
18:52 | I will try it!
| |
18:52 | <alkisg> You're welcome
| |
18:53 | <eu^dyndsl-092-25> would be great if that was the solution!
| |
18:53 | epoptes is really great! Fast and stable! Good work :)
| |
18:53 | <alkisg> :)
| |
18:53 | Let's hope funding is found to continue it
| |
18:54 | <eu^dyndsl-092-25> yes! Have to go now.... cu and thanks
| |
18:54 | <alkisg> bb
| |
18:54 | eu^dyndsl-092-25 has left IRC (eu^dyndsl-092-25!5cfc4816@gateway/web/freenode/ip.92.252.72.22, Quit: Page closed) | |
19:35 | SharpTrickster has joined IRC (SharpTrickster!b115352d@gateway/web/freenode/ip.177.21.53.45) | |
19:37 | ben_roose has joined IRC (ben_roose!~roose@roose.cs.wichita.edu) | |
19:45 | <SharpTrickster> hi, im reading the documentation on PiNet and LTSP and I was wondering if anyone was sucessful creating a PC server with RetroPie image and shared ROM files to boot several Raspberry Pis on a switch
| |
19:46 | any advices or suggestions on this one?
| |
19:50 | SharpTrickster has left IRC (SharpTrickster!b115352d@gateway/web/freenode/ip.177.21.53.45, Ping timeout: 260 seconds) | |
19:54 | Statler has left IRC (Statler!~Georg@p579FEC8C.dip0.t-ipconnect.de, Remote host closed the connection) | |
20:53 | GodFather has joined IRC (GodFather!~rcc@47.33.250.142) | |
21:59 | ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving) | |
23:07 | ben_roose has left IRC (ben_roose!~roose@roose.cs.wichita.edu, Remote host closed the connection) | |