Re: how to test if a file is more than one hour old in ksh
- From: "Dan Mercer" <damercer@xxxxxxxxxxx>
- Date: Fri, 25 Apr 2008 14:32:26 -0500
"Dave B" <daveb@xxxxxxxxxxxx> wrote in message news:fufrlv$19m$1@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
On Sunday 20 April 2008 18:33, Dan Mercer wrote:
Where did you read that? From the standard man page:
find [ -H | -L ] path ... [ operand_expression ... ]
find -H | -L are not standard find options - they may be Gnu find options,
but I've never seen them.
The synopsis for the standard find is
find path-name-list [expression]
Uhm, no. I copied/pasted that directly from the SUSv3 standard, so I suppose
that they *are* standard.
No, that means they are Standard (;-). Not that they are universally adopted, which find -H
isn't. HP-UX which has about a third of the market doesn't have it.
And who let that slip into the standard, anyway - two separate mechanism's for naming
options. Yuck!
Dan Mercer
--
D.
.
- Follow-Ups:
- Re: how to test if a file is more than one hour old in ksh
- From: Geoff Clare
- Re: how to test if a file is more than one hour old in ksh
- References:
- how to test if a file is more than one hour old in ksh
- From: SamL
- Re: how to test if a file is more than one hour old in ksh
- From: Ed Morton
- Re: how to test if a file is more than one hour old in ksh
- From: Dan Mercer
- Re: how to test if a file is more than one hour old in ksh
- From: Dave B
- Re: how to test if a file is more than one hour old in ksh
- From: Dan Mercer
- Re: how to test if a file is more than one hour old in ksh
- From: Dave B
- how to test if a file is more than one hour old in ksh
- Prev by Date: Re: Howto read file line-by-line in bash
- Next by Date: multi level diff using find
- Previous by thread: Re: how to test if a file is more than one hour old in ksh
- Next by thread: Re: how to test if a file is more than one hour old in ksh
- Index(es):
Relevant Pages
|
