I don't see what you want. How is the file presented to the program? as an argument? by a list of files in any folder the program reads?
Next, why would you care to know?, how is it going to help you?
Perhaps it's an idea to give some more information, so one of us can help you with a possible solution you're looking for.
On this moment, i can only say, look at the filename, if it's something like //foo/bar
it's probably 'remote', but that would not be taken for granted on a linux system where a misspelled // is just / (the root).
Next, i'd be careful with files that i don't even know where they come from...
Ah i understand now. Indeed as stated below use stat
as stated there
, you can see:
0 dev device number of filesystem
1 ino inode number
2 mode file mode (type and permissions)
3 nlink number of (hard) links to the file
4 uid numeric user ID of file's owner
5 gid numeric group ID of file's owner
6 rdev the device identifier (special files only)
7 size total size of file, in bytes
8 atime last access time in seconds since the epoch
9 mtime last modify time in seconds since the epoch
10 ctime inode change time in seconds since the epoch (*)
11 blksize preferred block size for file system I/O
12 blocks actual number of blocks allocated
"We all agree on the necessity of compromise. We just can't agree on when it's necessary to compromise." - Larry Wall.