Hi. I have a script which is deleting files with a particular extension and older than 45 days.The code is:
find <path> -name "<filename_pattern>" -mtime +45 -exec rm {} \;
But the problem is that some important files are also getting deleted.To prevent this I have decide to make a dummy... (4 Replies)
I'm writing a c program to list the files in a given directory but I also want to display the hidden files. I can't figure this out in c. Does anyone know how to do this? Here's the code I have so far:
#include <unistd.h>
#include <stdio.h>
#include <dirent.h>
#include <string.h>
#include... (2 Replies)
I have a bunch of hidden files in a directory in AIX. I would like to move these hidden files as regular files to another directory.
Say i have the following files in directory /x
.test~1234~567
.report~5678~123
.find~9876~576
i would like to move them to directory /y as
test~1234~567... (10 Replies)
Find all files in the current directory only excluding hidden directories and files.
For the below command, though it's not deleting hidden files.. it is traversing through the hidden directories and listing normal which should be avoided.
`find . \( ! -name ".*" -prune \) -mtime +${n_days}... (7 Replies)
I wanted to grep some text Recursively, without going through hidden files(.files/.folders)
In my Repo there are lot of .svn folders/subfolders etc.
I dont want to grep in that folders.
Hidden folders can be .svn or .<anyotherfoldername>
Can you give teh command whcih does it "Recursively" (5 Replies)
Hello.
I use this command :
rsync -av --include=".*" --dry-run "$A_FULL_PATH_S" "$A_FULL_PATH_D"The data comes from the output of a find command.
And no full source directories are in use, only some files.
Source example... (2 Replies)
Discussion started by: jcdole
2 Replies
LEARN ABOUT HPUX
sum
sum(1) General Commands Manual sum(1)NAME
sum - print checksum and block or byte count of file(s)
SYNOPSIS
[file ...]
Remarks
is obsolescent and should not be used in new applications that are intended to be portable between systems. Use instead (see cksum(1)).
DESCRIPTION
calculates and prints to standard output a checksum for each named file, and also prints the size of the file in 512 byte blocks, rounded
up.
The default algorithm is a 16-bit sum of the bytes in which overflow is ignored. Alternate algorithms can be selected with the and
options.
Standard input is used if no file names are given.
is typically used to verify data integrity when copying files between systems.
Options
recognizes the following options:
Use an alternate algorithm in which the 16-bit sum is right rotated
with each byte in computing the checksum.
Use the 32-bit cyclical redundancy check (CRC) algorithm used by
RETURN VALUE
returns the following values upon completion:
All files were processed successfully.
One or more files could not be read or some other error occurred.
If an inaccessible file is encountered, continues processing any remaining files, but the final exit status is affected.
DIAGNOSTICS
Read error conditions are indistinguishable from end of file on most devices; check the block or byte count.
WARNINGS
This command is likely to be withdrawn from X/Open standards. Applications using this command might not be portable to other vendors'
platforms. The usage of cksum(1) is recommended.
SEE ALSO cksum(1), wc(1).
STANDARDS CONFORMANCE sum(1)