Sponsored Content
Top Forums Shell Programming and Scripting How to move the files older than x days with similar directory structure? Post 302917747 by prvnrk on Thursday 18th of September 2014 11:40:58 AM
Old 09-18-2014
How to move the files older than x days with similar directory structure?

Hello,

I need to move all the files inside /XYZ (has multi-depth sub directories) that are older than 14 days to/ABC directory but with retaining the SAME directory structure.

for example:
/XYZ/1/2/3/A/b.txt should be moved as /ABC/1/2/3/A/b.txt

I know about find /XYZ -type f -mtime +14 -exec mv {} /ABC \; but it would NOT retain the directory structure.

I thought of backing up whole /XYZ to /ABC and then delete recent 14 days' files from /ABC and all files older than 14 days from /XYZ but I find it very inefficient.

Appreciate any help. Thanks!
 

9 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

MV files from one directory structure(multiple level) to other directory structure

Hi, I am trying to write a script that will move all the files from source directory structure(multiple levels might exist) to destination directory structure. If a sub folder is source doesnot exist in destination then I have to skip and goto next level. I also need to delete the files in... (4 Replies)
Discussion started by: srmadab
4 Replies

2. Shell Programming and Scripting

List directory 7 days older

Say folder archive/ contains many folder each created on a day. this folder may contain files. i want to write a script to delete all the folder inside archive/ which are 7 days older. i used the below script for the reason. find archive -mtime +7 -type d -exec rm -r {} \; pls suggest me if... (3 Replies)
Discussion started by: krishnarao
3 Replies

3. Shell Programming and Scripting

Move the latest or older File from one directory to another Directory

I Need help for one requirement, I want to move the latest/Older file in the folder to another file. File have the datetimestamp in postfix. Example: Source Directory : \a destination Directory : \a\b File1 : xy_MMDDYYYYHHMM.txt (xy_032120101456.txt) File2: xy_MMDDYYYYHHMM.txt... (1 Reply)
Discussion started by: pp_ayyanar
1 Replies

4. UNIX for Dummies Questions & Answers

move files older than 2 days to another folder

Hi I am facing problem in using this command, mv `find /export/june/PURGEDATA*.txt -mtime +2 -exec ls {} \;` june/archive/ mv: Insufficient arguments (1) Usage: mv f1 f2 mv f1 ... fn d1 mv d1 d2 Thank you in advance (2 Replies)
Discussion started by: vishwakar
2 Replies

5. Shell Programming and Scripting

Delete files older than 10 Days in a directory

Hi All I want to remove the files with name like data*.csv from the directory older than 10 days. If there is no files exists to remove older than 10 days, It should not do anything. Thanks Jo (9 Replies)
Discussion started by: rajeshjohney
9 Replies

6. AIX

Want to delete directory, subdirectories and all files which are older than 7 days

how do i remove sub directories of a directory and all files which are older than 7 days by a single command in AIX. pls help me. I am using command as #find /gpfs1/home/vinod/hpc/ -depth -type d -mtime +7 -exec rm -rf {} \; so i want to delete all sub directories and all files from the... (1 Reply)
Discussion started by: vinodkmpal
1 Replies

7. UNIX for Advanced & Expert Users

HPUX move files older than 30 days

Hello, I have a script which finds files in a directory that are older than 30 days and moves them to the specified directory. The problem is I don't know why it works the way it does? Code: find . -name '*.sql' ! -mtime -30 -exec mv '{}' /dataload/archivelogs \; I was under the... (4 Replies)
Discussion started by: pure_jax
4 Replies

8. Shell Programming and Scripting

How can i move folders and its content if folder is older than 1,5 days and keep subdirs in bash?

