dhosty

Linux & VPS · 6 min read

Linux services: Start, Stop & Automatic operation in VPS Cloud

To start, stop or automatically operate Linux services such as web servers or databases in VPS Cloud, you need basic knowledge of Linux shell. The VPS Cloud structure provides isolated containers with a common host kernel, so root access and SSH/SFTP are available. An active Linux shell experience is required for configuration of start/stop processes and automation (e.g. via cronjobs). For more details, see /vps-cloud/.

Important requirements for Linux services

To start Linux services such as web servers or databases in VPS Cloud, you need basic knowledge of the Linux shell. The isolated containers with a common host kernel allow root access and SSH/SFTP, but own software configuration requires technical expertise for the correct setup.

The VPS Cloud structure does not offer a separate virtual machine, but isolated Linux containers. This means that all services need to be configured directly via the host kernel without creating additional VM setup or specific security mechanisms for each instance.

For automated operation, cronjobs and scripts are required. The configuration of start/stop processes depends on the Linux shell experience, as the VPS Cloud does not provide pre-made service configurations for typical applications such as PHP or databases. An active shell experience is therefore essential.

Start Linux services in the VPS Cloud

To launch Linux services such as web servers or databases in VPS Cloud, you need root access via SSH or SFTP. The isolated containers share the host kernel so that services can be started directly via the shell without additional software installation. Some services such as Apache or Nginx are active by default.

The start processes are performed by commands from the Linux shell, e.g. `systemctl start apache2` for the Apache web server. For own services scripts have to be created and started in the background to ensure continuous operation. The configuration is done in the default service configuration files.

VPS Cloud does not offer a separate virtual machine, so all services need to be configured directly via the host shell. For automated startup processes, cronjobs or systemd settings are required to load services at system startup. No additional tools such as Docker are required.

Stopping Linux services in the VPS Cloud

To stop Linux services such as web servers or databases, use the SSH connection to the VPS Cloud instance. Start the service with the `systemctl stop <servicename>` command for systemd-based systems or `service <servicename> stop` for classic service managers. This is a standard Linux method that does not require any additional software installation.

For permanent stop operations, you can create automated scripts to disable services in certain events. The VPS Cloud structure allows you to run these scripts via cronjobs, which will automatically stop the services without manual intervention.

Important limitation: Since VPS Cloud uses isolated Linux containers with a common host kernel, it is only possible to stop services if you have root access. For more details, see [VPS Cloud].](/vps-cloud/).

Automatic operation with cronjobs and scripts

To start or stop Linux services automatically, use Cronjobs in the VPS Cloud Panel. These are configurable via the SSH interface and require an active shell experience for the implementation of scripts. The VPS Cloud structure allows isolated containers with a common host kernel, so that the services can be operated without additional software installation.

Cronjobs are ideal for repetitive tasks such as database startups or web server updates. They are executed in the background and do not require manual intervention. The scripts must be placed in the /root/ directory structure to run correctly from the host kernel. The VPS Cloud host supports the standard cron configuration for Linux.

Important limits: Cronjobs only work within the isolated containers and require root access. The automated mode of operation is not designed for complex services such as own virtual machines or network tools, as VPS Cloud does not offer separate VM. For advanced scripts, we recommend using SSH interfaces.

Limitations of the VPS cloud structure

VPS Cloud uses isolated Linux containers with a common host kernel, which means that services are not operated as separate virtual machines. This requires knowledge about the configuration of startup processes and automation systems such as cronjobs, as there is no separate VM structure.

The structure allows root access and SSH/SFTP, but sharing the host kernel leads to potential performance limitations at high loads. There are no isolated resources for each container, which can lead to bottlenecks in intensive services. The host kernel is accessible to all containers.

The automatic mode of operation requires scripts and cronjobs, as VPS Cloud does not offer built-in automation modules. The configuration of start and stop processes must be done manually without using additional software installations or services from the host kernel.

Which packages are suitable for Linux services?

For the configuration of web servers or databases, the packages 'Linux Start', 'Linux Plus' and 'Linux Pro' are suitable. They each offer at least 2 GB of RAM, 40–160 GB of memory and 2–6 vCPU for effective VPS cloud service scenarios. The packages are available from EUR 7.99 for 30 days.

Evaluate the package based on your actual requirements. A larger contingent can create more room for manoeuvre, but does not replace the appropriate configuration or control of utilization. The resources of the booked package and the confirmed scope of services are crucial. For a change, you first clarify target package, price and availability before switching existing data or ongoing services.

The packages are available from EUR 7.99 per month (30 days). For more details, see /help/ for the exact adaptation to your needs and the selection of the right resource combination for Linux services in the VPS Cloud model. There are no own VMs, but isolated containers with a common host kernel.

Why not own VM in VPS Cloud?

VPS Cloud uses isolated Linux containers with a common host kernel, not its own virtual machines. This enables more efficient resource management and reduces the complexity of the infrastructure through common kernel components. The structure is optimized for fast scaling and low latency.

This service is subject to the confirmed package size and the conditions agreed upon at the time of ordering. Account registration, deposit payment and payment of a specific order are different steps. Before releasing the price as well as the contained resources. Additional services must be coordinated separately; a technical act alone is not a statement of which fees are contractually agreed.

Since VPS Cloud does not provide a separate VM infrastructure, configuration of Linux services is possible directly via root access and SSH. This requires basic knowledge of the Linux shell, but provides a flexible environment for direct control of start, stop and automation processes without additional layers. For more steps, see [Help Center].](/hilfe/).

Frequently asked questions

How do I start a web server in the VPS Cloud without additional software installation?

With the Linux shell in VPS Cloud, you can start the web server directly via commands such as 'apache2' or 'nginx'. No additional software installation is required, since the environment is already configured.

Can I start and stop databases automatically with VPS Cloud without an SSH connection?

No. Automatic start/stop processes for databases require SSH access to configure cronjobs or scripts. No automation without direct server access.

Which packages are suitable for Linux services such as PHP or databases?

The packages 'Linux Start' (2 GB RAM, 40 GB memory), 'Linux Plus' (4 GB RAM, 80 GB memory) and 'Linux Pro' (8 GB RAM, 160 GB memory) are suitable for PHP or database services.

Why is there no virtual machine in VPS Cloud?

VPS Cloud uses isolated Linux containers with a common host kernel, not its own VMs. This allows for lower resource consumption and faster startup, but requires SSH access for configurations.

More hosting topics