#When does bash shell for windows 10 come out keygen
However, I have seen rare cases in which a program doesn't work properly when called via sudo/gksudo, but does work properly when called via su/gksu - in such cases, a given user should try to use sudo -i first, and if that does not work, one might have to resort to sudo su - root -c or similar, as a workaround of sorts to deal with a "misbehaving" program. The sudo su launches a second shell, and the command containing the & df is waiting to be executed in the non-root shell, just after the sudo su shell exits successfully.Įdit: please note that I don't normally use or advocate the use of sudo su - root -c type of constructions. This is because with sudo su & df, you are basically executing sudo su first and then df.Īlso make sure, your jenkins user can be sudo without password. If you are trying to run the df command as root, you should instead do sudo df. Then ran sh -c "sudo su & df" with no luck. I even did this manually and from the Jenkins machine logged into the other server (servername). The loging part works fine, then it runs the sudo su command and becomes root but it never runs the second command (i.e. Ssh -i /creds/jenkins jenkins# "sh -c 'sudo su & df'" “sudo su & somecommand” doesn't run somecommand I have created a Jenkins job today, what it does is the Jenkins user should log into another server and run two commands seperated by &: The second one works as intended because you background the command that was passed to su so it immediately returns back to the su, so then the backgrounded su can return. You have three processes because the su doesn't exit while your python continues to run. I'm assuming since you pass start to your script it may be running as a daemon process that doesn't immediately return. I don't know what is in your python script, but if you have it running in a loop, that means the su that you put in the background will NOT return until the command you passed returns. If you wish to see just the python process running, then all you need to do is make sure the & control operator is within the quoted command passed to su: You then run ps, and observe the bash and python processes still running The su process has likely finished any cleanup by this point and exits (almost instantaneously to human observation)
Su starts a bash process and puts it in the background In your second scenario, the following happens: It would be possible for su to fork and simply call the execve() system call for a given program path and arguments, but a lot of shell functionality would lost if that were the case - or you'd have to explicitly call su root -c "/bin/bash -c "
including pipes, redirections, shell-builtins, etc). However, I suspect the reason for this is to allow you to pass complex commands to su (e.g. The simple answer is that this bash shell process is started simply because the documentation says it will be. Specify a command that will be invoked by the shell using its -c. In your first scenario, I assume it is clear why the su and python processes exist, and you are unclear why the bash process exists. Is there anyway I can bring the processes running to one? Also how do I change the process name so that it looks something like as follows: I am not sure where /bin/bash -c python myservice.py start process is created. I was under the impression appending & for the first su command will kill the process once the command is run. Su root -c "/bin/bash -c \"$COMMAND"\" & " &ĥ121 /bin/bash -c python myservice.py start I was wondering why there are three processes that are created? Shell script running commands creates more than one processes - bash I have the following bash script:Ĥ311 su root -c python myservice.py startĤ421 /bin/bash -c python myservice.py start
0 kommentar(er)
