Wowza process apparently runs as root on my managed dedicated server, so when create new /application sub-directories, then Wowza creates sub-directories under mine (e.g. sharedobject) which are owned by root.
Since I don’t have root access, this means I have to file a support ticket with my host provider in order to delete the /application sub-directory which I created.
The “solution” (work-around) my host offered is to run a script on cron that chown’s to my userid, all sub-directories in the hierarchy under /application. The caveats cause tsuris:
The sub-directories won’t be writable or deletable by me for up to the max period of the cron cycle.
Some SFTP clients (e.g. at least the older version of VanDyke’s SecureFX I am using) may cache the owner id and permission bits, so I will actually have to remember to close the open connection window (not just disconnect) and re-connect, if I had already been “Access denied” in that session on a Wowza process created sub-directory delete (rename, etc).
Have to remember to transport this cron script to any new server. Adds to the number of little things that have to be remembered.
Is a burden on every managed host, especially if they do not yet know about this issue and will have to field a support ticket, figure it out, then contemplate a solution.
Is it possible to arrive at a more correct solution for managed hosting? Could the Wowza process chown to the owner of the parent directory? And/or, could there be some admin tool?
Speaking of need for admin tools:
P.S. note I am not referring to a shared server, as that would require a separate Wowza directory for each user.