Knowledge base

1000 FAQs, 500 tutorials and instructional videos. Here, there are only solutions!

Understanding the Limitations of SSH Scripts

Update 08/31/2026

This guide provides important information regarding launching and running command-line scripts (SSH) on different types of Infomaniak hosting.

 

Running scripts via SSH and managing resources

Unlike scripts executed via a web browser, there is generally no strict time limit (timeout) for commands launched via SSH. Your script can therefore theoretically run for as long as necessary.

 

Execution time and persistence

If your SSH session closes (due to a loss of internet connection or terminal closure), the script in progress will be immediately interrupted.

To avoid this during long tasks, it is recommended to run your scripts in the background or, in the case of a VPS, to use terminal multiplexing tools (such as screen, tmux, or the nohup utility). This allows the process to continue its work even after you disconnect.

 

Resource Limits (RAM and CPU)

Even if the time is not limited, hardware resources are.

The execution of your scripts remains subject to the machine's capabilities and its configuration:

  • Memory (RAM): if a process consumes more memory than the allowed limit (for example, the memory_limit of PHP or the available physical RAM), it will be terminated by the system to preserve server stability.
  • Processor (CPU): Excessive processor usage over a long period may result in throttling or interruption of the process.

 

It is possible to adjust these resource limits on dedicated environments (such as Cloud Server). However, on shared hosting, these limits are fixed and cannot be modified in order to guarantee performance for all users hosted on the same server.


Has this FAQ been helpful?