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


Channel log from 3 April 2019   (all times are UTC)

01:10vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Ping timeout: 240 seconds)
01:12jgee has left IRC (jgee!~jgee@190.159.118.121, Quit: Ping timeout (120 seconds))
01:13jgee has joined IRC (jgee!~jgee@190.159.118.121)
01:13vsuojanen has left IRC (vsuojanen!~vsuojanen@cable-hml-585686-205.dhcp.inet.fi, Ping timeout: 245 seconds)
01:57vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
02:05vsuojanen has joined IRC (vsuojanen!~vsuojanen@cable-hml-585686-205.dhcp.inet.fi)
04:13quinox has left IRC (quinox!~quinox@ghost.qtea.nl, Quit: WeeChat 2.2)
04:16quinox has joined IRC (quinox!~quinox@ghost.qtea.nl)
05:12
<alkisg>
vagrantc: what's the recommended license these days? gpl 3+?
05:12
(for the new ltsp)
05:39statler has joined IRC (statler!~Georg@p5489790B.dip0.t-ipconnect.de)
05:40
<vagrantc>
alkisg: gpl3+ has some positive things, definitely
05:40
maybe even agpl
05:42
<alkisg>
Thanks, putting this then: # SPDX-License-Identifier: GPL-3.0-or-later
05:47os_a has joined IRC (os_a!~Thunderbi@195.112.116.22)
05:54kjackal has joined IRC (kjackal!~quassel@2a02:587:3119:ef00:8593:ced4:afeb:e172)
06:02ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)
06:03os_a has left IRC (os_a!~Thunderbi@195.112.116.22, Read error: Connection reset by peer)
06:05os_a has joined IRC (os_a!~Thunderbi@141.101.206.111.leadertelecom.ru)
06:13woernie has joined IRC (woernie!~werner@46.189.28.76)
06:15julien has joined IRC (julien!~julien@141.138.180.162)
06:16julien is now known as Guest68778
06:53os_a1 has joined IRC (os_a1!~Thunderbi@195.112.116.22)
06:54os_a has left IRC (os_a!~Thunderbi@141.101.206.111.leadertelecom.ru, Ping timeout: 245 seconds)
06:54os_a1 is now known as os_a
07:37Guest68778 has left IRC (Guest68778!~julien@141.138.180.162, Remote host closed the connection)
07:50Da-Geek has joined IRC (Da-Geek!~Da-Geek@212.183.131.194)
07:58julien has joined IRC (julien!~julien@141.138.180.162)
07:59julien is now known as Guest60592
08:10Guest60592 has left IRC (Guest60592!~julien@141.138.180.162, Remote host closed the connection)
08:24statler has left IRC (statler!~Georg@p5489790B.dip0.t-ipconnect.de, Remote host closed the connection)
09:01julien has joined IRC (julien!~julien@141.138.180.162)
09:01julien is now known as Guest5555
09:05Guest5555 has left IRC (Guest5555!~julien@141.138.180.162, Remote host closed the connection)
09:40alkisg has left IRC (alkisg!~alkisg@ubuntu/member/alkisg, Quit: Leaving.)
09:53statler has joined IRC (statler!~Georg@gwrz.lohn24.de)
10:00julien has joined IRC (julien!~julien@141.138.180.162)
10:00julien is now known as Guest98370
10:13vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving)
10:14woernie has left IRC (woernie!~werner@46.189.28.76, Ping timeout: 268 seconds)
10:15woernie has joined IRC (woernie!~werner@46.189.28.81)
10:18Guest98370 has left IRC (Guest98370!~julien@141.138.180.162, Remote host closed the connection)
10:27alkisg has joined IRC (alkisg!~alkisg@ubuntu/member/alkisg)
10:49os_a has left IRC (os_a!~Thunderbi@195.112.116.22, Quit: os_a)
11:26julien has joined IRC (julien!~julien@141.138.180.162)
11:27julien has left IRC (julien!~julien@141.138.180.162, Remote host closed the connection)
11:27julien has joined IRC (julien!~julien@141.138.180.162)
11:27julien is now known as Guest88752
11:47Faith has joined IRC (Faith!~Paty_@unaffiliated/faith)
12:24Guest88752 has left IRC (Guest88752!~julien@141.138.180.162, Remote host closed the connection)
12:27clef__ has joined IRC (clef__!6d1dea72@gateway/web/freenode/ip.109.29.234.114)
12:32
<clef__>
Hello, I've an Android phone and I would like to connect it to a thin client usb to access internal storage. Is it possible ?
12:43
<alkisg>
Sure, with localapps
12:59
<clef__>
Great ! Which application could this work ? Localapps is already enabled. (LOCAL_APPS_MENU=True)
13:01spaced0ut has left IRC (spaced0ut!~spaced0ut@unaffiliated/spaced0ut, Quit: Leaving)
13:02julien has joined IRC (julien!~julien@141.138.180.162)
13:02julien is now known as Guest73068
13:14spaced0ut has joined IRC (spaced0ut!~spaced0ut@unaffiliated/spaced0ut)
13:41Guest73068 has left IRC (Guest73068!~julien@141.138.180.162, Remote host closed the connection)
13:47jgee has left IRC (jgee!~jgee@190.159.118.121, Ping timeout: 246 seconds)
13:49jgee has joined IRC (jgee!~jgee@190.159.118.121)
14:03julien has joined IRC (julien!~julien@141.138.180.162)
14:04julien is now known as Guest40148
14:15Guest40148 has left IRC (Guest40148!~julien@141.138.180.162, Remote host closed the connection)
14:25kjackal has left IRC (kjackal!~quassel@2a02:587:3119:ef00:8593:ced4:afeb:e172, Ping timeout: 258 seconds)
14:25kjackal has joined IRC (kjackal!~quassel@2a02:587:3119:ef00:8593:ced4:afeb:e172)
14:31adrianorg has joined IRC (adrianorg!~adrianorg@177.18.100.154)
14:34adrianor1 has left IRC (adrianor1!~adrianorg@187.115.106.242, Ping timeout: 250 seconds)
14:38clef__ has left IRC (clef__!6d1dea72@gateway/web/freenode/ip.109.29.234.114, Ping timeout: 256 seconds)
15:04julien has joined IRC (julien!~julien@141.138.180.162)
15:04julien is now known as Guest82233
15:08Da-Geek has left IRC (Da-Geek!~Da-Geek@212.183.131.194, Remote host closed the connection)
15:54Guest82233 has left IRC (Guest82233!~julien@141.138.180.162, Remote host closed the connection)
16:17woernie has left IRC (woernie!~werner@46.189.28.81, Remote host closed the connection)
16:25julien has joined IRC (julien!~julien@141.138.180.162)
16:25julien is now known as Guest7936
16:38Guest7936 has left IRC (Guest7936!~julien@141.138.180.162, Remote host closed the connection)
16:40quagmire has joined IRC (quagmire!82c03034@gateway/web/freenode/ip.130.192.48.52)
16:43
<quagmire>
Hi everyone, I am using LTSP on ubuntu 18.04 and I am having problems with using local devices (particularly USB keys) with thin clients.
16:44
I did set LOCALDEV=True in the lts.conf file but the situation doesn't change
16:45
<mwalters>
are you able to mount them w/ a local terminal?
16:45
e.g., `ltsp-localapps sensible-terminal` ?
16:45
or with a locally run file manager
16:46
not sure if sensible terminal stuff gets put in a thin chroot
16:46
<quagmire>
The clients can mount the USB keys, but they can't unmount them
16:47
<mwalters>
not sure about that
16:47
<quagmire>
The server, when a USB key is inserted makes a polkit error popup on all clients, about "org.freedesktop.udisks2.filesystem-mount-other-seat"
16:47
<mwalters>
do you get an access denied error when trying to unmount them?
16:48
pretty sure regular users need to be in a particular group for removeable devices on ubuntu
16:48
(to mount/unmount)
16:49
<quagmire>
yes, I get an "access denied" error
16:49
<mwalters>
not sure how this works/relates to thinclients
16:49
plugdev I think?
16:49
<quagmire>
I already tried adding all users to the "fuse" and "plugdev" group and the result is the same
16:50
<mwalters>
that's likely only making them members on the server
16:50
man lts.conf
16:50
ops
16:52
Not really sure... it probably "should work"... I think most of the devs are using fat clients now, though
16:58
<quagmire>
that is a problem for us, since we have installed over 500 thin clients in 35 laboratories, as you can see here: http://www.ltsp.org/stories/viewstory/?story_id=975&secret=40e329
17:00
<mwalters>
are you able to unmount it manually using a local terminal?
17:02
<quagmire>
I did open a local terminal using epoptes but it says that the device is not mounted. I can even mount it at the same time in the local OS and have write access on it. After that I can unmount it (but only in the local OS)
17:03
<mwalters>
anything useful in /var/log/syslog on the client?
17:06lopta has joined IRC (lopta!~ball@74-84-114-18.client.mchsi.com)
17:09
<quagmire>
didn't find anything useful
17:09
<mwalters>
sorry, not really sure. I don't have a way to test thin clients atm
17:09
wait around for a while and I'm sure someone smarter will chime in
17:09
<alkisg>
quagmire: may I ask why you're using thin clients instead of fat ones? Are your clients that slow/old?
17:10
<mwalters>
speak of the devil
17:10
<alkisg>
O:-)
17:10
<quagmire>
yes, both
17:10
<alkisg>
I.e. which cpu and how much ram?
17:12
<quagmire>
they vary from pentium to dual core maximum, with 256MB ram
17:12
<mwalters>
alkisg: any thoughts to running the ltsp server in a container (e.g., lxc)?
17:12
<alkisg>
Pentium 4's from 2.4 GHz and on, and dual core PCs work better as fat, provided they have at least 768 RAM
17:12
<mwalters>
might try it here in a while, but curious if you've explored it at all
17:13
<alkisg>
In any case, if you're talking about ltspfs and thin clients, there's no unmounting,
17:13
ltspfs syncs every two seconds, so you just need to wait 2 secs and then unplug the stick
17:13
<lopta>
Do "fat clients" get updated automatically by the server?
17:13
<alkisg>
mwalters: I don't know of any issues, but I'm not using virtualized ltsp servers in production
17:14
!fatclients
17:14
<ltsp>
fatclients: Nowadays LTSP supports thin and fat clients. They are both diskless and netbooted from the same LTSP chroot, but while thin clients run the session on the server and transfer the screen, fat clients run the session locally with their own CPU/RAM, thus performing amazingly better. See also !ltsp-pnp and https://help.ubuntu.com/community/UbuntuLTSP/FatClients
17:14
<lopta>
(I'm guessing they have their own Web browser?)
17:14
<mwalters>
cool, I'll report back if I run into anything
17:14
<alkisg>
lopta: it's just an ltsp-update-image -c /
17:14
<lopta>
Thanks alkisg
17:14
<alkisg>
I.e. they still don't have disks; they netboot the image from the server
17:14
The whole idea of ltsp is that you only need to maintain one or two images, not a lot of installations
17:15
<lopta>
alkisg: That is an appealing idea.
17:15
<alkisg>
!install
17:15
<ltsp>
install: http://wiki.ltsp.org/wiki/Installation/Ubuntu for Ubuntu, or http://wiki.ltsp.org/wiki/Installation for other distributions
17:15
<alkisg>
lopta: try a test installation some time, it takes 1 hour including the os installation
17:15
Follow the steps blindly
17:15
And customize later on...
17:15statler has left IRC (statler!~Georg@gwrz.lohn24.de, Remote host closed the connection)
17:16
<lopta>
I'll need a spare server and switch.
17:16
brb
17:16
<quagmire>
I don't get it: the ltspfs "fakes" mounting but actually just remembers what to do on a usb stick and syncs it every 2 seconds?
17:18
<alkisg>
quagmire: well it needs to "fake" mounting since the process runs on the server and the stick is on the client
17:18
So yup, what you said
17:18
Note that thin clients are getting deprecated, they won't be supported in the next ltsp version
17:18
So people that need them should switch to ltsp for netbooting and xfreerdp/xrdp or something for the remote desktop part
17:19
So, ltspfs will be replaced by xfreerdp folder sharing
17:20* lopta looks up xfreerdp
17:22
<alkisg>
lopta: your clients are pentium 4 and lower?
17:22
If not, ....just ignore thin clients :)
17:23
<lopta>
alkisg: I don't have any clients yet, though I have a pallet full of dual-core i5 machines that could probably do the job at a push.
17:23
(i5 and i3, I think)
17:23
<alkisg>
lopta: right, so completely ignore any mentions of thin clients
17:23
Go for fat ones, what we said previously
17:24
<lopta>
alkisg: For fat clients, presumably the terminal network would have to be routed out to the Internet.
17:24
(if I want people to be able to browse the Web, etc.)
17:25
<alkisg>
I'm not sure what you mean by that. Thin clients are remote desktop, fat clients are remote disk.
17:25
Both are netbooted
17:25* lopta nods
17:25
<alkisg>
Your ltsp server will be remote, over WAN?
17:26
<lopta>
alkisg: No, I was thinking the terminals would connect to the server over a separate Ethernet
17:26
...but I'm used to running the applications on the server.
17:26
<alkisg>
Networking is the same in both cases
17:26
It can be either single or dual nic
17:26julien has joined IRC (julien!~julien@141.138.180.162)
17:27julien is now known as Guest84172
17:27
<lopta>
Well in the thin client case the Internet doesn't have to be connected to the terminal LAN
17:27
...for thick clients it would have to be. That's not necessarily a problem, just a consideration.
17:27
fat clients, I mean.
17:27
<alkisg>
you can still do nat for fat clients
17:28
<lopta>
alkisg: Right but you wouldn't have to for thin clients.
17:30
<quagmire>
To solve my problem with USB keys, would it be possible to do a script to launch manually? If yes, where should I start from?
17:30
<lopta>
quagmire: I missed your question but are you plugging USB flash drives into the terminals?
17:32
<quagmire>
lopta: yes and the clients can operate on usb keys but can't unmount them. The server cannot do that as plugging a usb key pops up an form asking for the admin password on all clients
17:33
<lopta>
quagmire: I'm guessing there's a way to configure on the server what happens when a flash drive is plugged into a terminal.
17:33
(mount it, ignore it or prompt?)
17:39vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
17:44
<alkisg>
(08:28:18 PM) lopta: alkisg: Right but you wouldn't have to for thin clients. => sure but you're doing a whole remote desktop, much more expensive network-wise
17:46quagmire has left IRC (quagmire!82c03034@gateway/web/freenode/ip.130.192.48.52)
17:49
<lopta>
alkisg: In terms of network bandwidth? Sure.
17:50
<mwalters>
https://store.ui.com/products/edgerouter-x
17:50
just a little bit more than a gbnic
17:52
<alkisg>
lopta: not sure why you thought that not doing nat is an advantage... less configuration needed? it's automatic anyway
17:53
<lopta>
alkisg: I can think of a few edge cases where I might prefer that. Not many.
17:54
Mostly it's just how I'm used to thinking about thin client deployments.
17:54
For LTSP I'll have to learn the new way.
18:13Leandro_ has joined IRC (Leandro_!c891b51d@gateway/web/freenode/ip.200.145.181.29)
18:14
<Leandro_>
Hello guys. Could anyone please tell me what is the proper way to shutdown clients at a certain time everyday?
18:14
I'm using a chrootless install, and I can't seem to find info about it.
18:15
I tried to config CRONTAB_01 and SHUTDOWN_TIME in lts.conf but none of them worked.
18:15
<mwalters>
http://wiki.ltsp.org/wiki/Tips_and_Tricks/User_Experience#Shutting_down_idle_clients
18:15
That gets you some of the way there
18:15
not sure how you translate that to chrootless, though
18:16
<Leandro_>
I saw that, but that is for a chroot install, isn't it?
18:16
<mwalters>
the file location, yes... those files probably exist in a chrootless install... somewhere, though...
18:16
<vagrantc>
the client doesn't know weather it's created chrootless or with a chroot, all the same to the booted client
18:17
<mwalters>
vagrantc: /opt/ltsp/<arch> won't exist in a chrootless install, though, will it?
18:17
<vagrantc>
right, but it doesn't exist for a booted client either
18:17
<mwalters>
where do the ltsp initialization scripts live on a chrootless install, I think is the relevant question
18:17
(for the client)
18:18
<vagrantc>
same place, minus the /opt/ltsp/<arch> part ... e.g. /
18:18
<mwalters>
cool, so yeah... you could modify that line to check for the current time and shut them down
18:18
<Leandro_>
ok I see. But I'm using autologin, so I don't think I should use rc.d. Fow what I understand, everything in rc.d will run at all time.
18:18
<mwalters>
if you can't get the CRONTAB_01 lines to work
18:19
yeah, you're probably right... that'll only run if ldm is active, and no one is logged in
18:19
<Leandro_>
Yeah, I thought about making that check, but it didn't seem to me that it is the best way to do it.
18:20
I tried using crontab too, but no cigar.
18:20
<mwalters>
looks like CRONTAB_## is only for thin clients
18:21
<Leandro_>
Yeah, I guess so.
18:22
I took /var/spool/cron/crontab out of the excludes file, then I booted a fat client and running "crontab - l" displays the crontab correctly, but it won't run.
18:24
<mwalters>
you could try creating a script in /usr/share/ltsp/init-ltsp.d/ and adding a cron entry from that
18:24
that'll get run when the client boots
18:28
<Leandro_>
what do you mean by creating a script on that folder and adding the cron entry? What that script would do?
18:28
I don't think I follow you thought
18:33
<mwalters>
the script would add the cron entry... e.g., write a file to /etc/cron.daily
18:35
I'm grasping at straws a bit, I've never goofed with a chrootless server
18:35
but that seems like a good way to try
18:36
<vagrantc>
should figure out why CRONTAB_* doesn't work
18:36
rather than implementing workarounds
18:36
<mwalters>
manpage says it's for clients
18:36
eer
18:36
thin clients
18:36
<vagrantc>
there's nothing thin-client specific about it
18:36
<mwalters>
no idea
18:38
<Leandro_>
The CRONTAB_* doesn't work. I looked into /etc/cron.d on a booted client, and there is a file named ltsp there, with the time and command I had set.
18:38
But didnt't run :(
18:38
<vagrantc>
you might also need to add cron to KEEP_SYSTEM_SERVICES
18:39
<Leandro_>
nice! I'll give it a try and will get back with the result shortly
18:44
<mwalters>
systemctl shows cron running without that line in lts.conf
18:44
(on a client)
18:58
<Leandro_>
didn't work :(. Is there a way where I can see if cron is running jobs or not on a client? Cause syslog can't be accessed
18:59
systemctl also show that cron is running here
19:01
To try to be clear. So far I have CRONTAB_01 on my lts.conf, and it "works", it adds a file with the correct command to execute on /etc/cron.d/ on client
19:04
<mwalters>
by default it just throws away the output
19:04
you could have jobs log to file to see if they're doing anything
19:05
* * * * * <user> <command> > /some/file/to/log.to
19:11
<vagrantc>
that should get created before systemd is even started ... odd.
19:12
honestly, i've had problems with cron and systemd in general ...
19:13
maybe try installing systemd-cron ?
19:13
been a long time since i needed any of this
19:42Guest84172 has left IRC (Guest84172!~julien@141.138.180.162, Ping timeout: 246 seconds)
19:54willianmazzardo has joined IRC (willianmazzardo!8f89ef3c@gateway/web/freenode/ip.143.137.239.60)
19:58
<alkisg>
Leandro_: are you sure that your crontab line is correct?
19:59
afaik, crontab_xx in lts.conf works fine, I'm not aware of any issues
19:59
Can you paste that line here?
20:00
SHUTDOWN_TIME="14:00:00" => shuts down the clients IF they're in ldm at that time
20:00
RCFILE_SHUTDOWN="shutdown -h 14:00" ==> shuts down the clients even if they have logged in
20:01
I think that's easier than cron; but if you prefer cron, it should work too
20:03
<vagrantc>
nice RCFILE trick :)
20:04
shutdown after X hours of inactivity would be interesting, too
20:05
<mwalters>
curious how you would measure inactivity... load/utilization under a certain threshold?
20:06
<vagrantc>
there are functions in X to monitor activity that are used by screensavers
20:06
<mwalters>
oh, I guess that makes sense
20:06
<vagrantc>
so use the same "activity" detection to do something other than a screensaver
20:07
<mwalters>
I wonder if you could detect the screen being locked
20:07
and unlocked... if the screen has been locked for N minutes
20:07
<vagrantc>
could probably even use xautolock directly, since it can call an arbitrary screensaver ... i did that on some kiosks i had
20:08
though i think in the end i wrote a hook that prepended "timeout $((60*60*2)) /path/to/desktop-session" which just brutally killed the session
20:09
and then used xautolock to popup reminders or something
20:09
<mwalters>
won't you think of the sessions
20:09
yeah, I have locking/timeout setup through dconf right now
20:14
<Leandro_>
alkisg: crontab is having a weird behavior. If I put something like "touch test.txt" in it, it runs, but things like "shutdown -h now" "init 0" "mate-session-save --logout" dont't run at all.
20:14
I will try the RCFILE_SHUTDOWN trick here and will get back to you tomorrow. Thank you
20:15
<vagrantc>
mate-session-save certainly wouldn't work
20:16
<Leandro_>
it works on shell
20:16
<vagrantc>
a shell without DISPLAY and appropriate XAUTHORITY?
20:16
or user
20:16
?
20:16
<Leandro_>
user
20:17
on a terminal open with X, "mate-session-save --logout" logs out the user
20:18
<vagrantc>
yes, which is a very different environment from where cron runs
20:18
<Leandro_>
indeed, you're right
20:20
The RCFILE_SHUTDOWN worked!
20:20
<vagrantc>
alkisg almost always has the best suggestions
20:20
<Leandro_>
alkisg saving my ass once again. Thank you! And also thanks to vagrantc and mwalters
20:28willianmazzardo has left IRC (willianmazzardo!8f89ef3c@gateway/web/freenode/ip.143.137.239.60, Ping timeout: 256 seconds)
20:45Faith has left IRC (Faith!~Paty_@unaffiliated/faith, Quit: Leaving)
20:57vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Ping timeout: 250 seconds)
20:59vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
20:59ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Remote host closed the connection)
21:59lopta has left IRC (lopta!~ball@74-84-114-18.client.mchsi.com, Quit: leaving)
22:11kjackal has left IRC (kjackal!~quassel@2a02:587:3119:ef00:8593:ced4:afeb:e172, Ping timeout: 252 seconds)
23:08vsuojanen has left IRC (vsuojanen!~vsuojanen@cable-hml-585686-205.dhcp.inet.fi, Ping timeout: 268 seconds)
23:10vsuojanen has joined IRC (vsuojanen!~vsuojanen@cable-hml-585686-205.dhcp.inet.fi)