Messages in this thread |  | | Date | Sun, 20 Aug 2000 21:49:31 -0400 (EDT) | From | "Richard B. Johnson" <> | Subject | Re: Why does utime() exist? |
| |
On Sat, 19 Aug 2000, Julien Oster wrote:
> Hello! > > Why the heck does utime() exist? I could understand it, if it would only > have a filename as argument and issuing it would change the access and/or > modification time to the current time - also known as "touch"ing files. > Tar and other backup/restore programs need it. Without it, when you restore a bunch of files from a backup, they would all have the date/time at which you restored them rather than the date/time that was preserved during the backup.
> > Is it safe to disable it? It makes life a little harder for system > administrators concerned about security... >
Really? Tell me how (off-the-list, please). POSIX requires this.
Cheers, Dick Johnson
Penguin : Linux version 2.2.15 on an i686 machine (797.90 BogoMips).
"Memory is like gasoline. You use it up when you are running. Of course you get it all back when you reboot..."; Actual explanation obtained from the Micro$oft help desk.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org Please read the FAQ at http://www.tux.org/lkml/
|  |