Solaris

Greetings,
I need help understanding why FUSER will not bring back PSID's on mounted filesystems. Is this a common error?

Thanks in advance for your feedback.

Fuser works with files, not filesystems. What are PSID's ?
Can you give an example about what you think is an error ?

Hello,
Sorry for the delay. I work in the evenings. We have an FTP process that writes to an NFS filesystem. We have a daemon process that wakes up every now and then and issues an FUSER on the filesystem where the file is being FTP'd. When the daemon and the FTP happen on the same box, it returns the process-id's and user-ids of who has the filesystem open. However, when the FTP happens on a different machine(but the same NFS) the daemon / FUSER does not return the information, even though the FTP is writing to the filesystem. Any ideas? thanks so much for your help.

As I already commented, fuser works with files (including directories and devices) but not on file systems. Please explain better what your daemon is actually doing.

And how would an fuser process on one server be aware of a process on another server? It can't be.

Out of curiosity, how do you handle an FTP that fails in the middle of a transfer?

Greetings,
Thanks again for the support. The daemon issues an fuser on a file that is NFS mounted. So, (In theory) if a process has the file opened, the fuser would bring back the process id's and user-ids that have the file opened. It's a daemon process that was written before my time, and it has fallen on my lap to support. Currently, the daemon is moving grabbing files that are still being created by the FTP. Also, any ideas on how to identify if the FTP has not sent the complete file?

Here, fuser is properly detecting processes having a file open that is physically located on a remote server and accessed via NFS. On the NFS server side, no usage is detected as I was expected.