|06:02||jgee has left IRC (email@example.com, Quit: Ping timeout (120 seconds))|
|06:02||jgee has joined IRC (firstname.lastname@example.org)|
|06:02||vagrantc has left IRC (vagrantc!~vagrant@2600:3c01:e000:21:21:21:0:100e, Quit: leaving)|
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@18.104.22.168)|
|11:24||lcurl has left IRC (lcurl!~UserNick@22.214.171.124, 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)|
|14:22||Vercas has joined IRC (Vercas!~Vercas@gateway/tor-sasl/vercas)|
|16:10||zetaE has joined IRC (zetaEemail@example.com)|
would this work without admin rights?
ssh -oProxyJump=[RELAY_USER@]RELAY_HOST[:RELAY_PORT] [USER@]HOST
or this? ssh -J [RELAY_USER@]RELAY_HOST[:RELAY_PORT] [USER@]HOST
why does LTSP only use ubuntu?
LTSP relies on initramfs to provide certain functionality, to mount the disk from the network
Debian and Ubuntu use initramfs-tools, which provides that
Fedora etc use dracut, which provides it in a different way, and needs some development time to whip it into shape
Currently noone was interested in doing that; it's about a week of development work
About the ssh questions, what's the end goal?
alkisg: be able to shutdown clients from either server or other remote clients
I do not know about 'ssh', but I do know about these similar topics: 'sshd'
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
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
alkisg: no access to epoptes
there's no real admin
You can use remote epoptes
But I mainly pasted that link to show how to enable ssh for the clients
After you ssh to the server then you should be able to ssh to the clients and shut them down, sure
alkisg: no root access here
Not sure what you mean. You don't need root in your own PC to ssh as root on the ltsp server,
and if you don't have root on the ltsp server, how are you going to enable ssh for the clients...
alkisg: I can ssh into anywhere but ONLY using server's ip
Your end goal is to shut down a ltsp client while you're on a non-ltsp pc, right?
That means that you'll need to ssh root@server, and from there, ssh ltsp-client poweroff
Which part you can't do?
no, from another ltsp terminal pc
OK, it's the same thing then
let.s say from clint1 shutdown client2
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
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)|