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


Channel log from 4 May 2021   (all times are UTC)

03:42vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving)
05:14sutula has left IRC (sutula!~sutula@184.97.9.9, Ping timeout: 260 seconds)
05:21sutula has joined IRC (sutula!~sutula@76.6.6.37)
06:08ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)
06:26RaphGro has joined IRC (RaphGro!~raphgro@fedora/raphgro)
07:22mistik1 has joined IRC (mistik1!~mistik1@96.43.180.108)
07:23
<mistik1>
greetings folks
07:23
<alkisg>
Hello mistik1
07:24
<mistik1>
Its been some time glad to see you guys still at the job :)
07:24
<alkisg>
There are few left, but we're still going!
07:28
<mistik1>
Well I have a computer again, so i'll be around a bit more
07:29
<alkisg>
Woah you managed to live without one?! :D
07:29
<mistik1>
*sigh* 1 year now
07:29* alkisg wants to find enough time in the summer to test that...
07:30
<mistik1>
I am totally off grid and when I finished my house and setup solar the laptop did not turn on
07:30
<alkisg>
Ouch. And for wifi, using 4g/5g?
07:30
*for internet access
07:30
<mistik1>
4g
07:30
<alkisg>
Good enough
07:31
<mistik1>
good enough that i'm listening to a book and using the net, setting up this machine
07:32
I'm so rusty, need to get coding on something again soon
07:32
<alkisg>
If you have a second computer or a VM, you can test the new ltsp! :)
07:33
<mistik1>
I do have a couple old RasPi around
07:33
<alkisg>
raspi is harder, but I do have working documentation about it there: https://ltsp.org/docs/installation/raspios/
07:34
<mistik1>
I was just reading that
07:35
I was seeing what direction the project has taken since I was involved
07:35
<alkisg>
Where were you last contributions, which year?
07:36
<mistik1>
circa 2014~2015
07:36
<alkisg>
Ah OK you know about fat clients then
07:36
<mistik1>
a long time as I said
07:36
Yes
07:36
<alkisg>
Nowadays it's "fat clients only"; with remote desktop/rdp/vnc for thin client emulation
07:37
<mistik1>
I just read the docs and am impressed, it certainly gets rid of the problems we had with remote sound and all that nonsense
07:39Aison0 has joined IRC (Aison0!~Asion0@2a02:168:200f:110:69c6:120a:877c:5a19)
07:40
<mistik1>
anyhow, I still dont have enough batteries to do all nighters with the computer and lights, so i'll sign off for now
07:40
<alkisg>
Good to see you again! Cheers
07:40
<mistik1>
Take care
07:41mistik1 has left IRC (mistik1!~mistik1@96.43.180.108)
10:19ltsp_user17 has joined IRC (ltsp_user17!0134eb5c@1.52.235.92)
10:20
<ltsp_user17>
hello everyone
10:20
<alkisg>
Hello ltsp_user17
10:20
<ltsp_user17>
I've ltsp to netboot my ubuntu 18.04 server
10:20
but i don't know why my openssh-server at client no enable
10:21
I've check on my server it's on with
10:21
 systemctl is-enabled ssh
