Mansur, Warren [EMAIL PROTECTED] writes:
If we disable the last access time on the machine, will it mess up any applications?
I always thought the atime was kind of useless but I don't know if some applications
use it in an esoteric way.
[please configure your email program to wrap lines
On 26 Mar 2002, at 8:03am, Kevin D. Clark wrote:
I would encourage people to not mess around with [the noatime mount]
option.
I would encourage people to do what meets their needs.
In many situations, the atime field is either not useful, or actively bad
for performance.
In general,
Sorry for wading in here, but I have about 5 minutes to spare, ...
Some places use the atime field to archive (or remove) files that are unused.
I've worked at several shops where they have large reports that just
accumulate daily, and they manage their disk space using the atime feature - if
At 10:40 AM 3/26/2002 -0500, [EMAIL PROTECTED] wrote:
Sorry for wading in here, but I have about 5 minutes to spare, ...
SNIP.
Keep in mind that their definition of access means read - not modified.
One more tidbit: - the man page for stat(2) states that the atime (access
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Your e-mail client is wrapping somewhere around 90 columns. On this
list, it is generally regarded good netiquette to wrap at less than 80
colums, and most consider 72 idea. Please configure it to something
less than 80.
At some point hitherto,
out how then it will help (me at least).
Regards,
Warren
-Original Message-
From: Derek D. Martin [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, March 26, 2002 11:43 AM
To: Greater NH Linux Users' Group
Subject: Re: Atime [Was: behavior of find /]
-BEGIN PGP SIGNED MESSAGE
At 11:42 AM 3/26/2002 -0500, Derek D. Martin wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Your e-mail client is wrapping somewhere around 90 columns. On this
list, it is generally regarded good netiquette to wrap at less than 80
colums, and most consider 72 idea. Please configure it to
This has been puzzling me for weeks. If (as root) I type
find / -print |grep somefilename
sometimes it takes many minutes, sometimes it completes in seconds and
sometimes I get a new shell prompt but I can hear the disk grinding away for
many seconds after the command seems to have
On Mon, 25 Mar 2002, at 7:52pm, Tom Rauschenbach wrote:
This has been puzzling me for weeks. If (as root) I type
find / -print |grep somefilename
sometimes it takes many minutes, sometimes it completes in seconds ...
Sometimes the system has to walk the directory tree on disk, sometimes
Many filesystems maintain a notation of the last access time of a
filesystem object. Under Unix/Linux, this is called the atime.
Directories are generally considered filesystem objects. So,
when you walk
the directory tree, you touch the atime of every directory.
All of those
updated
On Mon, 25 Mar 2002, at 8:46pm, Mansur, Warren wrote:
If we disable the last access time on the machine, will it mess up any
applications?
Only those that use it.
--
Ben Scott [EMAIL PROTECTED]
| The opinions expressed in this message are those of the author and do not |
| necessarily
11 matches
Mail list logo
