Hi,
sorry for my very first and maybe stupid question.
I have a little Note / Docs which tells me to set following Cronjobs:
0 * * * * chmod -R 777 /usr/local/WowzaStreamingEngine/applications/
0 * * * * chmod -R 777 /usr/local/WowzaStreamingEngine/conf/
1 */1 * * * chmod -R 777 /usr/local/WowzaStreamingEngine/logs/
Is there any Reason for it, to be 777? I would never create such rights, except if its save and required.
But i can’t imagine.
Can’t i use 755 for Folders and 644 for the Files?
Thank you in advance
Hello and welcome- that’s not stupid at all, it’s some advanced admin info. I’m confirming with tech support as far as the specific folders you mention.
In the meantime, is this the doc you’re looking for?
Change ownership and permissions on the Wowza Streaming Engine installation files. For example:
cd /usr/local
chown -h wowza:wowza WowzaStreamingEngine
chown -R wowza:wowza WowzaStreamingEngine-4.0.1
chmod -R 775 WowzaStreamingEngine-4.0.1
rm -f /var/run/WowzaStreamingEngine*
https://www.wowza.com/docs/how-to-run-wowza-streaming-engine-as-a-named-user-linux-and-os-x
1 Like
Tech support agrees that 777 is a bad idea. They suggest you do not change the default which is right now set as 757 for those directories. If you are really being told to change it to something else, the engineers suggest you send in a support ticket and discuss the reasons why.
I hope this helps.
1 Like
Thank you for confirmation. I thought that. I will try with 757 instead of 755 though.
1 Like
I’d stick with 755 or 775. If you do 757, you may as well do 777. And I don’t see why anyone else but the user/group needs full access to these folders.
1 Like