I am using Spring Shell to run some long running command. Is there anyway to interrupt a running command in Spring Shell using Control+C command without exiting the shell.
Unfortunately, this is not supported. Support for CTRL-C is in PR, but not for killing an external command (rather for cancelling text entered at the prompt so far).
Related
Typically in most terminals I've worked with (for instance, powershell or OSX's built-in "terminal") if you start typing your next command while the previous is still running, the terminal will receive your keyboard inputs and insert them anyway.
With the windows ubuntu terminal, all my keystrokes while the current command is running are lost.
This seems to only happen when I run a windows exe through the ubuntu terminal.
For example, this suppresses all my keyboard input: "ping.exe windows.com", while using ubuntu's ping does not: "ping windows.com"
Is there a fix to make it so that my keyboard input is not suppressed when running windows tools in the ubuntu terminal? I find this valuable since I often being typing the next command while the previous is still running.
I am trying to start a Powershell script in remote windows 2012 server with Bitvise. The script has the command to start a spring boot application.
start "MyApp" java -jar myapp.jar
Bamboo Job triggers the script using SSH task and based on the logs, the jar is executed and the application is up. However, as soon as the bamboo job completes, the application goes down. Is there a way to keep this application running even after the job completes?
Note: I tried running a bat file instead of PowerShell and in that case the bamboo job simply never completes and if the job is manually stopped the application goes down in the server.
Regards,
Jai
I use remote shh interpreter in PyCharm regularly, using the configured deployment. I often run remote programs from PyCharm GUI (using F5 key), that takes hours to complete (e.g. training a deep net). This unfortunately means that any network outage causes running script to exit and I have to run the script over again. Is there a way to detach the running script so it keeps running? In the sense similar to what screen or nohup is doing? I know I can run it in screen manually via ssh, but it is a bit inconvenient.
Ok. I found out that this feature is not implemented yet. There is however a suggested workaround
I have ran a command here at work that my coworkers told me to run:
They told me that this command was supposed to run in background, once it takes hours and hours to run ... but after running the command, the prompt stucked in this "Sending output to nohup.out" and it's like this for more than 1 hour.
Question: can I shutdown my computer? Sorry about my ignorance, I do not understand anything about it. By the way, this is a windows command prompt, connected to an AIX server using Telnet.
You are at a command prompt, the output of the previous command wrote on top of it. Yes, you can disconnect from the remote system and the command will continue (it will ignore the HUP signal sent on disconnect). Yes, you can shut down your Windows client.
I'm having big problems connecting a windows slave to a working jenkins CI setup.
How do you connect using command on the master? I've tried the following command:
bash -c 'ssh user#hostname cmd /c "java -jar C:/jenkins/slave.jar -text 2>C:/jenkins/slave_error.txt"'
This successfully connects, BUT all commands talk to whatever shell has been spawned by the ssh server. This should be a new cmd shell (is this akin to a new bash shell?) as if the local user ran cmd.exe. freeSSHd claims to do this, but I can't get it to work. Instead the sshd server shipped with cygwin spawns a cmd shell, which spawns an emulated bash shell, which spawns an emulated cmd shell, which calls "java -jar slave.jar".
It seems that through all those layers of emulation, a) some system environment variables are lost, and b) windows commands run slower. Does anyone else connect to windows with ssh, and if so, how? I haven't found any information on running windows builds remotely with purely command line calls.
The build works perfectly on windows 7 through Java Web Start.
Why does the Java Web Start option, which creates a service on the slave, disconnect after ~20 hours? This option works great, but we cannot tolerate this sort of unreliability. Windows 7 has no such issue.
Why is connection through DCOM seemingly impossible to set up?
In case anyone else is trying to use "Launch slave agents on Unix machines via SSH", it cannot work at all for a windows slave. Use "Launch slave via execution of command on the Master".
Any advice is appreciated.