On Sat, 2019-06-29 at 16:27 +, Renfro, Michael wrote:
> Is this output file being written to a central file server that can be
> accessed from your submit host? If so, start another ssh session from your
> local computer to the submit host.
>
> Is the output file being written to a location
Is this output file being written to a central file server that can be accessed
from your submit host? If so, start another ssh session from your local
computer to the submit host.
Is the output file being written to a location only accessible from the compute
node running your job? You might b
On Sat, 2019-06-29 at 07:57 -0700, Brian Andrus wrote:
> I believe you are referring to an interactive terminal window.
>
> You can do that with srun --pty bash
>
> Windows themselves are not handled by slurm at all. To have multiple
> windows is a function of your workstation. You would need mu
On Sat, 2019-06-29 at 16:48 +0200, Valerio Bellizzomi wrote:
> On Sat, 2019-06-29 at 07:36 -0700, Brian Andrus wrote:
> > A little more details of what you are trying to do would help.
> >
> > multiple srun statements with --pty options will spawn multiple
> > terminals. Just like running bash mu
I believe you are referring to an interactive terminal window.
You can do that with srun --pty bash
Windows themselves are not handled by slurm at all. To have multiple
windows is a function of your workstation. You would need multiple
connections to the cluster (eg: multiple ssh windows with
On Sat, 2019-06-29 at 07:36 -0700, Brian Andrus wrote:
> A little more details of what you are trying to do would help.
>
> multiple srun statements with --pty options will spawn multiple
> terminals. Just like running bash multiple times, if you do it within
> the same terminal it will create a
A little more details of what you are trying to do would help.
multiple srun statements with --pty options will spawn multiple
terminals. Just like running bash multiple times, if you do it within
the same terminal it will create a terminal within a terminal.
So, I would ask: what are you try
How it gets done normally ?
On Fri, 2019-06-28 at 09:39 +0200, Ole Holm Nielsen wrote:
> On 6/28/19 9:18 AM, Valerio Bellizzomi wrote:
> > On Fri, 2019-06-28 at 08:51 +0200, Valerio Bellizzomi wrote:
> >> On Thu, 2019-06-27 at 18:35 +0200, Valerio Bellizzomi wrote:
> >>> The nodes are now communicating however when I run the
