![]() |
![]() |
#1 |
1D9E16 Posts |
![]()
I've searched the entire forum and google for running mprime over SSH and got no hits, so I guess I'll go ahead and ask.
I want to test an entire rack of servers with mprime by using the command: ssh <ip address> /home/mprime/mprime -t and it works, but only for the first node and then it gets hung up on the response message. I've also tried having the script from my execution unit run another script that ran mprime on the other nodes but it had the same issues. (For clarification) script 1: ssh <ipaddress> /home/mprime/start-mprime.sh start-mprime.sh (loaded on the outside nodes) /home/mprime/mprime -t Any suggestions out there? |
![]() |
![]() |
#2 |
A Sunny Moo
Aug 2007
USA (GMT-5)
3·2,083 Posts |
![]()
I think what you need is to run mprime with "nohup" so it doesn't get terminated when you close the SSH connection. If you run it like this:
ssh <ip address> /home/mprime/mprime -t mprime will be started in the background on the client represented by <ip address>, and will stay running when you disconnect from SSH. mprime's console output will be redirected to the file stdout.log (or something like that, I'm not completely sure) in whatever working directory your SSH connection first puts you in. |
![]() |
![]() |
![]() |
#3 | |
Sep 2009
242610 Posts |
![]() Quote:
ssh <ip address> 'nohup /home/mprime/mprime -t >mprime.out 2>&1 & ' The single quotes round the parms passed to ssh ensure everything inside it is passed to the destination to run there. Without the redirection to mprime.out nohup would write to nohup.out, which is OK unless some other task also tries to write to it. Your SSH connection will usually put you into your home dir. Try "ssh <ip address> pwd" to check. You could also try running the whole ssh command under nohup on the source system. Chris K |
|
![]() |
![]() |
![]() |
#4 | |
A Sunny Moo
Aug 2007
USA (GMT-5)
11000011010012 Posts |
![]() Quote:
![]() ![]() Last fiddled with by mdettweiler on 2011-06-30 at 00:45 |
|
![]() |
![]() |
![]() |
#5 |
1C3216 Posts |
![]()
I actually found a way to use a daemon script over SSH to start mprime. The only problem now is that the few servers running Ubuntu are giving me fits.
I've tried using the daemon script from the Ubuntu forums and it gives me the same issue that I had before (the script hangs after starting the mprime test). Unless I can find a way to get the daemon capabilities from Fedora to Ubuntu I'll end up messing with the script until it finally works. Thanks for the suggestions. |
![]() |
![]() |
Thread Tools | |
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
mprime | Unregistered | Information & Answers | 3 | 2011-08-05 09:17 |
./mprime -B in 257 | Lazlow | PrimeNet | 3 | 2008-10-29 20:40 |
64 bit mprime? | aaronl | Linux | 1 | 2005-11-10 16:50 |
ECM using gmp-ecm and mprime on a P4 | geoff | Factoring | 60 | 2004-12-02 07:16 |
Problem with mprime (Fixed with mprime -d) | antiroach | Software | 2 | 2004-07-19 04:07 |