Smart questions
Smart answers
Smart people
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Member Login

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips now!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

Join Tek-Tips
*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

LINK TO THIS FORUM!

Add Stickiness To Your Site By Linking To This Professionally Managed Technical Forum.
Just copy and paste the
code below into your site.

Partner With Us!

"Best Of Breed" Forums Add Stickiness To Your Site
Partner Button
(Download This Button Today!)

Feedback

"...I've learned more from your forums in 3 days than 3 months at school and on the job combined..."

Geography

Where in the world do Tek-Tips members come from?
theniteowl (Programmer)
24 May 12 10:05
I expect this should be easy but...

We have a NAS folder mounted on our Unix server under the name of dms.
We have a process that watches that folder for files to appear and then to process them. The process runs under an account named ops.
When the files appear in the folder they show up with root as the owner and the ops account does not have sufficient permissions to handle the files.

I changed the owner of the folder to ops but the files still come up owned by root. How can I get the files to come up with ops as the owner or at least assign ops sufficient permissions to modify/delete the files?

I have only previously had to modify rights on individual files and I am missing something in the folder permissions area.

Thanks.

At my age I still learn something new every day, but I forget two others.

SamBones (Programmer)
24 May 12 12:17
You can't have them automatically be owned by a different owner than the creator unless it's done via an "su" or "sudo" or something similar. Since it is "root" that's creating the file, it could do a "chown" on the file after it's created to change the file's owner.

You could also have the process that creates the file do a "umask 000" right before creating it. That will set the file's permissions to "-rw-rw-rw-" which will allow anyone to modify or delete the files.

Annihilannic (MIS)
24 May 12 21:33

Quote (SamBones)

You could also have the process that creates the file do a "umask 000" right before creating it. That will set the file's permissions to "-rw-rw-rw-" which will allow anyone to modify or delete the files.

Modify, yes, but to delete they will need write permission to the directory containing the file as well.

Annihilannic
tgmlify - code syntax highlighting for your tek-tips posts

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close