Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: Weird 'find' results
Top Forums UNIX for Beginners Questions & Answers Weird 'find' results Post 302991835 by bakunin on Thursday 16th of February 2017 05:54:16 PM
Old 02-16-2017
Quote:
Originally Posted by Don Cragun
which is looking for regular files owned by user database that contain exactly 1073741824 bytes.
I don't think so: because the size (which is a small fraction of a GB) is rounded up to the next unit (GB here, therefore 1GB) all files with 1GB and less (but at least 1c) are shown.

I hope this helps.

bakunin
This User Gave Thanks to bakunin For This Post:
bodisha
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

find results

Hi, how can I get only useful results from find / -size 10000000 without the "Permissions denied" files ? tks C (5 Replies)
Discussion started by: Carmen123
5 Replies

2. UNIX for Dummies Questions & Answers

How to sort find results

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)
Discussion started by: groundlevel
8 Replies

3. Shell Programming and Scripting

need to move find results

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)
Discussion started by: pimentelgg
9 Replies

4. UNIX for Advanced & Expert Users

byte swapping 32-bit float and weird od results

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)
Discussion started by: GoDonkeys
2 Replies

5. Programming

Weird timing results in C

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)
Discussion started by: CRGreathouse
6 Replies

6. Shell Programming and Scripting

Find files older than X with a weird file format

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)
Discussion started by: MickAAA
2 Replies

7. UNIX for Dummies Questions & Answers

sort find results

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)
Discussion started by: shellBeginner75
4 Replies

8. UNIX for Dummies Questions & Answers

How to do ls -l on results of grep and find?

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)
Discussion started by: newbie_01
5 Replies

9. UNIX for Dummies Questions & Answers

[Solved] weird in find -exec command

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)
Discussion started by: lsy
12 Replies

10. Shell Programming and Scripting

How to find out the weird blank characters?

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

nflocks

nflocks(5)							File Formats Manual							nflocks(5)

NAME

       nflocks - maximum number of file locks

VALUES

   Failsafe
   Default
       The  default  value is computed at runtime and depends on the amount of physical memory on the system.  For small memory systems (less than
       1GB), the default is 1200.  For systems with more than 1GB of memory, the default is 4096, or 4K.

   Allowed values
       The minimum value is 50.  The maximum value is 0x1000000.

       Specify a positive integer value.

DESCRIPTION

       The tunable represents the maximum number of file locks that are available system-wide.

   Who Is Expected to Change This Tunable?
       This tunable should be changed on systems expected to run applications with large number of file locks.	When  changing	this  number  note
       that one file may have several locks, and databases that use or may need an exceptionally large number of locks.

   Restrictions on Changing
       This  tunable  is dynamic (tuning will take effect immediately on the running system).  When the value of is dynamically tuned it cannot be
       set to a value lower than the current number of file locks in the running kernel.

   When Should the Value of This Tunable Be Raised?
       The value should be increased when large numbers of file locks are expected to be used simultaneously.

   What are the Side Effects of Raising the Value?
       The kernel allocates a portion of memory proportional to the new value of and frees memory proportional to the old value.  Additional  mem-
       ory is consumed as new locks are created.

   When Should the Value of This Tunable Be Lowered?
       The value can be lowered to limit the number of available file locks on a system and reduce memory consumption.

   What are the Side Effects of Lowering the Value?
       The  kernel allocates a portion of memory proportional to the new value of and frees memory proportional to the old value.  Additional mem-
       ory may be released to the system to be used for other purposes if the usage was ever higher than this new value.

   What Other Tunable Values Should Be Changed at the Same Time?
       None.

WARNINGS

       Setting to the maximum value(0x1000000) will result in a large memory allocation (~.5GB).  A request to change the value of will fail with
       set if there is either not enough free memory or the remaining free memory would be so small as to potentially hinder system performance.

       All  HP-UX kernel tunable parameters are release specific.  This parameter may be removed or have its meaning changed in future releases of
       HP-UX.

       Installation of optional kernel software, from HP or other vendors, may cause changes to tunable  parameter  values.   After  installation,
       some  tunable  parameters may no longer be at the default or recommended values.  For information about the effects of installation on tun-
       able values, consult the documentation for the kernel software being installed.	For information about optional kernel  software  that  was
       factory installed on your system, see at

AUTHOR

       was developed by HP.

SEE ALSO

       kctune(1M), sam(1M), gettune(2), settune(2), fcntl(2), lockf(2).

							     Tunable Kernel Parameters							nflocks(5)
All times are GMT -4. The time now is 08:59 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy