00:29 | ltspnoob has left IRC (ltspnoob!~ltspnoob@riddle.wizard.ca, Quit: Client closed) | |
03:04 | mistik1 has joined IRC (mistik1!~mistik1@96.43.180.28) | |
04:14 | woernie has left IRC (woernie!~werner@p5ddec030.dip0.t-ipconnect.de, Remote host closed the connection) | |
04:15 | woernie has joined IRC (woernie!~werner@p5ddec030.dip0.t-ipconnect.de) | |
04:40 | quinox has left IRC (quinox!~quinox@ghost.qtea.nl, Quit: WeeChat 3.0.1) | |
04:43 | quinox has joined IRC (quinox!~quinox@ghost.qtea.nl) | |
05:25 | ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz) | |
06:50 | woernie has left IRC (woernie!~werner@p5ddec030.dip0.t-ipconnect.de, Ping timeout: 258 seconds) | |
06:50 | woernie has joined IRC (woernie!~werner@p578bb7b6.dip0.t-ipconnect.de) | |
07:58 | mistik1 has left IRC (mistik1!~mistik1@96.43.180.28, Ping timeout: 265 seconds) | |
07:59 | woernie has left IRC (woernie!~werner@p578bb7b6.dip0.t-ipconnect.de, Ping timeout: 240 seconds) | |
08:00 | woernie has joined IRC (woernie!~werner@p5ddec030.dip0.t-ipconnect.de) | |
13:14 | lucas_ has joined IRC (lucas_!~lucascast@177-185-133-236.dynamic.isotelco.net.br) | |
13:15 | mistik1 has joined IRC (mistik1!~mistik1@96.43.180.28) | |
13:17 | lucascastro has left IRC (lucascastro!~lucascast@189.90.44.253.jupiter.com.br, 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 (bcg!~b@dg4ybwyyyyyyyyyyyyyyt-3.rev.dnainternet.fi, Quit: bcg) | |
15:02 | bcg has joined IRC (bcg!~b@dg4ybwyyyyyyyyyyyyyyt-3.rev.dnainternet.fi) | |
15:25 | lucas_ has left IRC (lucas_!~lucascast@177-185-133-236.dynamic.isotelco.net.br, Quit: Leaving) | |
15:25 | lucascastro has joined IRC (lucascastro!~lucascast@177-185-133-236.dynamic.isotelco.net.br) | |
16:26 | ltspnoob has joined IRC (ltspnoob!~ltspnoob@riddle.wizard.ca) | |
16:59 | <ltspnoob> 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
| |
16:59 | " 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?
| |
17:00 | <vagrantc> shoud be no reason to run "cd /srv/ltsp" ... though maybe that triggers an issue somehow
| |
17:01 | the /run directories are effectively reset at boot, usually because they're on a filesystem in ram
| |
17:01 | and /run/ltsp should get created as needed
| |
17:02 | <alkisg> Don't set DEBUG_LOG manually
| |
17:03 | What's the output of `env | grep ^DEBUG`, or of `grep DEBUG /etc/ltsp/ltsp.conf` ?
| |
17:04 | <ltspnoob> oh. I did set "DEBUG_LOG=1" in /etc/ltsp/ltsp.conf when I was troubleshooting the Metacity unlock issue yesterday!
| |
17:04 | <alkisg> You can use LTSP_DEBUG but not DEBUG_LOG
| |
17:05 | <ltspnoob> I see. I read somewhere that I could enable debug logging to try to find out what went wrong with the Metacity issue.. lol
| |
17:08 | 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
| |
17:08 | <alkisg> Hmm, I think it does need a bit better documentation though
| |
17:08 | ..for later! :)
| |
17:09 | <ltspnoob> better documentation is always good. =D
| |
17:16 | mistik1 has left IRC (mistik1!~mistik1@96.43.180.28, Remote host closed the connection) | |
17:17 | mistik1 has joined IRC (mistik1!~mistik1@96.43.180.28) | |
17:18 | <ltspnoob> 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/ ?
| |
17:19 | I have a few "chroot" directory in /srv/ltsp/ , which I use for building the chroot-custom images with "ltsp image <chroot dirname>"
| |
17:19 | * "chroot" directorIES
| |
17:22 | <alkisg> It's possible to boot the chroots OR the images
| |
17:22 | chroot nfs vs image nfs
| |
17:25 | <ltspnoob> 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...)
| |
17:25 | <alkisg> Yes, as nfs directories, vs nfs images
| |
17:26 | It's slower, but useful in faster troubleshooting or in maintaining images of different architectures
| |
17:26 | <ltspnoob> I see. which is the preferred way?
| |
17:26 | ah ok. I see.
| |
17:26 | Interesting...
| |
17:28 | <alkisg> If you do not want them to be listed, you can put them elsewhere, and run ltsp image /full/path/to/chroot
| |
17:30 | <ltspnoob> 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". :') :')
| |
17:30 | <alkisg> Btw about metacity, it's not a problem if you want to use a chroot, but that bug doesn't seem related to ltsp,
| |
17:30 | it will probably appear if you copy the chroot to a local disk with grub etc, so you can troubleshoot the issue there
| |
17:33 | <ltspnoob> 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.
| |
17:33 | <alkisg> KDE currently is lighter than mate, which is lighter than xfce
| |
17:33 | So we'll probably switch to KDE in the next deployment in schools here
| |
17:34 | <vagrantc> oh wow
| |
17:34 | <alkisg> (from mate)
| |
17:36 | <ltspnoob> I see! good to know!
| |
17:39 | 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 (ltspnoob!~ltspnoob@riddle.wizard.ca, Quit: Client closed) | |
17:59 | <alkisg> Yes
| |
18:55 | ltspnoob has joined IRC (ltspnoob!~ltspnoob@riddle.wizard.ca) | |
18:59 | <ltspnoob> 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)
| |
19:01 | and ..after getting the server back awake.. rerunning "ltsp image /" resulted in an error at the very last stage: " adm (4)
| |
19:01 | systemd-journal (101)
| |
19:01 | syslog (110)
| |
19:01 | x2goprint (137)
| |
19:01 | mv: cannot stat '/srv/ltsp/images/x86_64.img.tmp': No such file or directory
| |
19:01 | LTSP command failed: mv /srv/ltsp/images/x86_64.img.tmp /srv/ltsp/images/x86_64.img
| |
19:01 | Aborting ltsp
| |
19:01 | Emulating a shell, type `return [0|1]` to continue|exit:
| |
19:01 | "
| |
19:02 | running it again now and see if that happens again.. (no disk space issues)
| |
19:09 | It succeeded this time. :D
| |
19:09 | so... not sure what happened earlier..
| |
19:21 | 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?
| |
19:22 | <alkisg> ltsp initrd on the server and client reboot sends the passwd to the client
| |
19:22 | For custom, /etc/ltsp/passwd
| |
19:23 | <ltspnoob> Thanks! I will go try that!
| |
19:29 | 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...
| |
19:35 | Correction: "running ltsp initrd with the /etc/group in /etc/ltsp/group" did result in /etc/group in the client being updated..
| |
19:36 | Although.. only 2 out of the 10 entries got through .and those 2 entries.. are missing additional users after the groups
| |
19:36 | e.g. original /etc/group's custom entries:
| |
19:38 | group1:x:501:user1,user2,user3 group2:x:501:user1:user2 , ... group10... => ended up as group2:x:502:user .. group7:x:507:user1
| |
19:44 | update: the server went into suspended mode again somehow... without me running "ltsp image /"
| |
20:01 | woernie has left IRC (woernie!~werner@p5ddec030.dip0.t-ipconnect.de, Ping timeout: 252 seconds) | |
20:01 | woernie has joined IRC (woernie!~werner@p578bb7b6.dip0.t-ipconnect.de) | |
20:02 | <alkisg> I don't think that "suspend mode" is related to ltsp somehow
| |
20:10 | <ltspnoob> 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
| |
20:31 | 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 (woernie!~werner@p578bb7b6.dip0.t-ipconnect.de, Ping timeout: 256 seconds) | |
20:38 | <ltspnoob> 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) | |
20:46 | <alkisg> ltspnoob: anything under /etc/ltsp goes to the client /etc/ltsp
| |
20:46 | Then, with a POST_INIT directive, symlink it wherever you need
| |
20:47 | (ltsp initrd needed of course)
| |
21:09 | mistik1 has left IRC (mistik1!~mistik1@96.43.180.28, Ping timeout: 255 seconds) | |
21:45 | ltspnoob has left IRC (ltspnoob!~ltspnoob@riddle.wizard.ca, Quit: Client closed) | |
22:03 | ltspnoob has joined IRC (ltspnoob!~ltspnoob@riddle.wizard.ca) | |