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

Request log from specific day:

Channel log from 9 January 2022 (all times are UTC)

06:02	jgee has left IRC (jgee!~jgee@186.80.49.20, Quit: Ping timeout (120 seconds))
06:02	jgee has joined IRC (jgee!~jgee@186.80.49.20)
06:02	vagrantc has left IRC (vagrantc!~vagrant@2600:3c01:e000:21:21:21:0:100e, Quit: leaving)
06:50	<alkisg> Finally we can point directly to ltsp.conf manpage parameters! E.g. https://ltsp.org/man/ltsp.conf/#CRONTAB_x
09:08	ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)
11:21	lcurl_ has joined IRC (lcurl_!~UserNick@222.254.154.163)
11:24	lcurl has left IRC (lcurl!~UserNick@222.254.154.163, Ping timeout: 250 seconds)
11:24	lcurl_ is now known as lcurl
11:59	Vercas has left IRC (Vercas!~Vercas@gateway/tor-sasl/vercas, Remote host closed the connection)
13:17	<quinox> nice
14:22	Vercas has joined IRC (Vercas!~Vercas@gateway/tor-sasl/vercas)
16:10	zetaE has joined IRC (zetaE!~neon@139.47.114.154)
16:10	<zetaE> hei
16:10	would this work without admin rights?
16:10	ssh -oProxyJump=[RELAY_USER@]RELAY_HOST[:RELAY_PORT] [USER@]HOST
16:12	or this? ssh -J [RELAY_USER@]RELAY_HOST[:RELAY_PORT] [USER@]HOST
16:16	why does LTSP only use ubuntu?
16:17	<alkisg> Hi zetaE
16:17	LTSP relies on initramfs to provide certain functionality, to mount the disk from the network
16:17	Debian and Ubuntu use initramfs-tools, which provides that
16:18	Fedora etc use dracut, which provides it in a different way, and needs some development time to whip it into shape
16:18	Currently noone was interested in doing that; it's about a week of development work
16:18	About the ssh questions, what's the end goal?
16:19	<zetaE> alkisg: be able to shutdown clients from either server or other remote clients
16:20	<alkisg> !ssh
16:20	<ltspbot> I do not know about 'ssh', but I do know about these similar topics: 'sshd'
16:20	<zetaE> the set up is unattended with only a faux admin account to deal with read/write permission on public shares to prevent clients erasing everything
16:20	<alkisg> !sshd
16:20	<ltspbot> sshd: Exposing sshd host keys over NFS is unsafe, so it's disabled by default and !epoptes is recommended instead. If you insist on running sshd in LTSP clients, read https://github.com/ltsp/ltsp/discussions/310#discussioncomment-101549
16:20	<zetaE> alkisg: no access to epoptes
16:20	there's no real admin
16:20	<alkisg> You can use remote epoptes
16:21	But I mainly pasted that link to show how to enable ssh for the clients
16:21	After you ssh to the server then you should be able to ssh to the clients and shut them down, sure
16:22	<zetaE> ah thanks
16:22	alkisg: no root access here
16:24	<alkisg> Not sure what you mean. You don't need root in your own PC to ssh as root on the ltsp server,
16:24	and if you don't have root on the ltsp server, how are you going to enable ssh for the clients...
16:25	<zetaE> alkisg: I can ssh into anywhere but ONLY using server's ip
16:26	<alkisg> Your end goal is to shut down a ltsp client while you're on a non-ltsp pc, right?
16:26	That means that you'll need to ssh root@server, and from there, ssh ltsp-client poweroff
16:26	Which part you can't do?
16:27	<zetaE> no, from another ltsp terminal pc
16:27	<alkisg> OK, it's the same thing then
16:27	<zetaE> let.s say from clint1 shutdown client2
16:28	<alkisg> OK, it's the same answer, you can either run epoptes in client1 and do it graphically, or you can ssh directly to ltsp2, or ssh to the server and then to ltsp2
16:28	I'm not sure what kind of additional restrictions you have
19:40	vagrantc has joined IRC (vagrantc!~vagrant@2600:3c01:e000:21:21:21:0:100e)
19:49	lucascastro[m] has joined IRC (lucascastro[m]!~lucascast@2001:470:69fc:105::1:59f2)
21:52	ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving)
22:28	vagrantc has left IRC (vagrantc!~vagrant@2600:3c01:e000:21:21:21:0:100e, Quit: leaving)