Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
that is written: file is successfully created, but failed to set time - because of the permissions.
Need to know umask settings and also access rights on that dir and current user (at least)
You haven't yet showed the group of honigwb, so I also look forward to the output of id.
Do you have SELinux enabled or access control lists?
If so than you also need to look at what restrictions they enforce on the current file.
yes, I can only repeat:
umask looks ok, you are on the filesystem: isilon.hpc:/ifs/data.
We know your user id and dir, but we still don't know how is this filesystem mounted (and we also don't know the settings of the original filesystem/OS).
The file you touch-ed was successfully created, but the owner (honigwb) has no any right on it, therefore time cannot be set.
(is this your homework or exam?)
Try the same (permission restrictions) on a local file system, to see if your scenario behaves the same.
mount | grep ifs/data
(Also on file server isilon.hpc)
Maybe also check the NUMERIC uids on both machines. (/etc/passwd)
Carefully COMPARE and show us the (true maybe meaning UTC) date
on both this machine and the file server isilon.hpc
Note my comment about how `ls` only reports the date and not the time IF the inode time is in the future!
stat give lots of details about an inode
I'm suspecting the time on the file server, where the inode actually lives, is in the future, relative to this machine. You can do some web research about this condition with NFS
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.