I guess you mean the file names?
Then consider sort and unique to sort out duplicates.
Show the duplicate file names:
Show the non-duplicates:
Show each file name once
I've searched about a bit and more than likely, I'm not entering the correct search phrase, but my question is as follows:
When a user does an 'ls' (and whatever various flags needed) and in the results, we see duplicate or backup files from editing. IE:
file1.txt
file1.txt~
Is there a... (3 Replies)
Hi!
I want to find duplicate files (criteria: file size) in my download folder.
I try it like this:
find /Users/frodo/Downloads \! -type d -exec du {} \; | sort > /Users/frodo/Desktop/duplicates_1.txt;
cut -f 1 /Users/frodo/Desktop/duplicates_1.txt | uniq -d | grep -hif -... (9 Replies)
Hi !
I wonder if anyone can help on this : I have a directory: /xyz that has the following files:
chsLog.107.20130603.gz
chsLog.115.20130603
chsLog.111.20130603.gz
chsLog.107.20130603
chsLog.115.20130603.gz
As you ca see there are two files that are the same but only with a minor... (10 Replies)
Hi champs,
I have one of the requirement, where I need to compare two files line by line and ignore duplicates. Note, I hav files in sorted order.
I have tried using the comm command, but its not working for my scenario.
Input file1
srv1..development..employee..empname,empid,empdesg... (1 Reply)
I am so frustrated!!!
I want a nice command that clears away duplicate files:
find . -type f -regex '.*{1,3}\..*' | xargs -I## rm -v '##'
should work in my opinion. But it finds nothing even though I have files that have the file name:
Scooby-Doo-1.txt
Himalaya-2.jpg
Camping... (8 Replies)
I have tried the following code and with that i couldnt achieve what i want.
#!/usr/bin/bash
find ./ -type f \( -iname "*.xml" \) | sort -n > fileList
sed -i '/\.\/fileList/d' fileList
NAMEOFTHISFILE=$(echo $0|sed -e 's/\/()$*.^|/\\&/g')
sed -i "/$NAMEOFTHISFILE/d"... (2 Replies)
Discussion started by: gold2k8
2 Replies
LEARN ABOUT DEBIAN
backintime
backintime(1) USER COMMANDS backintime(1)NAME
backintime - a simple backup tool for Linux.
This is command line tool. The graphical tools are: backintime-gnome and backintime-kde4.
SYNOPSIS
backintime [ --backup | --backup-job | --snapshots-path | --snapshots-list | --snapshots-list-path | --last-snapshot | --last-snapshot-path
| --help | --version | --license ]
DESCRIPTION
Back In Time is a simple backup tool for Linux. The backup is done by taking snapshots of a specified set of folders.
All you have to do is configure: where to save snapshots, what folders to backup. You can also specify a backup schedule: disabled, every
5 minutes, every 10 minutes, every hour, every day, every week, every month. To configure it use one of the graphical interfaces available
(backintime-gnome or backintime-kde4).
It acts as a 'user mode' backup tool. This means that you can backup/restore only folders you have write access to (actually you can backup
read-only folders, but you can't restore them).
If you want to run it as root you need to use 'su'.
A new snapshot is created only if something changed since the last snapshot (if any).
A snapshot contains all the files from the selected folders (except for exclude patterns). In order to reduce disk space it use hard-links
(if possible) between snapshots for unchanged files. This way a file of 10Mb, unchanged for 10 snapshots, will use only 10Mb on the disk.
When you restore a file 'A', if it already exists on the file system it will be renamed to 'A.backup.currentdate'.
For automatic backup it use 'cron' so there is no need for a daemon, but 'cron' must be running.
user-callback
During backup process the application can call a user callback at different steps. This callback is "$XDG_CONFIG_HOME/backintime/user-
callback" (by default $XDG_CONFIG_HOME is ~/.config).
The first argument is the progile id (1=Main Profile, ...).
The second argument is the progile name.
The third argument is the reason:
1 Backup process begins.
2 Backup process ends.
3 A new snapshot was taken. The extra arguments are snapshot ID and snapshot path.
4 There was an error. The second argument is the error code.
Error codes:
1 The application is not configured.
2 A "take snapshot" process is already running.
3 Can't find snapshots folder (is it on a removable drive ?).
4 A snapshot for "now" already exist.
OPTIONS -b, --backup
take a snapshot now (if needed)
--backup-job
take a snapshot (if needed) depending on schedule rules (used for cron jobs)
--snapshots-path
display path where is saves the snapshots (if configured)
--snapshots-list
display the list of snapshot IDs (if any)
--snapshots-list-path
display the paths to snapshots (if any)
--last-snapshot
display last snapshot ID (if any)
--last-snapshot-path
display the path to the last snapshot (if any)
-h, --help
display a short help
-v, --version
show version
--license
show license
SEE ALSO
backintime-gnome, backintime-kde4.
Back In Time also has a website: http://backintime.le-web.org
AUTHOR
This manual page was written by BIT Team (<bit-team@lists.launchpad.net>).
version 1.0.10 Mars 2009 backintime(1)