On Lu, 28 iul 14, 16:34:14, Rick Thomas wrote: > > mode=1777 sets all accesses allowed (it is “/tmp” after all…) and also > sets the “sticky bit” which (according to stat(2)) “on a directory > means that a file in that directory can be renamed or deleted only by > the owner of the file, by the owner of the directory, and by a > privileged process.”
Right, makes sense for /tmp and I kind of ignored that anyway. What I meant (and failed to explain)... > “strictatime” (according to mount(8)) "Allows to explicitly > requesting full atime updates. This makes it possible for kernel to > defaults to reltime or native but still allow userspace to override > it.” > > So in an embedded system with root on flash, but /tmp in RAM, we get > standard semantics for atime (no need to be nice to flash since the > whole filesystem is in RAM) and the usual expected behavior for > deletion/rename operations in /tmp. ... was the reason for strictatime (vs. relatime which is default, or the more aggressive noatime). Sure, it's a tmpfs, and the penalty for updating atime is probably much lower than any other conventional storage (though /tmp contents might end up being swapped), but is there any software that actually relies on atime for files in /tmp? Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic http://nuvreauspam.ro/gpg-transition.txt
signature.asc
Description: Digital signature