Hello all, do you know any way i can i move folders and its content if folder is older than 1,5 days in bash? I tried: find /home/xyz/DATA/* -type d -ctime +1.5 -exec mv "{}" /home/xyz/move_data_here/ \;All i got was that Files from DATA /home/xyz/DATA/* ended messed up in... (1 Reply)
Discussion started by: ZerO13
1 Replies

9. Linux

Finding files older than x days within directory with spaces

Hi, I am trying to run a command that finds all files over x amount of days, issue is one of the directories has spaces within it. find /files/target directory/*/* -type f -mtime +60 When running the above the usual error message is thrown back + find '/files/target\' 'directory/*/*' -type... (1 Reply)
Discussion started by: Ads89
1 Replies
ct_telnet(3erl) 					     Erlang Module Definition						   ct_telnet(3erl)

NAME
ct_telnet - Common Test specific layer on top of telnet client ct_telnet_client.erl. DESCRIPTION
Common Test specific layer on top of telnet client ct_telnet_client.erl Use this module to set up telnet connections, send commands and perform string matching on the result. See the unix_telnet manual page for information about how to use ct_telnet, and configure connections, specifically for unix hosts. The following default values are defined in ct_telnet: Connection timeout = 10 sec (time to wait for connection) Command timeout = 10 sec (time to wait for a command to return) Max no of reconnection attempts = 3 Reconnection interval = 5 sek (time to wait in between reconnection attempts) Keep alive = true (will send NOP to the server every 10 sec if connection is idle) These parameters can be altered by the user with the following configuration term: {telnet_settings, [{connect_timeout,Millisec}, {command_timeout,Millisec}, {reconnection_attempts,N}, {reconnection_interval,Millisec}, {keep_alive,Bool}]}. Millisec = integer(), N = integer() Enter the telnet_settings term in a configuration file included in the test and ct_telnet will retrieve the information automatically. Note that keep_alive may be specified per connection if required. See unix_telnet for details. DATA TYPES
connection() = handle() | {target_name() (see module ct), connection_type()} | target_name() (see module ct) : connection_type() = telnet | ts1 | ts2 : handle() = handle() (see module ct_gen_conn) : Handle for a specific telnet connection. prompt_regexp() = string() : A regular expression which matches all possible prompts for a specific type of target. The regexp must not have any groups i.e. when matching, re:run/3 shall return a list with one single element. EXPORTS
close(Connection) -> ok | {error, Reason} Types Connection = connection() (see module ct_telnet) Close the telnet connection and stop the process managing it. A connection may be associated with a target name and/or a handle. If Connection has no associated target name, it may only be closed with the handle value (see the open/4 function). cmd(Connection, Cmd) -> {ok, Data} | {error, Reason} Equivalent to cmd(Connection, Cmd, DefaultTimeout) . cmd(Connection, Cmd, Timeout) -> term() cmdf(Connection, CmdFormat, Args) -> {ok, Data} | {error, Reason} Equivalent to cmdf(Connection, CmdFormat, Args, DefaultTimeout) . cmdf(Connection, CmdFormat, Args, Timeout) -> term() cont_log(Str, Args) -> term() end_log() -> term() expect(Connection, Patterns) -> term() Equivalent to expect(Connections, Patterns, []) . expect(Connection, Patterns, Opts) -> {ok, Match} | {ok, MatchList, HaltReason} | {error, Reason} Types Connection = connection() (see module ct_telnet) Patterns = Pattern | [Pattern] Pattern = string() | {Tag, string()} | prompt | {prompt, Prompt} Prompt = string() Tag = term() Opts = [Opt] Opt = {timeout, Timeout} | repeat | {repeat, N} | sequence | {halt, HaltPatterns} | ignore_prompt Timeout = integer() N = integer() HaltPatterns = Patterns MatchList = [Match] Match = RxMatch | {Tag, RxMatch} | {prompt, Prompt} RxMatch = [string()] HaltReason = done | Match Reason = timeout | {prompt, Prompt} Get data from telnet and wait for the expected pattern. Pattern can be a POSIX regular expression. If more than one pattern is given, the function returns when the first match is found. RxMatch is a list of matched strings. It looks like this: [FullMatch, SubMatch1, SubMatch2, ...] where FullMatch is the string matched by the whole regular expression and SubMatchN is the string that matched subexpression no N . Subexpressions are denoted with '(' ')' in the regular expression If a Tag is given, the returned Match will also include the matched Tag . Else, only RxMatch is returned. The function will always return when a prompt is found, unless the ignore_prompt options is used. The timeout option indicates that the function shall return if the telnet client is idle (i.e. if no data is received) for more than Timeout milliseconds. Default timeout is 10 seconds. The repeat option indicates that the pattern(s) shall be matched multiple times. If N is given, the pattern(s) will be matched N times, and the function will return with HaltReason = done . The sequence option indicates that all patterns shall be matched in a sequence. A match will not be concluded untill all patterns are matched. Both repeat and sequence can be interrupted by one or more HaltPatterns . When sequence or repeat is used, there will always be a MatchList returned, i.e. a list of Match instead of only one Match . There will also be a HaltReason returned. Examples: expect(Connection,[{abc,"ABC"},{xyz,"XYZ"}], [sequence,{halt,[{nnn,"NNN"}]}]). will try to match "ABC" first and then "XYZ", but if "NNN" appears the function will return {error,{nnn,["NNN"]}} . If both "ABC" and "XYZ" are matched, the function will return {ok,[AbcMatch,XyzMatch]} . expect(Connection,[{abc,"ABC"},{xyz,"XYZ"}], [{repeat,2},{halt,[{nnn,"NNN"}]}]). will try to match "ABC" or "XYZ" twice. If "NNN" appears the function will return with HaltReason = {nnn,["NNN"]} . The repeat and sequence options can be combined in order to match a sequence multiple times. get_data(Connection) -> {ok, Data} | {error, Reason} Types Connection = connection() (see module ct_telnet) Data = [string()] Get all data which has been received by the telnet client since last command was sent. open(Name) -> {ok, Handle} | {error, Reason} Equivalent to open(Name, telnet) . open(Name, ConnType) -> {ok, Handle} | {error, Reason} Types Name = target_name() ConnType = connection_type() (see module ct_telnet) Handle = handle() (see module ct_telnet) Open a telnet connection to the specified target host. open(KeyOrName, ConnType, TargetMod) -> {ok, Handle} | {error, Reason} Equivalent to open(KeyOrName, ConnType, TargetMod, []) . open(KeyOrName, ConnType, TargetMod, Extra) -> {ok, Handle} | {error, Reason} Types KeyOrName = Key | Name Key = atom() Name = target_name() (see module ct) ConnType = connection_type() TargetMod = atom() Extra = term() Handle = handle() Open a telnet connection to the specified target host. The target data must exist in a configuration file. The connection may be associated with either Name and/or the returned Handle . To allocate a name for the target, use ct:require/2 in a test case, or use a require statement in the suite info function ( suite/0 ), or in a test case info function. If you want the connection to be associated with Handle only (in case you need to open multiple connections to a host for example), simply use Key , the configuration variable name, to specify the target. Note that a connection that has no associated target name can only be closed with the handle value. TargetMod is a module which exports the functions connect(Ip,Port,KeepAlive,Extra) and get_prompt_regexp() for the given TargetType (e.g. unix_telnet ). send(Connection, Cmd) -> ok | {error, Reason} Types Connection = connection() (see module ct_telnet) Cmd = string() Send a telnet command and return immediately. The resulting output from the command can be read with get_data/1 or expect/2/3 . sendf(Connection, CmdFormat, Args) -> ok | {error, Reason} Types Connection = connection() (see module ct_telnet) CmdFormat = string() Args = list() Send a telnet command and return immediately (uses a format string and a list of arguments to build the command). SEE ALSO
unix_telnet AUTHORS
<> common_test 1.5.3 ct_telnet(3erl)
All times are GMT -4. The time now is 07:40 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy