07-14-2005
Error when using if [ find '
I am trying to issue the following command in script:
if [ 'find /tmp/tst_file =mtime -1 grep | wc -l' -eq 1 ]; then
and I am getting the following error:
bad number
Any ideas
Rgds
Joe
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
2 AIX servers (AIX 5.3). From local server, I need to manage remote files. But I have some errors with find :
# rsh remoteserver find /directory -name filename
is OK : I can see the remote file
BUT :
# rsh remoteserver find /directory -name filename -exec ls -l {} \;
fails : I have :
find :... (5 Replies)
Discussion started by: annemar
5 Replies
2. AIX
Hi,
While trying to configure Apache Web Server on P630 Server i am getting the below message
"Creating Makefile in src
+ configured for AIX 5.2 platform
Error: could not find any of these C compilers
anywhere in your PATH: gcc cc acc c89
Configure terminated"
when i did a "lslpp -l... (2 Replies)
Discussion started by: cherryven
2 Replies
3. Shell Programming and Scripting
I have a directory that our applications are continuely generate new file to it , some files hv a word "error" in content , I would like to find out which file hv this word and send me notify mail to inform me which file hv this word , currently , I have a stupid script to grep the word , the... (1 Reply)
Discussion started by: ust
1 Replies
4. Shell Programming and Scripting
Hi Guru's
here is part of my shell script where the error is coming.
function daemon_start
{
daemon=""
clear
:<<COMMENT
Meenakshi 25-Jun Code Cleanup IA - code comented - Start
echo "
`date`
... (1 Reply)
Discussion started by: namishtiwari
1 Replies
5. UNIX for Advanced & Expert Users
for FNAME in `find . -type f -exec grep -il unixs317 {} \;`; do C=`grep -c unixs317 ${FNAME}`; echo "${C}:${FNAME}" >> output.txt; done
When I run this command and a directory is empty it is returning an error and just does nothing more.
How can I continue with my search even when it find... (3 Replies)
Discussion started by: TimHortons
3 Replies
6. UNIX for Dummies Questions & Answers
Have a random question:
In simple terms I have a find command on a dir:
/path/user/data/
/path/user is a link to:
/tmp/storage/
The find command outputs the files it finds as:
/path/user/data/file
What I need is:
/tmp/storage/file
Is there a way to "resolve" the Unix... (5 Replies)
Discussion started by: Cranie
5 Replies
7. Programming
Please see the error below
Program:
#include<stdio.h>
#include<sys/types.h>
#include<sys/mman.h>
#include<stdlib.h>
#include<fcntl.h>
#include<sys/stat.h>
#include<unistd.h>
#include<signal.h>
#include<string.h>
main(int argc, char *argv)
{
int fd,changes,i,random_spot,kids;... (1 Reply)
Discussion started by: gokult
1 Replies
8. Shell Programming and Scripting
why is this giving me errors?
i type this in: find / -name "something.txt" 2>/dev/null
i get the following error messages:
find: bad option 2
find: path-list predicate-list
:confused: (5 Replies)
Discussion started by: magiling
5 Replies
9. Shell Programming and Scripting
Hi,
We have a shell script which looks into a directroy for any folder older than 30 days and removes them. The command being used is
find $ARCHIVE_DIR -type d -mtime +$PURGE_HIST_DAYS -exec rm -rf {} \;
It removes some folders but then throw below errors for others:
find:... (2 Replies)
Discussion started by: DejaVu
2 Replies
10. Shell Programming and Scripting
Today is my first day in shell scripting.
I am not able to find error.
Need Help!
Error is :-
syntax error near unexpected token `then'
test.sh: line 50: ` if; then
echo "Enter Path o(if empty file will be unzipped to /var/www/):" read path
echo... (3 Replies)
Discussion started by: sunny2802
3 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)