CGRU Forum

My apologies, I will try to dig into the issue and provide you with some more concrete information. I have tried to look at the archives the submission script creates, but since they appear to me, to be binary files, I'm afraid it's out of my depth. I will check and see if I can gather any informati...

Hi, with clarisse 3.6, some projects when submitted with "create render archive" checked, end up as unreadable files which do not render. It's not a huge issue, as you can de-check it and type in the *.project file instead, but anyway, thought I should mention it.

Ah! yes I'm sorry I wasn't more clear about that, that makes sense in that case. Sorry for the confusion.

Peter.

Hi, happy to help if I can... it builds without any issue, no errors at all. All compiled binaries (afserver, afrender etc) seem to work as expected, however python script does not want to run at all... even a simple script such as thumbs.py. It's very possible I could be doing something wrong, but ...

I found a small hack for getting cgru to work better in an updated Arch install. The main issue is that Arch maps python to it's always updated and bleeding edge python3 version(3.6), most other distros still link to python2. I have not understood why python3 does not work well with the py scripts i...

Thanks Timur, got it.

Haha, yes we do the same here... No accidents so far... But as a paranoid sysadmin I'm always suspecting the worst. Could you maybe let me know where the 0777 settings are for the rules folders and it's contents? I'd like to taka a stab in implementing a decent permission structure here with a few r...

Hi Timur, would you mind letting us know a little on how you suggest implementing RULES in terms of permissions and security? I noticed that RULES creates 777 files and directories, for instance when asking it to do a walk or make thumbnails (I guess it's actually user render that creates the .rules...

Hi Jakob, I find that writing a small oneshot service script was easiest... Then I just keep the afserver and afrender in the /usr/local/bin folder. Here's an example service script (/etc/systemd/system/afserver.service): [Unit] Description=AFServer After=network.target [Service] Type=oneshot ExecSt...

Ok, got it working now. I ended up using the path mapping :

/cgru/, /mnt/cgru/

And the rules_link: /mnt/projects