Solaris / OpenSolarisThis forum is for the discussion of Solaris, OpenSolaris, OpenIndiana, and illumos.
General Sun, SunOS and Sparc related questions also go here. Any Solaris fork or distribution is welcome.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
As we have one application in which it creates files with user& group as ownership "nobody", due to that there are issues in overwriting the same file.
Can anybody suggest how we can prevent this ownership assignment as "nobody"
Distribution: Solaris 9 & 10, Mac OS X, Ubuntu Server
Posts: 1,197
Rep:
So, the application is running as user nobody. It creates files. Those files then are owned by nobody. nobody's primary group is nobody. so the group ownership is nobody. This also means that you have a directory that is writable by nobody (or, likely 777 which is writable by anybody).
The contradiction here is that you have an application you don't trust and run as nobody, yet you have a directory that you have set up to allow anyone to write to. You need to lock all of that down a bit.
Typically, if an application is running like that you want to know about it, and user nobody kind of hides it. Create a user for that application. Then if that application needs a log file or something to write to, create the log file for it and set the permissions so it can write to it. Don't have it world writable.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.