Stopping and Starting RStudio Package Manager


Stopping and Starting

Occasionally it is necessary to start and stop the RStudio Package Manager service. Stopping and starting is handled by systemd.

After a restart, any scheduled syncs that were missed during downtime will automatically begin. See The CRAN Source for details.

The RStudio Package Manager installer installs a systemd service called rstudio-pm, which causes the RStudio Package Manager to be started and stopped automatically when the machine boots up and shuts down. The rstudio-pm service is also automatically launched during installation.

Use the following commands to manually start and stop the server:

sudo systemctl start rstudio-pm
sudo systemctl stop rstudio-pm

You can restart the server with:

sudo systemctl restart rstudio-pm

If you wish to keep the server running without interruption, but reload the configuration, you can use the systemctl command to send a HUP signal:

sudo systemctl kill -s HUP --kill-who=main rstudio-pm

The HUP signal causes the server to re-initialize but does not interrupt the current processes or any of the open connections to the server.

Use a HUP signal when your configuration changes are limited to properties marked as reloadable. See Appendix: Configuration to learn which settings may be reloaded via HUP. Perform a full restart of RStudio Package Manager when changing other properties.

You can check the status of the rstudio-pm service using:

sudo systemctl status rstudio-pm

And finally, you can use the enable/disable commands to control whether RStudio Package Manager should be run automatically at boot time:

sudo systemctl enable rstudio-pm
sudo systemctl disable rstudio-pm