02-24-2005
find and move, part II
Thank you for your reply. Looks like this will work, however, I am getting the following as a result of the sed command:
+ echo /home/sasadm/setinit.txt
j=ome/sasadm/setinit.txt
I need the /home to drop and do:
j=/code/sasadm/setinit.txt
TIA
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I am looking for files of a certian type and logging them. After they are logged they need to be moved to a different directory. HOw can i incorporate that in my current script?
CSV_OUTFILE="somefile.csv"
find . -name W\* -exec printf "%s,%s,OK" {} `date '+%Y%m%d%H%M%S'` \; > ${CSV_OUTFILE}
... (9 Replies)
Discussion started by: pimentelgg
9 Replies
2. Shell Programming and Scripting
i have some 1000 files in my dir and i want to find top 100 files and move them to some other location:
below the 2 commands i used, but it is not working
ls -ltr | grep ^- | head -100 | xargs mv destination - _________>not working
ls -ltr | grep ^- | head -100 | xargs mv {}... (3 Replies)
Discussion started by: ali560045
3 Replies
3. UNIX for Advanced & Expert Users
Hello I am new to this board.
I was looking for a one line command to find the oldest 10,000 files in a directory and move them.
I tried such things as:
find . -type f | ls -ltr | head -n 10000 -exec mv {} directory/ \;
find . -type f | ls -ltr | head -n 50 | xargs mv directory/ \;
... (7 Replies)
Discussion started by: natasha80
7 Replies
4. Shell Programming and Scripting
Hello All,
/storage3
/storage4
I have written a shell script to locate files older than 7 days in /storage4 folder and move to /storage3.At the same time it will take output as number of files moved and log in a .txt file.
It will also find files in /storage3 older than 90 days and remove... (4 Replies)
Discussion started by: Siddheshk
4 Replies
5. Shell Programming and Scripting
Hi All,
So I have another question. I'm trying to search for files with a certain extension and then move all of them up one level in the folder hierarchy.
So something like this:
original: /path/to/file/test.txt
after: /path/to/test.txt
I had some great help recently with another... (4 Replies)
Discussion started by: ideal2545
4 Replies
6. Shell Programming and Scripting
Hi all
I wrote a little script that search for a file and moves it, its like this:
#!/bin/ksh
today=`date +"%d_%m_%y"`
if ;
then
mkdir -p /tmp/bigfiles/$today
mv $1 /tmp/bigfiles/$today/
echo "moving big file from /home/appcwec " | mailx -s "bigfile" ffff@yyy.com
else
... (4 Replies)
Discussion started by: fretagi
4 Replies
7. Red Hat
Greetings....
Trying to find and move the 30 days old logs
#!/bin/bash
DATE=`date +%d-%b-%Y`
STATUSLOG="$HPATH$DATE-E3Backup.log"
HPATH="/ABC/Websphere/"
HT=`hostname`
BKUPSTR="/ABC/Websphere/$HT/"
echo "Moving of old logs Started on $HT " >> $STATUSLOG
find... (2 Replies)
Discussion started by: manju98458
2 Replies
8. Debian
Hi
A mismatch occurred on my system (Debian, Sid). I've got 3 disks sda, b, c.
Unfortunately, when I was adding a third disk (sdc) it all finished so that both sdb and sdc now have a boot flag. So, the first thing I would like to find out is which disk the system now boots from: sdb or sdc? In... (0 Replies)
Discussion started by: mladen
0 Replies
9. Shell Programming and Scripting
Hi all,
I am trying to find files newer than a given file and them mv them to a new location.
So I far I have:
find . ! -newer <file_name> -exec ls -l {} \;
and
find . ! -newer <file_name> -exec mv /TEMP_LOCATION {} \;
find is not liking this.
Anyone know how to modify the last... (2 Replies)
Discussion started by: jonnyd
2 Replies
10. Shell Programming and Scripting
I have the below command to delete all .xml files older than 90 days
find . -type f -name '*.xml' -mtime +90 -exec rm {} \;
What will be the command to move all the .xml files older than 90 days to this folder -> "/tmp/my_bk"
My OS: SunOS my-pc 5.10 Generic_150400-17 sun4v sparc... (4 Replies)
Discussion started by: mohtashims
4 Replies
LEARN ABOUT NETBSD
npm-run-script
NPM-RUN-SCRIPT(1) NPM-RUN-SCRIPT(1)
NAME
npm-run-script - Run arbitrary package scripts
SYNOPSIS
npm run-script <command> [--silent] [-- <args>...]
alias: npm run
DESCRIPTION
This runs an arbitrary command from a package's "scripts" object. If no "command" is provided, it will list the available scripts.
run[-script] is used by the test, start, restart, and stop commands, but can be called directly, as well. When the scripts in the package
are printed out, they're separated into lifecycle (test, start, restart) and directly-run scripts.
As of ` https://blog.npmjs.org/post/98131109725/npm-2-0-0, you can use custom arguments when executing scripts. The special option -- is
used by getopt https://goo.gl/KxMmtG to delimit the end of the options. npm will pass all the arguments after the -- directly to your
script:
npm run test -- --grep="pattern"
The arguments will only be passed to the script specified after npm run and not to any pre or post script.
The env script is a special built-in command that can be used to list environment variables that will be available to the script at run-
time. If an "env" command is defined in your package, it will take precedence over the built-in.
In addition to the shell's pre-existing PATH, npm run adds node_modules/.bin to the PATH provided to scripts. Any binaries provided by
locally-installed dependencies can be used without the node_modules/.bin prefix. For example, if there is a devDependency on tap in your
package, you should write:
"scripts": {"test": "tap test/*.js"}
instead of
"scripts": {"test": "node_modules/.bin/tap test/*.js"}
to run your tests.
The actual shell your script is run within is platform dependent. By default, on Unix-like systems it is the /bin/sh command, on Windows it
is the cmd.exe. The actual shell referred to by /bin/sh also depends on the system. As of `
https://github.com/npm/npm/releases/tag/v5.1.0 you can customize the shell with the script-shell configuration.
Scripts are run from the root of the module, regardless of what your current working directory is when you call npm run. If you want your
script to use different behavior based on what subdirectory you're in, you can use the INIT_CWD environment variable, which holds the full
path you were in when you ran npm run.
npm run sets the NODE environment variable to the node executable with which npm is executed. Also, if the --scripts-prepend-node-path is
passed, the directory within which node resides is added to the PATH. If --scripts-prepend-node-path=auto is passed (which has been the
default in npm v3), this is only performed when that node executable is not found in the PATH.
If you try to run a script without having a node_modules directory and it fails, you will be given a warning to run npm install, just in
case you've forgotten.
You can use the --silent flag to prevent showing npm ERR! output on error.
You can use the --if-present flag to avoid exiting with a non-zero exit code when the script is undefined. This lets you run potentially
undefined scripts without breaking the execution chain.
SEE ALSO
o npm help 7 scripts
o npm help test
o npm help start
o npm help restart
o npm help stop
o npm help 7 config
January 2019 NPM-RUN-SCRIPT(1)