10:21
enabled
10:21
but on my client I've checkd it's disable
10:22
how can I enable openssh-server at all client
10:22
<alkisg>
!sshd
10:22
<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
10:22
<alkisg>
!epoptes
10:22
<ltspbot>
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: https://epoptes.org
10:22
<alkisg>
ltsp_user17: read these ^
10:23
<ltsp_user17>
thank you, I've read that post
10:23
my issue is openssh-server on client not auto start when booting
10:23
when I login into client and manualy start openssh-server, I can ssh into that client
10:24
But I want to auto enable openssh-server when booting all client
10:24
<alkisg>
ltsp_user17: so you have KEEP_SYSTEM_SERVICES=ssh in ltsp.conf?
10:25
<ltsp_user17>
yes, I have KEEP_SYSTEM_SERVICES=ssh
10:25
<alkisg>
And all the rest, like POST_INIT_MV_SSH ?
10:27
<ltsp_user17>
I added that
10:27
[server]
10:27
OMIT_FUNCTIONS="ssh_host_keys"
10:27
OMIT_IMAGE_EXCLUDES="etc/ssh/ssh_host_*"
10:27
[clients]
10:27
KEEP_SYSTEM_SERVICES="openssh-server"
10:27
I ssh with my password
10:27
<alkisg>
ltsp_user17: don't do that
10:27
Read the link that I pasted instead
10:27
Use the POST_INIT_MV_SSH directive etc
10:28
<ltsp_user17>
oh, let me try
10:28
thank you, another question
10:28
how can I execute custom script when boot client
10:29
<alkisg>
At init? After boot? At login?
10:29
What does this do, does it need xorg access?
10:29
<ltsp_user17>
after boot
10:29
<alkisg>
Does it stay running?
10:29
Anyway one way is POST_SERVICE_X="command"
10:29
<ltsp_user17>
no UI, it's just command
10:29
<alkisg>
This runs it around the time that the login screen is reached
10:29
<ltsp_user17>
I've running ubuntu server, not desktop
10:29
<alkisg>
Isn't POST_INIT_X better?
10:30
If you say what it's doing, I'll tell you where it's better. Otherwise use one of them...
10:30
<ltsp_user17>
what difference between POST_SERVICE_X and POST_INIT_X
10:30
<alkisg>
init is very early, like init=/bin/bash
10:31
service is later, like rc.local
10:31
<ltsp_user17>
where I can find any example or document about it
10:31
<alkisg>
For most tasks, init is better
10:31
In the ltsp.conf man page
10:31
!ltsp.conf
10:31
<ltspbot>
ltsp.conf: Configuration file for LTSP: https://ltsp.org/man/ltsp.conf/
10:33
<ltsp_user17>
I've tried post_init to set root account
10:33
POST_INIT_SET_ROOT_HASH="section_set_root_hash"
10:33
# This is the hash of "qwer1234"; cat /etc/shadow to see your hash.
10:33
[set_root_hash]
10:33
sed 's|^root:[^:]*:|root:$6$bKP3Tahd$a06Zq1j.0eKswsZwmM7Ga76tKNCnueSC.6UhpZ4AFbduHqWA8nA5V/8pLHYFC4SrWdyaDGCgHeApMRNb7mwTq0:|' -i /etc/shadow
10:33
<alkisg>
And?
10:33
<ltsp_user17>
but i can't login with root account
10:34
<alkisg>
Did you use your own hash, or this one?
10:34
<ltsp_user17>
use this one
10:34
<alkisg>
Also did you run `ltsp initrd`?
10:34
<ltsp_user17>
root | qwer1234
10:34
yes I've ran ltsp initrd
10:34
and when login into my client
10:35
I can saw root with hash at /etc/shadow
10:35
but I can't login
10:35
don't know why
10:35
<alkisg>
Maybe the hash is wrong, use another one
10:35
<ltsp_user17>
root@ltsp143:~# cat /etc/shadow | grep root
10:35
root:$6$bKP3Tahd$a06Zq1j.0eKswsZwmM7Ga76tKNCnueSC.6UhpZ4AFbduHqWA8nA5V/8pLHYFC4SrWdyaDGCgHeApMRNb7mwTq0:::::::
10:35
you can see
10:36
<alkisg>
Type passwd, set qwer1234 as the password, then cat shadow and use that hash
10:36
Maybe the ltsp.conf man page example hash is wrong
10:36
<ltsp_user17>
ok, let me try
10:44Vercas1 has joined IRC (Vercas1!~Vercas@gateway/tor-sasl/vercas)
10:45Vercas has left IRC (Vercas!~Vercas@gateway/tor-sasl/vercas, Ping timeout: 240 seconds)
10:45Vercas1 is now known as Vercas
10:50
<ltsp_user17>
I think it's wrong
10:50
but I change still not work :(
10:51
root@ubuntu18:~# cat /etc/shadow | grep demo
10:51
demo:$6$FBPBqMA0$h5z8nRzHgsG07swgt7jzkvkwHQMs3f3YMOGKLbTK6kk/rkTs2oZ0GY3Qa7SQMKCgdd2uh7b4OOvd2E4GFWIwD/:18751:0:99999:7:::
10:51
root@ubuntu18:~# cat /etc/ltsp/ltsp.conf | grep sed
10:51
# The hash contains $, making it hard to escape in POST_INIT_x="sed ...".
10:51
# So put sed in a section and call it at POST_INIT like this:
10:51
#sed 's|^root:[^:]*:|root:$6$bKP3Tahd$a06Zq1j.0eKswsZwmM7Ga76tKNCnueSC.6UhpZ4AFbduHqWA8nA5V/8pLHYFC4SrWdyaDGCgHeApMRNb7mwTq1:|' -i /etc/shadow
10:51
sed 's|^root:[^:]*:|root:$6$MgFtSVYk$YWDt2Hl0rs9CVeu3d0Sl7Fn9VLDJSwFj4hf.pOxwqTvnxeqeJDpKJ5OVYjSIU8U7ZHkZG82Kqe2.Agu3Qlp/K.' -i /etc/shadow
10:53
when boot client, it throw: sed: -e expression #1, char 118: unterminated `s' command
10:57
<alkisg>
Yes see the man page example, it needs a | at the end
10:57
I.e. it's like this: sed 's|what-to-search|replacement|' -i /etc/shadow
11:02
<ltsp_user17>
oh, I bypass that error, but still incorrect pass
11:03
Can you provide me sed command for passwd: qwer1234
11:07
I saw everytime I change with same password, it's generate difference hash, don't know why :))
11:22
for ssh I added POST_INIT_MV_SSH and no luck, openssh not auto start
12:11ltsp_user17 has left IRC (ltsp_user17!0134eb5c@1.52.235.92, Quit: Connection closed)
12:12ltsp_user17 has joined IRC (ltsp_user17!0134eb5c@1.52.235.92)
12:13
<ltsp_user17>
Hi alkisg, I tried setup ssh key and auto enable service with POST_SERVICE_, it work!
12:14
thank you
12:29
<alkisg>
ltsp_user17: great
12:42
<ltsp_user17>
I wonder when ltsp server is down, can my client still work or crash?
12:49
<alkisg>
ltsp_user17: access to nfs files makes the client hang until the server is up again
12:50
Access to sshfs files (under /home/username) is less tolerant, it doesn't survive reboots
12:55
<ltsp_user17>
what's nfs file?, it include rootfs ?
12:59
<alkisg>
Yes, all rootfs (all files under /) is accessed via NFS
13:31AppleMuncy has joined IRC (AppleMuncy!4436794d@c-68-54-121-77.hsd1.in.comcast.net)
13:31
<AppleMuncy>
!news
13:31
<ltspbot>
I do not know about 'news', but I do know about these similar topics: 'nfs'
13:41
<ltsp_user17>
Hi alkisg, on my client, I just saw /home/user01 mounted with nfs
13:41
root@ltsp143:~# df -h
13:41
Filesystem Size Used Avail Use% Mounted on
13:41
udev 456M 0 456M 0% /dev
13:41
tmpfs 99M 2.0M 97M 3% /run
13:41
tmpfs 493M 5.7M 487M 2% /run/initramfs/ltsp
13:41
tmpfs 493M 0 493M 0% /dev/shm
13:41
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
13:41
tmpfs 493M 0 493M 0% /sys/fs/cgroup
13:41
user01@server: 8.8G 7.5G 942M 89% /home/user01
13:41
tmpfs 99M 0 99M 0% /run/user/1000
13:41
tmpfs 99M 0 99M 0% /run/user/0
13:41
<alkisg>
!paste
13:41
<ltspbot>
paste: To avoid channel flooding, please upload text longer than 3 lines to http://paste.debian.net. Don't forget to paste the resulting URL here.
13:41
<ltsp_user17>
you can see here
13:41
http://paste.debian.net/1196250/
13:41
<alkisg>
That's sshfs, not nfs
13:42
/ is mounted via nfs, while /home/username with sshfs
13:42
You can also mount /home with nfs if you want, but it's not the default
13:42
!nfs
13:42
<ltspbot>
nfs: to enable NFS home directories for localapps and fat clients, install nfs-kernel-server on your server, nfs-common on your client (don't forget ltsp-update-image), and put this in lts.conf: FSTAB_1="server:/home /home nfs defaults,nolock 0 0"
13:42
<alkisg>
!forget nfs
13:42
<ltspbot>
The operation succeeded.
13:42
<alkisg>
!nfs
13:42
<ltspbot>
I do not know about 'nfs', but I do know about these similar topics: 'ltsp-nfs', 'nfsnotresp', 'squashfs-over-nfs'
13:42
<alkisg>
!ltsp-nfs
13:42
<ltspbot>
ltsp-nfs: Configure NFS exports for LTSP: https://ltsp.org/man/ltsp-nfs/
13:44
<alkisg>
!learn nfs-home as You can mount /home over NFS, see https://ltsp.org/man/ltsp-nfs/#examples - it's faster and more stable than SSHFS, but also insecure
13:44
<ltspbot>
The operation succeeded.
13:44
<ltsp_user17>
so if all rootfs mount by nfs, it will hang when ltsp server stop :(
13:45
<alkisg>
Yes, when you have your files in a server, you don't want the server to stop
13:45
There's no magic involved
13:46
<ltsp_user17>
does IMAGE_TO_RAM will help this ?
13:46
<alkisg>
Are your users able to save files?
13:46
E.g. documents, mails etc?
13:46
<ltsp_user17>
my users just save some config text, it's so small
13:47
<alkisg>
Where will that small be saved, in the air?
13:47
<ltsp_user17>
and I don't want when ltsp server is down or network is stuck, all my client is hang
13:47
<alkisg>
On the server, on a local disk, on the internet, on a usb stick?
13:47
Do you have kiosks or normal ltsp clients?
13:47
If you have kiosks, and NOT users, then you can have them work without the server, all in ram
13:48
If you have users, with dconf settings, small text files, or large videos, then you need to find storage for them
13:48
<ltsp_user17>
oh, my usecase is kiosks, not users
13:48
<alkisg>
It took a while to say that :)
13:49
!kiosk
13:49
<ltspbot>
I do not know about 'kiosk', but I do know about these similar topics: 'kiwi', 'kms'
13:49
<ltsp_user17>
I just want all my client running a app, and when I update on ltsp server, reboot all my client
13:49
<alkisg>
How much RAM do your clients have?
13:49
<ltsp_user17>
and it will affect all my client
13:50
it will be > 4GB
13:50
<alkisg>
Then yes it sounds like you want IMAGE_TO_RAM
13:50
That way you'll be able to power off the server, and the clients will keep working
13:52
<ltsp_user17>
yes that what I want to do
13:52
but I got issue
13:53
https://github.com/ltsp/ltsp/discussions/269
13:53
like this
13:54
<alkisg>
There's no point in using IMAGE_TO_RAM with sshfs
13:54
You'll need to create a local user in RAM, not on the server
13:54AppleMuncy has left IRC (AppleMuncy!4436794d@c-68-54-121-77.hsd1.in.comcast.net, Quit: Connection closed)
13:54
<alkisg>
LTSP doesn't have code for that yet, you'll need to do it manually
13:55
<ltsp_user17>
how can I create local user
13:55
<alkisg>
With adduser. Sorry but I don't have a couple of hours to implement this for you over IRC :)
13:58
<ltsp_user17>
yes, thank for your time, you've very kind
13:58
<alkisg>
You're welcome
13:58
<ltsp_user17>
so If I got problem, I will raise on github
13:58
<alkisg>
You'll need to implement that part for yourself...
13:59
It's a whole new feature that I have no interest to do at this moment in time
13:59
If sponsoring is found, then I can do new features for others, but I only do new features for free for the schools I maintain
14:00
<ltsp_user17>
If I undertand ltsp deep enough, I will implement it for sure
14:00
<alkisg>
Sure, it will just need some time. Patches welcome.
14:01
<ltsp_user17>
is there any document for understand and develop ltsp?
14:01
<alkisg>
The documentation at ltsp.org, and the code
14:01
That's all there is
14:03Vercas has left IRC (Vercas!~Vercas@gateway/tor-sasl/vercas, Quit: Ping timeout (120 seconds))
14:03Vercas has joined IRC (Vercas!~Vercas@gateway/tor-sasl/vercas)
14:03
<ltsp_user17>
yes, thank you, I will try for myself, If I got a issue, hope you guide me to implement it : D
14:04
<alkisg>
It depends on how much YOU help others!
14:04
I can't help everyone, but I can help those that help other ltsp users
14:04
<ltsp_user17>
yes, sure for that!
14:04adrianor1 has joined IRC (adrianor1!~adrianorg@201.22.229.88.dynamic.dialup.gvt.net.br)
14:08adrianorg has left IRC (adrianorg!~adrianorg@179.187.29.157, Ping timeout: 265 seconds)
14:08Aison0 has left IRC (Aison0!~Asion0@2a02:168:200f:110:69c6:120a:877c:5a19, Ping timeout: 260 seconds)
14:09
<alkisg>
It also helps if you're not anonymous; noone like to talk with "ltsp_user17", while even if it's "john1234", it's more friendly :)
14:09ltsp_user17 is now known as cbr09
14:09
<cbr09>
yes I changed my name :D
14:10Aison0 has joined IRC (Aison0!~Asion0@2a02:168:200f:110:69c6:120a:877c:5a19)
14:10
<alkisg>
Better, at least now it's something to remember for future chats
14:10cbr09 is now known as jaycb09
14:10
<jaycb09>
yes: D
14:11
at your school, how many client do you have
14:13
<alkisg>
I help maintain more than 1000 schools
14:13
Schools usually have 1 to 3 computer labs with 12 clients and a server. But I've set up LTSP in other areas with more than 100 clients.
14:13
If you're going to use IMAGE_TO_RAM, then you can serve any number of clients
14:14
<jaycb09>
yes, I see, with nfs mount, large client will have lag
14:15
<alkisg>
The main problem is /home/username
14:15
Because when a user opens firefox or libreoffice, it writes there
14:15
So if you have 100 users, you need a lot of bandwidth
14:15
But if you have kiosks, you don't care about that, your /home is in RAM
14:16
So the main traffic is SSHFS, not NFS
14:17
<jaycb09>
why ltsp choose /home with sshfs, it can be mount over nfs
14:17
what's advance for using sshfs than nfs
14:19
<alkisg>
!nfs-home
14:19
<ltspbot>
nfs-home: You can mount /home over NFS, see https://ltsp.org/man/ltsp-nfs/#examples - it's faster and more stable than SSHFS, but also insecure
14:19
<alkisg>
The "insecure" part
14:19
We don't want "insecure" by default
14:24
<jaycb09>
yes, security is first
14:52Aison0 has left IRC (Aison0!~Asion0@2a02:168:200f:110:69c6:120a:877c:5a19, Ping timeout: 246 seconds)
14:55adrianor1 is now known as adrianorg
14:59lucascastro has joined IRC (lucascastro!~lucascast@177-185-139-167.dynamic.isotelco.net.br)
16:01jaycb09 has left IRC (jaycb09!0134eb5c@1.52.235.92, Quit: Connection closed)
16:32lucas_ has joined IRC (lucas_!~lucascast@177-185-139-167.dynamic.isotelco.net.br)
16:32lucascastro has left IRC (lucascastro!~lucascast@177-185-139-167.dynamic.isotelco.net.br, Read error: Connection reset by peer)
17:42RaphGro has left IRC (RaphGro!~raphgro@fedora/raphgro, Remote host closed the connection)
19:30woernie has left IRC (woernie!~werner@p5ddec80a.dip0.t-ipconnect.de, Remote host closed the connection)
20:27AppleMuncy has joined IRC (AppleMuncy!4436794d@c-68-54-121-77.hsd1.in.comcast.net)
20:42AppleMuncy has left IRC (AppleMuncy!4436794d@c-68-54-121-77.hsd1.in.comcast.net, Quit: Connection closed)
21:24Vercas has left IRC (Vercas!~Vercas@gateway/tor-sasl/vercas, Quit: buh bye)
21:26adrianor1 has joined IRC (adrianor1!~adrianorg@186.215.21.248)
21:28adrianorg has left IRC (adrianorg!~adrianorg@201.22.229.88.dynamic.dialup.gvt.net.br, Ping timeout: 240 seconds)
21:54ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving)