OpenRport Docs
GITHUB
  • OpenRPort Knowledge Base
  • 👀WHAT IS RPORT
    • Features and benefits of RPort
      • Full feature list
    • Screenshots
  • 🚀GETTING STARTED
    • Install the RPort Server
      • Install on-premises
      • Install RPort on any virgin cloud VM
      • Enable two factor authentication
        • Use push on mobile for 2FA
        • Use TOTP
    • Connecting Clients
    • Using the remote access
      • Creating tunnels
        • VNC via browser
      • RDP via Browser
      • Open SSH from the browser
      • Scp,sftp through a tunnel
    • Renaming and tagging of clients
    • Organize clients with groups
    • Activate the vault
    • Manage users and permissions
  • 🗣️NEED HELP?
    • Troubleshoot common problems
      • Restart rport through a tunnel
      • Attributes file path not set
      • Recover lost passwords
      • Client is not connecting
      • Id is already in use
  • 🔦DIGGING DEEPER
    • Using the API
      • Create client credentials
    • RPort Technology Explained
    • Commands and Scripts
      • Executing commands
      • Executing scripts
      • Tacoscript
    • The scheduler
    • File copy and reception
    • Client Configuration Options
      • Supervision of OS updates
      • Script and command execution
    • Advanced client management
      • Install the RPort client manually
      • Uninstall the RPort client
      • Run with SELinux
    • Server Maintenance
      • Monitoring of RPortd
      • Updating RPort
      • Backing up the rport server
      • Renewing certificates
    • FAQ
      • How to use Cloudflare
Powered by GitBook
On this page
  1. DIGGING DEEPER
  2. Client Configuration Options

Supervision of OS updates

Starting with rport client version 0.2.4 the supervision of available operating system updates is possible

Enable Update supervision

On Linux

To enable update supervision you must have the following line in the [client] section of your /etc/rport/rport.conf file.

[client]
 # ...snip ...snap
 updates_interval = '4h'

A refresh of the update status can be requested through the API and the user interface independently of the specified update interval. Going faster than 4 hours is usually not need and not recommended.

Don't forget to restart the rport client after changing the configuration file. Use systemctl restart rport.

⚠️ Debian, Ubuntu and SuSE Linux need a sudo rule to fetch the update status. Create a file /etc/sudoers.d/rport-update-status with the following content.

/etc/sudoers.d/rport-update-status
rport ALL=NOPASSWD: SETENV: /usr/bin/apt-get update -o Debug\:\:NoLocking=true
/etc/sudoers.d/rport-update-status
rport ALL=NOPASSWD: SETENV: /usr/bin/zypper refresh *
PreviousClient Configuration OptionsNextScript and command execution

Last updated 1 year ago

🔦