Run a shell command on klone and return its stdout.

cmd is run by the remote shell, so pipes, redirects, and && chains work. For everything beyond simple commands — SLURM job submission, job inspection, log tailing, disk queries, etc. — invoke the appropriate shell tool here. See klone://docs/commands for a list of klone-specific utilities (hyakalloc, hyakstorage, squeue, sacct, sbatch, scontrol, scancel, sinfo, apptainer, ...).

For long-running work (compilation, training), submit a SLURM job via sbatch rather than running it directly.

timeout (seconds) controls how long to wait for the remote command. Default 60. Bump for expensive queries like du -sh /gscratch/....

First-time orientation: if you haven't already, read klone://docs/quickstart — it covers the storage/quota layout, the SSD-staging performance pattern, and indexes all other klone://help/* topics (SLURM, GPUs, containers, MATLAB, R, Jupyter, etc). Reading it once saves repeated trial-and-error.

Create or overwrite a file on klone with the given content.

Content is piped via SSH stdin, so size is unlimited (no ARG_MAX boundary) and shell metacharacters in content are not interpreted.

Use this for writing SLURM scripts, config files, small data files — anything where you want exact bytes written verbatim. For very large data files, use rsync or scp from the calling machine instead.

If you're writing a SLURM script, read klone://help/jobs first for the partition catalog and klone://help/checkpoint if you're planning to use ckpt-all (preemption handling is required).