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 OPENSOLARIS
sum
sum(1B) SunOS/BSD Compatibility Package Commands sum(1B)NAME
sum - calculate a checksum for a file
SYNOPSIS
/usr/ucb/sum file...
DESCRIPTION
sum calculates and displays a 16-bit checksum for the named file and displays the size of the file in kilobytes. It is typically used to
look for bad spots, or to validate a file communicated over some transmission line. The checksum is calculated by an algorithm which may
yield different results on machines with 16-bit ints and machines with 32-bit ints, so it cannot always be used to validate that a file has
been transferred between machines with different-sized ints.
USAGE
See largefile(5) for the description of the behavior of sum when encountering files greater than or equal to 2 Gbyte ( 2^31 bytes).
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWscpu |
+-----------------------------+-----------------------------+
SEE ALSO sum(1), wc(1), attributes(5), largefile(5)DIAGNOSTICS
Read error is indistinguishable from EOF on most devices; check the block count.
NOTES
sum and /usr/bin/sum (see sum(1)) return different checksums.
This utility is obsolete.
SunOS 5.11 8 Nov 1995 sum(1B)