Permissions Help???

[stu78]

Hi,

I am seeing some strange behavior on our hardened build when installing some software, which I think are permissions based errors.

I have used lsof & truss to see what the problem might be, does anyone else know the best way to see what file/perms are causing a process to fails?

DC

 

[KenCunningham]

What is the 'strange behavior' and how does it manifest itself?

 

[stu78]

Hi,

Basically I am installing software - which maintains it's own log file.

I can log fine to /tmp for example, but I need to log to a specific file system as a certain user.

As this user I can touch a file in the directory I neeed to log to, but when I run the daemon that should log, it fails... I'm pretty sute it's a perms issue, but if anyone knows good commands to troubleshoot this?

That's kinda what I'm looking for;
DC

 

[SamBones]

We'd need more information. Specific information.

1) What is the owner, group, and permissions of the directory you want to write the log to?

2) What is the owner and group of the userid that needs to write to the directory?

3) Are you sure the daemon is running with the userid you think it is?

4) Is there an ACL on the directory? (Try [tt]getfacl -d /logdir[/tt])

5) When the daemon that tries to open the log file fails, are there any error message?

6) Are there any system messages being logged? (Try [tt]cat /var/adm/messages[/tt] and look for something from the daemon)

7) Is that file system full?

Anyway, there's a lot of possibilities. More information would help.

 

[SamBones]

And to answer your original question, [tt]truss[/tt] is usually the best for finding why a program can't open or find a file. You can find the call where it tries to open the log file, then follow what it does when it gets a FAILURE return code from the open() call.

Hope this helps.