08-04-2009
You can get back the data with a good and recent backup.
And congratulations: you've just learned 3 of the most valuable lessons:
- Think twice before using rm -r, and double so when you are root
- Always quote potential shell characters, except when you explicitly need them substituted
- Always keep a good and current backup, and run test to ensure that you really can restore from it
8 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I have a big file, which vi opens it with message not sufficient space with file system.
I am not adding any data in the file but changing some values within.
To make these changes effective, it asks for forced write (w!), even after doing this,
I see this particular record, change is not... (4 Replies)
Discussion started by: videsh77
4 Replies
2. UNIX for Advanced & Expert Users
dear experts ...help :eek:
I'm running FC2 and i was installing fluxbox but it wouldnt work so i uninstalled it by using rpm -e but because i installed fluxbox-styles it was dependent on fluxbox-0.10 so i used rpm -e --nodeps that was all fine and im not sure that was the cause of the error, but... (1 Reply)
Discussion started by: zeeman
1 Replies
3. UNIX for Dummies Questions & Answers
Hi again!
I finally managed to image the 3 floppies for installing freeBSD but I simply can't boot! I've selected floppy for first boot device and it even starts to readf the boot floppy and the hard drive light is continuously flashing but it doesn't stop even after half an hour and doesn't do a... (4 Replies)
Discussion started by: Mudrack
4 Replies
4. UNIX for Dummies Questions & Answers
i have some problem in linux booting
will u please help me
the problem is
i was using federo core 1 on my system
everything was fine
i made one entry in /etc/fstab file for accessing E
drive of WINDOWS XP
in that i had given file system as VFAT after
rebooting system it
was not... (1 Reply)
Discussion started by: great_indian
1 Replies
5. Linux
Hi...
I have a very wired problem with my redhat4 update 4 server...
Every time i create a file bigger then my physical memory the server kills the process\session that creates the file, and in the "messages" file i see this error:
"Oct 21 15:22:22 optidev kernel: Out of Memory: Killed process... (6 Replies)
Discussion started by: eliraza6
6 Replies
6. Programming
I need to create an executable with these two makefiles(they both have libaries i
need(qt and ruby))
i have extconf.rb
gui.ui
gui_include.h
main.cpp
ScaleIM_client.rb
ui_gui.h
i want to combine them all into one executable
please!... (2 Replies)
Discussion started by: gjgfuj
2 Replies
7. Shell Programming and Scripting
Warning! I'm ridiculously new at all this, so pardon my ignorance...
I have a very simple script which is intended to search a hosts file when given a partial hostanme or ip address. The if the partial hostname/ip given is unique, the script automatically logs the user in to that host. If... (6 Replies)
Discussion started by: itomb
6 Replies
8. Post Here to Contact Site Administrators and Moderators
Every time that i quit from the forum despite i'm 100 % sure that i put the right login (i make a copy and past of the correct data) i obtain always the message that the login is wrong so i must always reset it. :wall:
Could be a bug?
I use a 64 bit linux system. (4 Replies)
Discussion started by: alexscript
4 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)