Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*noatime\s*$/: 41 ]

Total 41 documents matching your query.

1. Re: noatime (score: 1)
Author: Greg Freemyer <freemyer-ml@xxxxxxxxxxxxxxxxx>
Date: Mon, 02 Feb 2004 14:55:34 -0500
Part of my company does computer forensics. As part of that our forensics team might testify in court that "Rob created a flat file export of the Customer Database on Dec 15, 03. He accessed this fla
/archives/xfs/2004-02/msg00009.html (9,718 bytes)

2. Re: noatime (score: 1)
Author: Robert Brockway <robert@xxxxxxxxxxxxxxxxx>
Date: Mon, 2 Feb 2004 16:30:11 -0500 (EST)
I do know of one such use of atime by a friend of mine while tracking an errant user. The problem (as I see it) is that a knowledgable user who owns the file or has root access (all too common on man
/archives/xfs/2004-02/msg00010.html (9,024 bytes)

3. Re: noatime (score: 1)
Author: Bernd Petrovitsch <bernd@xxxxxxxxx>
Date: Tue, 03 Feb 2004 00:36:45 +0100
Given the possibilities to fake that info it is[0] (for usage in court or similar) probably better to actually have no atime. But if you (or someone) wants to use it in court (or similar) it should n
/archives/xfs/2004-02/msg00017.html (9,174 bytes)

4. Re: noatime (score: 1)
Author: Greg Freemyer <freemyer-ml@xxxxxxxxxxxxxxxxx>
Date: Mon, 02 Feb 2004 19:12:34 -0500
I don't do the forensic work myself but I know our examiners try to use the access time (and create/modify). FYI: About 10 years ago I was working at a company were a manager inadvertently corrupted
/archives/xfs/2004-02/msg00021.html (11,255 bytes)

5. Re: noatime (score: 1)
Author:
Date: Mon, 02 Feb 2004 14:55:34 -0500
... -Eric
/archives/xfs/2004-02/msg00344.html (9,718 bytes)

6. Re: noatime (score: 1)
Author:
Date: Mon, 2 Feb 2004 16:30:11 -0500 (EST)
this fla
/archives/xfs/2004-02/msg00345.html (9,024 bytes)

7. Re: noatime (score: 1)
Author:
Date: Tue, 03 Feb 2004 00:36:45 +0100
atly appr
/archives/xfs/2004-02/msg00352.html (9,174 bytes)

8. Re: noatime (score: 1)
Author:
Date: Mon, 02 Feb 2004 19:12:34 -0500
t would g
/archives/xfs/2004-02/msg00356.html (11,255 bytes)

9. noatime (score: 1)
Author: AndyLiebman@xxxxxxx
Date: Fri, 30 Jan 2004 12:04:26 EST
ort
/archives/xfs/2004-01/msg00348.html (7,368 bytes)

10. Re: noatime (score: 1)
Author: Edmund White <ewwhite@xxxxxxx>
Date: Fri, 30 Jan 2004 11:12:16 -0600 (CST)
le?
/archives/xfs/2004-01/msg00349.html (8,677 bytes)

11. Re: noatime (score: 1)
Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Fri, 30 Jan 2004 17:13:14 +0000
://
/archives/xfs/2004-01/msg00350.html (8,367 bytes)

12. Re: noatime (score: 1)
Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Fri, 30 Jan 2004 17:24:18 +0000
FS.
/archives/xfs/2004-01/msg00351.html (8,406 bytes)

13. Re: noatime (score: 1)
Author: AndyLiebman@xxxxxxx
Date: Fri, 30 Jan 2004 12:54:57 EST
, a
/archives/xfs/2004-01/msg00353.html (7,453 bytes)

14. Re: noatime (score: 1)
Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Fri, 30 Jan 2004 17:57:56 +0000
is
/archives/xfs/2004-01/msg00354.html (8,317 bytes)

15. Re: noatime (score: 1)
Author: AndyLiebman@xxxxxxx
Date: Fri, 30 Jan 2004 13:44:40 EST
1.1
/archives/xfs/2004-01/msg00356.html (7,575 bytes)

16. Re: noatime (score: 1)
Author: Robert Brockway <robert@xxxxxxxxxxxxxxxxx>
Date: Sat, 31 Jan 2004 03:37:01 -0500 (EST)
nic
/archives/xfs/2004-01/msg00358.html (8,976 bytes)

17. Re: noatime (score: 1)
Author: Marc Schmitt <mschmitt@xxxxxxxxxxx>
Date: Sat, 31 Jan 2004 11:26:23 +0100
ked
/archives/xfs/2004-01/msg00359.html (8,265 bytes)

18. Re: noatime (score: 1)
Author: Ethan Benson <erbenson@xxxxxxxxxx>
Date: Fri, 30 Jan 2004 23:52:51 -0900
arc
/archives/xfs/2004-01/msg00360.html (9,998 bytes)

19. Re: noatime (score: 1)
Author: Stefan Smietanowski <stesmi@xxxxxxxxxx>
Date: Sat, 31 Jan 2004 14:12:32 +0100
uns
/archives/xfs/2004-01/msg00361.html (8,662 bytes)

20. noatime (score: 1)
Author: AndyLiebman@xxxxxxx
Date: Fri, 30 Jan 2004 12:04:26 EST
to sort
/archives/xfs/2004-01/msg00714.html (7,368 bytes)


This search system is powered by Namazu