statler has left IRC (statler!~Georg@p5489790B.dip0.t-ipconnect.de, Remote host closed the connection)

09:30

nehemiah has left IRC (nehemiah!~nehemiah@hs-user-138.wia.cz, Remote host closed the connection)

11:57

Faith has joined IRC (Faith!~Paty_@unaffiliated/faith)

12:10

mads2 has joined IRC (mads2!~mads2@2804:14c:878d:9567:4955:9ed1:58e0:669e)

13:41

mwalters has joined IRC (mwalters!~ubox@c-73-152-61-86.hsd1.va.comcast.net)

13:43

<mwalters>

alkisg: looks like there's no epoptes command line API right now? (e.g., log off someone via a command)

13:45

like 90% of our users leave their machines logged in overnight, thinking about logging everyone off around 0200 or so to make sure they have updated images

13:58

<alkisg>

mwalters: cron?

14:01

You can even launch an "at" command from the epoptes execute dialog...

14:02

<mwalters>

ideally cron, yes

14:03

oh

14:03

I get what you're saying... a cron job in the image

14:04

I can't keep up with so many layers of abstraction @_@

14:04

One of these days my sanity is going to be abstracted away

14:05

But yes, thanks... that sounds much less complicated than what I was thinking of doing ;)

14:08

I dropped that CPU idlestate script in last night... best I can tell, I think it may have fixed my J1900s freezing

14:08

Also, I dropped another with `chvt 7` in there, which seems to have solved certain clients sometimes booting to tty1 (I only use tty7 for clients)

14:10

I had to modified the intel_cstate script from the one that I found, my C6 states were named a bit different from the one in that bug thread, I can share if anyone runs into that issue... J1900s are pretty old now, though

14:21

<mads2>

Any idea why my clients hang on "Stop job is running for Raise network interfaces" when I try to shutdown them? I tried "shutdown -h now", "halt" and the power off in the GUI, all with the same result.

14:21

Here are pics of it https://imgur.com/a/8xlVIYR

14:25

<alkisg>

(04:03:48 PM) mwalters: I get what you're saying... a cron job in the image ==> or in lts.conf

14:25

mads2: are you using the greek schools ppa?

14:26

<mads2>

@alkisg: yes. Ubuntu LTS and greek ppa

14:26

<alkisg>

mads2: which ubuntu lts?

14:26

16, 18?

14:27

<mads2>

18

14:27

<alkisg>

chroot or chrootless?

14:27

<mads2>

chroot, back to NFS

14:28

<alkisg>

And are you sure that your chroot does have the ppa?

14:28

What's the output of sudo ltsp-info?

14:28

<mads2>

I'm not in my lab right now. But I'm sure.

14:28

Doing some research, it may not be related to the LTSP

14:29

but to systemd or some network driver

14:29

<alkisg>

That symptoms is seen when one does not have the ppa

14:29

I solved it and uploaded a new version to the ppa

14:29

But if you say you are SURE... let's continue when you're at the lab

14:29

<mads2>

really? recently? I'll try to upgrade the system when I get there

14:30

<alkisg>

In late august

14:30

<mads2>

unnn. So it's probably not the problem.

14:31

but I will verify it just to be sure sure

14:31

bengoa has left IRC (bengoa!~alberto@194.50.55.200)

14:31

bengoa has joined IRC (bengoa!~alberto@194.50.55.200)

14:31

<alkisg>

It's very usual that people think they have the ppa in the chroot, but they don't