Application servers routinely run with virtually-no permissions ... the Unix/Linux equivalent of nobody. Specifically, after initially and necessarily launching as root, they promptly strip themselves of their "godliness" before beginning to accept requests.
However, you can specify the user-id and/or the set of limited permissions that they de-evolve themselves to. You can define a custom user-id which reflects the permissions that you need, and direct the server to that. However, bear in mind that this designation will now apply to "the entire server."
In reply to Re: permission denied on file write only when running browser on application server
by Anonymous Monk
in thread permission denied on file write only when running browser on application server
by raccardi
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |