Using plink with sudo access

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Inheriting SUDO access?

I had a question on users inheriting SUDO capabilities of another account. Let's say that there are three users A, B, and C. A has access to Sudo into B. B has access to Sudo into C. Does this give A access to sudo into B and then sudo into C. A -> B B -> C A -> B -> C ? Another example. My...

2. Red Hat

Sudo access issue

Hi, I have given access to user mwadmin in shudders file as : mwadmin ALL:NOPASSWD:/www/* /usr/* /opt/* However, not able to execute below command: sudo mkdir -p /usr/test password for mwadmin: Sorry, user mwadmin is not allowed to execute '/bin/mkdir -p /usr/test' as root. ...

3. Solaris

Sudo access in Solaris

Install the sudo pkg SFWsudo.tar bash#tar -xvf SFWsudo.tar bash#pkgadd -d . SFWsudo path may be /opt/sfw/bin Make entry the user name in sudoer file path of the sudoer file /opt/sfw/etc/sudoers check with the below command as a user (not as a root user) user1$...

4. UNIX for Advanced & Expert Users

Help needed in sudo access

I want to give root access to a user called denielr on server - tsprd01, but do not want to share root password. I have sudoers configured already. He should have all access equal to root. I made this entry in /etc/sudoers, but it is not working denielr tsprd01 =(root) NOPASSWD: ALL I tried to...

5. Ubuntu

Restrict SUDO Access

Linux ubuntu 3.0.0-12-generic #20-Ubuntu SMP Fri Oct 7 14:56:25 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux Hi Folks, Please help me. I am bit struck here. Here is the OS info. Linux ubuntu 3.0.0-12-generic #20-Ubuntu SMP Fri Oct 7 14:56:25 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux I have a...

6. UNIX for Dummies Questions & Answers

sudo/root access

I'm actually working with a Ubuntu-System here and have a question about executing a command with 'sudo'. I tried and got a error message like "not allowed". After this I logged in with 'sudo -s' and typed the command without 'sudo'. This worked well. Can please somebody explain me this...

7. Shell Programming and Scripting

ONLY SU Sudo access

Hello All, I want to create a script that will do ONLY su to any user on the server with hpadmin login using sudo. Can anyone let me know how can it do it. Regards Ankit

8. AIX

sudo user access

I have installed sudo on AIX 6100-04 and want to know how do I set it up for a user to be able to run only some commands? I want to give the user the rights to only cd to certain directories and run the ls command to name a few? Are there any issues with running sudo when the user is forced to...

9. Linux

sudo access verification

Hi All, I got lots of request with sudo, a manager request, verbal command, do this and do that. The problem with this kind of request is when I added that script and that. It will not be perfect, it's because I can't verify the userid sudo access, I can't reset their password as well, I...

10. Solaris

secure access using sudo

I just need to know what should be done on a login user so that no one can access it except through sudo i.e. telnet server login: user NO ACCESS telnet server login: mylogin sudo - user <any command> ACCESS GRANTED thanks

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)

Shell Programming and Scripting