|00:29||ltspnoob has left IRC (firstname.lastname@example.org, Quit: Client closed)|
|03:04||mistik1 has joined IRC (email@example.com)|
|04:14||woernie has left IRC (firstname.lastname@example.org, Remote host closed the connection)|
|04:15||woernie has joined IRC (email@example.com)|
|04:40||quinox has left IRC (firstname.lastname@example.org, Quit: WeeChat 3.0.1)|
|04:43||quinox has joined IRC (email@example.com)|
|05:25||ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)|
|06:50||woernie has left IRC (firstname.lastname@example.org, Ping timeout: 258 seconds)|
|06:50||woernie has joined IRC (email@example.com)|
|07:58||mistik1 has left IRC (firstname.lastname@example.org, Ping timeout: 265 seconds)|
|07:59||woernie has left IRC (email@example.com, Ping timeout: 240 seconds)|
|08:00||woernie has joined IRC (firstname.lastname@example.org)|
|13:14||lucas_ has joined IRC (email@example.com)|
|13:15||mistik1 has joined IRC (firstname.lastname@example.org)|
|13:17||lucascastro has left IRC (email@example.com, Ping timeout: 255 seconds)|
|14:13||vagrantc has joined IRC (vagrantc!~vagrant@2600:3c01:e000:21:21:21:0:100b)|
|15:00||bcg has left IRC (firstname.lastname@example.org, Quit: bcg)|
|15:02||bcg has joined IRC (email@example.com)|
|15:25||lucas_ has left IRC (firstname.lastname@example.org, Quit: Leaving)|
|15:25||lucascastro has joined IRC (email@example.com)|
|16:26||ltspnoob has joined IRC (firstname.lastname@example.org)|
after a reboot of the LTSP server.. when I tried to update the main client image with "cd /srv/ltsp; ltsp image /" , I got the error "/usr/sbin/ltsp: 385: cannot create /run/ltsp/debug.log: Directory nonexistent
" I manually created the "/run/ltsp" and the "ltsp image /" proceeded normally. anyone know why that /run/ltsp directory would suddenly disappear after a reboot?
shoud be no reason to run "cd /srv/ltsp" ... though maybe that triggers an issue somehow
the /run directories are effectively reset at boot, usually because they're on a filesystem in ram
and /run/ltsp should get created as needed
Don't set DEBUG_LOG manually
What's the output of `env | grep ^DEBUG`, or of `grep DEBUG /etc/ltsp/ltsp.conf` ?
oh. I did set "DEBUG_LOG=1" in /etc/ltsp/ltsp.conf when I was troubleshooting the Metacity unlock issue yesterday!
You can use LTSP_DEBUG but not DEBUG_LOG
I see. I read somewhere that I could enable debug logging to try to find out what went wrong with the Metacity issue.. lol
Thank you all! confirmed: I can run "ltsp image /" from anywhere, and after removing DEBUG_LOG=1 from ltsp.conf, "ltsp image /" auto creates /run/ltsp if it doesn't exist without error-exiting
Hmm, I think it does need a bit better documentation though
..for later! :)
better documentation is always good. =D
|17:16||mistik1 has left IRC (email@example.com, Remote host closed the connection)|
|17:17||mistik1 has joined IRC (firstname.lastname@example.org)|
Question: why is ipxe listing the directory names in /srv/ltsp/ on the ipxe boot menu? isn't it supposed to be just listing the .img files in /srv/ltsp/images/ ?
I have a few "chroot" directory in /srv/ltsp/ , which I use for building the chroot-custom images with "ltsp image <chroot dirname>"
* "chroot" directorIES
It's possible to boot the chroots OR the images
chroot nfs vs image nfs
Oh I see! hmm... and the chroots directories are booted differently by (.. offered differently to) the clients? ( not sure if I am asking the question right...)
Yes, as nfs directories, vs nfs images
It's slower, but useful in faster troubleshooting or in maintaining images of different architectures
I see. which is the preferred way?
ah ok. I see.
If you do not want them to be listed, you can put them elsewhere, and run ltsp image /full/path/to/chroot
ah.. good to know! reading the docs on the site, I thought I had to put the chroots in /srv/ltsp due to the command format "ltsp image <dirname>" , not knowing I could run "ltsp image /full/path/chroot". :') :')
Btw about metacity, it's not a problem if you want to use a chroot, but that bug doesn't seem related to ltsp,
it will probably appear if you copy the chroot to a local disk with grub etc, so you can troubleshoot the issue there
Yes, I agree that bug shouldn't be related to ltsp, but within metacity itself. I will test a standalone metacity installation separately when I get sometime. I wanted to use Metacity because the current LTSP5 installation is using Metacity. But I think I will move to xfce for this new LTSP set up.
KDE currently is lighter than mate, which is lighter than xfce
So we'll probably switch to KDE in the next deployment in schools here
I see! good to know!
re. KDE.. I guess it's the Plasma version/release that is the most light weight?
|17:48||vagrantc has left IRC (vagrantc!~vagrant@2600:3c01:e000:21:21:21:0:100b, Quit: leaving)|
|17:57||ltspnoob has left IRC (email@example.com, Quit: Client closed)|
|18:55||ltspnoob has joined IRC (firstname.lastname@example.org)|
hmm...strangely... twice now that when I run "ltsp image /" ..the server goes into Suspended mode... (never happened before when I was building the chroot images)
and ..after getting the server back awake.. rerunning "ltsp image /" resulted in an error at the very last stage: " adm (4)
mv: cannot stat '/srv/ltsp/images/x86_64.img.tmp': No such file or directory
LTSP command failed: mv /srv/ltsp/images/x86_64.img.tmp /srv/ltsp/images/x86_64.img
Emulating a shell, type `return [0|1]` to continue|exit:
running it again now and see if that happens again.. (no disk space issues)
It succeeded this time. :D
so... not sure what happened earlier..
Question: the client computer after booting up.. does not have the updated /etc/group file from the server.. How do I set it so that custom entries in /etc/group in the LTSP server do take effect in client's /etc/group file?
ltsp initrd on the server and client reboot sends the passwd to the client
For custom, /etc/ltsp/passwd
Thanks! I will go try that!
running "ltsp initrd" didn't result in the client rebooted to receive the custom entries in /etc/group .. I am trying with putting /etc/group in /etc/ltsp/group now...
Correction: "running ltsp initrd with the /etc/group in /etc/ltsp/group" did result in /etc/group in the client being updated..
Although.. only 2 out of the 10 entries got through .and those 2 entries.. are missing additional users after the groups
e.g. original /etc/group's custom entries:
group1:x:501:user1,user2,user3 group2:x:501:user1:user2 , ... group10... => ended up as group2:x:502:user .. group7:x:507:user1
update: the server went into suspended mode again somehow... without me running "ltsp image /"
|20:01||woernie has left IRC (email@example.com, Ping timeout: 252 seconds)|
|20:01||woernie has joined IRC (firstname.lastname@example.org)|
I don't think that "suspend mode" is related to ltsp somehow
I don't think so either.. it'd too strange if it did! .. maybe it's the xfce4 package I installed in the server yesterday... and with the reboot earlier today...something got changed in the server... hmmm
Question: is there a way to get a custom file in the server at /etc/ltsp/<filename> copied to the client's specific directory, e.g. /etc/<filename> ?
|20:31||woernie has left IRC (email@example.com, Ping timeout: 256 seconds)|
hmm...I think I figured out: using ltsp.conf [clients] section to include another section with a "cp -a /etc/ltsp/filename /etc/filename", then run "ltsp initrd"
|20:42||ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving)|
ltspnoob: anything under /etc/ltsp goes to the client /etc/ltsp
Then, with a POST_INIT directive, symlink it wherever you need
(ltsp initrd needed of course)
|21:09||mistik1 has left IRC (firstname.lastname@example.org, Ping timeout: 255 seconds)|
|21:45||ltspnoob has left IRC (email@example.com, Quit: Client closed)|
|22:03||ltspnoob has joined IRC (firstname.lastname@example.org)|