I am a UNIX novice and was trying to write a bash script that would read two parameters, $1 would be the archive file path where the archiving path is passed, so the archiving script will write to this file path. The second parameter will be the directory path to the library which will contain the files to be archived. For this exercise I am using James Goseling's archiving script:
I know that I will have to call this script recursively if I am to use it as a function and pass on to it the above mentioned parameters, but I don't know how to do it recursively. Could anyone please give me a hint?
Thank you!
I am running into a new problem, namely I am getting : line 32: syntax error: unexpected end of file
I have modified the original code to:
Can anyone please help me understand why I am getting this error.
Thank you
Moderator's Comments:
How to use code tags when posting data and code samples.
Last edited by pernuntium; 03-26-2012 at 03:58 PM..
Reason: Please use code tags for data and code samples, thank you
I am looking for some advice. I have some files on a Unix server, which contain symbolic links. I need to copy these over to a nfts environment, but wish to keep the symbolic links intact. Any ideas? (7 Replies)
Hello Gurus,
I have a requirement where I have to remove users that have not logged into our unix box last 90 days. I want to script this one and remove the users automatically now and then. Has any one ever done this before, if so please give me some sample code. I am not a good unix... (2 Replies)
Hi,
I want to archive below directory
ex: /home/oracle/dd0
sub-directories in dd0
/home/oracle/dd0/backup/backup1
/home/oracle/dd0/backup/backup2
/home/oracle/dd0/dmp
....etc
I want a command(tar) which will let me archive the above directory excluding *.dmp(dump files), *.log(log... (1 Reply)
Im trying to create a script to archive specified directories into a specified tarball backup file. This is what i want the input to look like
ex. save -i '/bin/b*' -i '/bin/ls' -o backup
this is what i have
#!/bin/bash
#save - backup file script
unset myInput
unset myOutput
while... (3 Replies)
Hi all. I am trying to set up archiving of directories, such that I keep every directory made in the past week, but just one directory per week beyond that. Using the find command, I can easily delete everything more than one week old, but can not figure out how to save one.
Each directory... (4 Replies)
Hi,
Suppose I have 2 files of yesterday's. And today I have received 3 files.
Before processing anything I want to archieve the 2 files of yesterday's into a different folder.
How can this be done?
Regards,
Sunitha (1 Reply)
Hi Guys
i am experiencing this problem when trying to archive a file in perl. the files name is created dynamically. (my $date = `date +"%d%m%Y"`;)
`tar czf /opt/memex/backups/Complete$date.tar.gz /opt/memex/backups/Complete$date`;
error message:
tar: Cowardly refusing to create an empty... (4 Replies)
hi,
Am trying to acrhive a bunch of files on some ftp site and somehow managed to come out with the below logic.
I'm getting "syntax error: unexpected end of file" error. Interestingly this below snipeet works fine if run for the first time but the subsequent runs fail!
Anybody has any idea... (3 Replies)
Hi ,
Might be the very basic question and most frequent one also..
wanted to archive the logs/files older than one month or older than 30 days to some particular location.
File/log format is like below
ABCD_EF_GHIJ_Defaulter_Report_(06-Jun-2014_11-50-20_AM)
Source : /test/ABC... (3 Replies)
Discussion started by: Riverstone
3 Replies
LEARN ABOUT LINUX
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)