I am using SCO openserver realease 3.2 and tried to test versioning on a directory with undelete -s . The command executes well but it is not creating any versions of the files in it. I have also setted versioning options via filesystem and then remounted it but of no use.
Through scoadmin, I set
maxvdepth=3
minvtime=1
remounted the filesystem partition , then at directory level used
undelete -s <directory path>
but when I list using
undelete -l
it shows no versions even after waiting for minvtime .
Filesystem type : HTFS
Any suggestions on what may actually be the problem , are appreciated.
I have this code that works great ...
#!/bin/sh
for file in "$@"
do
ext=${file##*.}
base=${file%.*}
num=${base##*v}
zeroes=${num%%*}
num=${num#$zeroes} #remove leading zeros, or it uses octal
num=$((num+1))
base=${base%v*}
... (5 Replies)
Hi,
I need to get versioning of the branch name dynamically. can you please help us to achieve this functionality.
curl https://altrecmktg.com/artifactory/mediamarketing/release-2.0.1/altrec.tar
curl https://altrecmktg.com/artifactory/mediamarketing/release-2.0.2/altrec.tar
everytime... (5 Replies)
Hi,
In tcsh, I mistakenly deleted some files under a dir with rm *
Is there any way by which I can recover those files (without restoring to an earlier backup point) ?
I mean any command like undelete or anything similar (10 Replies)
Hi
Is there a way by which I can recover the last deleted file file from a folder.
OR
I had a file in a path .(i didnt notice the size at that time ) I tried ftp that file to my windows but got file of zero size.
I want to check whether the file was already empty when I tried ftping it... (1 Reply)
Dear Members,
Do you know any information about versioning a binary file. That means test.out 1.0.0, 1.0.1, 1.1.0, and so on. Can I manually edit version number (both major and minor) and revision number myself (how?) or any utility to set version number (which one?).
Best Regards,
Francesco (2 Replies)
Please correct me if I am wrong... Isnt the only difference between minor releases of Solaris, ex. 9/04 and 9/05, is the patche revs between them? If so, why does the /etc/release info stay static when patched? (4 Replies)
Right, a mate of mine screwed up today and deleted the entire contents of a directory and he really needs to get the files back. He's using Red Hat Enterprise Edition 4. The files were deleted using rm *. He can't remember if the hard drive was formatted using ext2 or ext3. Anybody have any idea... (0 Replies)
RM(1) BSD General Commands Manual RM(1)NAME
rm, unlink -- remove directory entries
SYNOPSIS
rm [-f | -i] [-dIPRrvWx] file ...
unlink file
DESCRIPTION
The rm utility attempts to remove the non-directory type files specified on the command line. If the permissions of the file do not permit
writing, and the standard input device is a terminal, the user is prompted (on the standard error output) for confirmation.
The options are as follows:
-d Attempt to remove directories as well as other types of files.
-f Attempt to remove the files without prompting for confirmation, regardless of the file's permissions. If the file does not exist, do
not display a diagnostic message or modify the exit status to reflect an error. The -f option overrides any previous -i options.
-i Request confirmation before attempting to remove each file, regardless of the file's permissions, or whether or not the standard
input device is a terminal. The -i option overrides any previous -f options.
-I Request confirmation once if more than three files are being removed or if a directory is being recursively removed. This is a far
less intrusive option than -i yet provides almost the same level of protection against mistakes.
-P Overwrite regular files before deleting them. Files are overwritten three times, first with the byte pattern 0xff, then 0x00, and
then 0xff again, before they are deleted. Files with multiple links will not be overwritten nor deleted and a warning will be
issued. If the -f option is specified, files with multiple links will also be overwritten and deleted. No warning will be issued.
Specifying this flag for a read only file will cause rm to generate an error message and exit. The file will not be removed or over-
written.
N.B.: The -P flag is not considered a security feature (see BUGS).
-R Attempt to remove the file hierarchy rooted in each file argument. The -R option implies the -d option. If the -i option is speci-
fied, the user is prompted for confirmation before each directory's contents are processed (as well as before the attempt is made to
remove the directory). If the user does not respond affirmatively, the file hierarchy rooted in that directory is skipped.
-r Equivalent to -R.
-v Be verbose when deleting files, showing them as they are removed.
-W Attempt to undelete the named files. Currently, this option can only be used to recover files covered by whiteouts in a union file
system (see undelete(2)).
-x When removing a hierarchy, do not cross mount points.
The rm utility removes symbolic links, not the files referenced by the links.
It is an error to attempt to remove the files /, . or ...
When the utility is called as unlink, only one argument, which must not be a directory, may be supplied. No options may be supplied in this
simple mode of operation, which performs an unlink(2) operation on the passed argument.
EXIT STATUS
The rm utility exits 0 if all of the named files or file hierarchies were removed, or if the -f option was specified and all of the existing
files or file hierarchies were removed. If an error occurs, rm exits with a value >0.
NOTES
The rm command uses getopt(3) to parse its arguments, which allows it to accept the '--' option which will cause it to stop processing flag
options at that point. This will allow the removal of file names that begin with a dash ('-'). For example:
rm -- -filename
The same behavior can be obtained by using an absolute or relative path reference. For example:
rm /home/user/-filename
rm ./-filename
When -P is specified with -f the file will be overwritten and removed even if it has hard links.
EXAMPLES
Recursively remove all files contained within the foobar directory hierarchy:
$ rm -rf foobar
Either of these commands will remove the file -f:
$ rm -- -f
$ rm ./-f
COMPATIBILITY
The rm utility differs from historical implementations in that the -f option only masks attempts to remove non-existent files instead of
masking a large variety of errors. The -v option is non-standard and its use in scripts is not recommended.
Also, historical BSD implementations prompted on the standard output, not the standard error output.
SEE ALSO chflags(1), rmdir(1), undelete(2), unlink(2), fts(3), getopt(3), symlink(7)STANDARDS
The rm command conforms to IEEE Std 1003.2 (``POSIX.2'').
The simplified unlink command conforms to Version 2 of the Single UNIX Specification (``SUSv2'').
HISTORY
A rm command appeared in Version 1 AT&T UNIX.
BUGS
The -P option assumes that the underlying storage overwrites file blocks when data is written to an existing offset. Several factors includ-
ing the file system and its backing store could defeat this assumption. This includes, but is not limited to file systems that use a Copy-
On-Write strategy (e.g. ZFS or UFS when snapshots are being used), Flash media that are using a wear leveling algorithm, or when the backing
datastore does journaling, etc. In addition, only regular files are overwritten, other types of files are not.
BSD April 25, 2013 BSD