Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

problems with chown

Status
Not open for further replies.

unixwhoopie

Programmer
May 6, 2003
45
US
my script is kicked off by an external process. so whenever a log file is created, it is created with the external process' owner id, thus making it difficult for me to read the file.

I tried chown and also copying the file onto a seperate dir. No help so far.

Any ideas?

thanks
 
in your script, after the log file is created, type chmod 666. This gives everyone read and write rights to the log file.
 
Only root can chown the user on the file. Do you need to own the file or just be part of a group that can access? Is the log file being created by the script? Try adding after the logfile is created:

chmod 740 /path/filename
chgrp groupname /path/filename
(groupname should be one that you belong to)

Change 740 to 770 if you need full access to the file.

[morning] needcoffee
 
If you are able influence the sysadmin for your unix box, then ask them to put 'umask 000' into the .profile of the external user. It might help if you pretended to be their friend.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top