|02:27||vagrantc has left IRC (vagrantc!~vagrant@2600:3c01:e000:21:21:21:0:100b, Quit: leaving)|
|03:38||vagrantc has joined IRC (vagrantc!~vagrant@2600:3c01:e000:21:21:21:0:100e)|
|04:26||vagrantc has left IRC (vagrantc!~vagrant@2600:3c01:e000:21:21:21:0:100e, Quit: leaving)|
|07:05||woernie has joined IRC (email@example.com)|
|07:05||woernie_ has left IRC (firstname.lastname@example.org, Ping timeout: 256 seconds)|
|07:10||ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)|
alkisg: thanks (about case in ltsp.ipxe). Thought so.
I've started working on epoptes first, as it had a regression; in a few days I'll finish with it and start working on the new ltsp release
|11:15||fiesh_ is now known as fiesh|
|12:00||lucascastro has left IRC (email@example.com, Remote host closed the connection)|
|12:09||lucascastro has joined IRC (firstname.lastname@example.org)|
|12:51||danboid has joined IRC (email@example.com)|
I'm trying to troubleshoot my PAM/SSH issues but can't access the logs on the LTSP clients. How do I create a local sudo user that is enabled in the LTSP image?
I already have such a user in the source VM image but I presume LTSP disables thej by default
Also, although I've disabled the lightdm option to show the users on the login screen and that option works in my source VM image, I still see all the users when I boot the same image under LTSP
Its as if its not reading the lightdm config file under LTSP and no, I've not got any snapshots now
The same image after being compressed by ltsp image that is
It looks like I might do this using the PASSWORDS statement in ltsp.conf, maybe but the man page doesn't mention sudo
Does LTSP expect that these users already exist in the image so if they do exist and are in the sudo group and are mentioned in the PASSWORDS statement I'll be able to log in as a sudo user?#
Although thats not quite what I want as I don't want anyone to be able top login as a sudo user
Is there not some user whitelist or something?
It seems LTSP disables local users in the source image right?
Someone other than alkisg must know the answer to this
Actually no, the ltsp.conf man page says
"Normally, all the server users are listed on the client login screens and are permitted to log in"
Thats not been my experience. I have not been able to login as any of the users the exist on the image
The PWMERGE_SUR=, PWMERGE_SGR=, PWMERGE_DGR=, PWMERGE_DUR= commands hint at why I'm still seeing all the local users listed on the lightdm login screen
I've read the pwmerge comments / instructions but I don't understand them. I'm not sure what the difference is between the the destination and the merged accounts
Are the merged passwords the destination?
|14:40||woernie has left IRC (firstname.lastname@example.org, Ping timeout: 256 seconds)|
|14:40||woernie has joined IRC (email@example.com)|
danboid: see the last line in https://ltsp.org/man/ltsp.conf/
You'll get root that way, then you'll be able to troubleshoot
Although it's much easier to just use epoptes and right click > open a root terminal
After you get root, you can add temporary sudo users with `adduser`, if you want to test PAM with them
alkisg, Ill try that. What about pwmerge vs lightdm?
alkisg, In my lightdm.conf I have the lines
but that seems to be overridden by ltsp / pwmerge
See LIGHTDM_CONF in ltsp.conf
You can specify things from there if you can't do it via your image
pwmerge shouldn't be needed since you shouldn't be using accounts from the image anyway
|16:45||woernie has left IRC (firstname.lastname@example.org, Ping timeout: 250 seconds)|
|16:45||woernie has joined IRC (email@example.com)|
alkisg, LIGHTDM_CONF goes under the [clients] section of ltsp.conf right?
|18:39||vagrantc has joined IRC (vagrantc!~vagrant@2600:3c01:e000:21:21:21:0:100e)|
|19:31||dan_ has joined IRC (firstname.lastname@example.org)|
|19:31||danboid has left IRC (email@example.com, Read error: Connection reset by peer)|
|19:52||dan_ has left IRC (firstname.lastname@example.org, Quit: Leaving)|
Ouch, now I remember, there was NO `cp -u` in older busybox versions
also very dependent on a working clock ... sometimes the clock doesn't get updated till after initramfs ...
but maybe that's just the buggy systems i work with...
It was added in 2016 in busybox, so only older distributions are affected; a cp -au || cp -a should be good enough then :)
sunweaver, vagrantc : https://github.com/ltsp/ltsp/issues/636#issuecomment-1012501601
|21:06||ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving)|