Now, this is funny - this is eactly what i thought to be the case, until Don said it can't be that way. The same reasoning led me to think that any file sized >0c is selected by -size 1G - because it is "rounded up" to the next full GB.
Now completely confused.
bakunin
Hi Bakunin,
Don't be confused. What we see here is another case where GNU utilities and BSD utilities behave differently. (And, some UNIX systems don't offer the extension at all.) You get exactly the same behavior on BSD, Linux, and UNIX systems for:
which are the -size primary argument formats required by the POSIX standards, but the behavior of:
where one of the optional size multipliers is supplied is likely to give you a syntax error on some UNIX-branded systems, one of the two behaviors that we have discussed in this thread on Linux systems (and maybe on some UNIX-branded systems), and the other behavior on BSD-based systems and at least one UNIX-branded system.
This User Gave Thanks to Don Cragun For This Post:
Hi--
Ok. I have now found that:
find -x -ls
will do what I need as far as finding all files on a particular volume. Now I need to sort the results by the file's modification date/time.
Is there a way to do that?
Also, I notice that for many files, whereas the man for find says ls is... (8 Replies)
I am looking for files of a certian type and logging them. After they are logged they need to be moved to a different directory. HOw can i incorporate that in my current script?
CSV_OUTFILE="somefile.csv"
find . -name W\* -exec printf "%s,%s,OK" {} `date '+%Y%m%d%H%M%S'` \; > ${CSV_OUTFILE}
... (9 Replies)
I'm attempting to read a file that is composed of complex 32-bit floating point values on Solaris 10 that came from a 64-bit Red Hat computer.
When I first tried reading the file, it looked like there was a byte-swapping problem and after running the od command on the file Solaris and Red Hat... (2 Replies)
I was running some timings in my code to see which of several functions was the best and I've been getting some odd results. Here's the code I'm using:
static double time_loop(int (*foo)(int)) {
clock_t start, end;
int n = 0, i = 0;
start = clock();
for (; i <= MAXN; i++)
if... (6 Replies)
I have an issue with a korn shell script that I am writing. The script parses through a configuration file which lists a heap of path/directories for some files which need to be FTP'd. Now the script needs to check whether there are any files which have not been processed and are X minutes old.
... (2 Replies)
Hi,
I have a problem with a shell script.
The script should find all .cpp and .h files and list them.
With:
for file in `find $src -name '*.h' -o -name '*.cpp'
it gives out this:
H:\FileList\A\E\F\G\newCppFile.cpp
H:\FileList\header01.h
H:\FileList\B\nextCppFile.cpp
... (4 Replies)
Hi,
Am running the command below to search for files that contains a certain string.
grep -il "shutdown" `find . -type f -mtime -1 -print` | grep "^./scripts/active"
How do I get it to do a ls -l on the list of files? I tried doing ls -l `grep -il "shutdown" `find . -type f -mtime -1... (5 Replies)
i feel weird with this 2 command
find /tmp/*test* -user `whoami` -mtime +1 -type f -exec rm -f {}\;
find /tmp/*test* -user `whoami` -mtime +1 -type f -exec ls -lrt {}\;
the first one return correct which only delete those filename that consist *test* where second command it listed all the... (12 Replies)
I have a text file downloaded from the web, I want to count the unique words used in the file, and a person's speaking length during conversation by counting the words between the opening and closing quotation marks which differ from the standard ASCII code. Also I found out the file contains some... (2 Replies)
Discussion started by: yifangt
2 Replies
LEARN ABOUT HPUX
standards
standards(5) File Formats Manual standards(5)NAME
standards - UNIX standards behavior on HP-UX
DESCRIPTION
HP-UX conforms to various UNIX standards. In some cases, these standards conflict. This manpage describes the methods that programmers
and users must follow to have an application conform and execute according to a particular UNIX standard.
UNIX Standard Conformant Programmer Environment
The following table lists feature test macros and environment variables that must be defined while compiling an application. Both a fea-
ture test macro and an environment variable must be defined while compiling the application so that the application conforms and executes
according to a particular UNIX standard. Otherwise, the behavior is undefined.
Standard Feature Test Macros to be Environment variable
defined during compilation to be set
UNIX 95 _XOPEN_SOURCE_EXTENDED=1 UNIX95 or
UNIX_STD=95 or
UNIX_STD=1995
UNIX 2003 _XOPEN_SOURCE=600 UNIX_STD=2003
The compiler uses the feature test macros to obtain the appropriate namespace from the header files. The compiler uses the environment
variable to link in an appropriate object file to the executable. Using the environment variable customizes libc to match UNIX standards
for various functions.
If an application has already been compiled for default HP-UX behavior or for one particular standard, and needs to change to a particular
UNIX standard behavior, recompile the application as specified in the above table.
For an HP-UX command to conform to a particular UNIX standard behavior, the application has to set the corresponding environment variable
as specified in the above table before executing that command.
UNIX Standard Conformant User Environment
To enable a particular UNIX standard conformant user environment, set the corresponding environment variable as defined in the above table.
EXAMPLES
The following examples shows an application example. To have the system be conformant to UNIX2003 behavior, set the environment variable
to and define the feature test macro before compilation.
The following example changes the command to have UNIX95 behavior by setting one of the environment variables to or to before executing
that command. There are three ways of setting the environment variable for UNIX95:
or
or
SEE ALSO cc(1), stdsyms(5).
standards(5)