Re: Nimby and LockAllCores

Cam Wright

Thanks Brian.


$ cuerqd $HOSTNAME --lh

..successfully locked the cores, in that rqd let the current
dispatched frames finish and no more were dispatched, but then running
the '--ulh' flag didn't undo that, and I needed to restart the rqd
service before more frames would get dispatched again.

So that's somewhat workable, but not perfect.

I guess what I'm really trying to achieve is a process where an artist
can arrive in the morning, run a command to kill all dispatched frames
on their workstation immediately (regardless of their progress) and
then run another script when they leave (or we can automate it based
on X-session idle time) that will reopen those cores for business to
give us extra grunt overnight.

I suppose in the meantime I could hack together a 'systemctl stop rqd'
to kill all running frames, and then a 'systemctl start rqd' to bring
it back online.. but then Cuebot assumes the system is offline, which
isn't perfect but might be feasible... I was hoping there'd be a nicer
solution though.


Cam Wright

On Thu, Aug 22, 2019 at 5:29 AM Brian Cipriano via Lists.Aswf.Io
<> wrote:

Thanks Cam. Sounds like you've found a bug here, and your diagnosis sounds accurate -- RQD using "localhost" as a default is likely causing problems due to mismatch with the name reported to Cuebot.

Let us know if that fixes it for you!

- brian

On Tue, Aug 20, 2019 at 5:52 PM Cam Wright <cam.wright@...> wrote:

So.. it seems in my haste last night I didn't RTFM and completely missed the hostname arg to cuerqd... so that might have just solved my problem.

Join to automatically receive all group messages.