Overview

This article explains how to configure a custom temporary folder for JetPatch Connector installation on Linux and Windows endpoints. 

This configuration only affects initial connector installation, as connector upgrades do not use the /tmp directory.

Upgrade Behavior

The temp path configuration described in this article does not apply to connector upgrades. The behavior differs between initial installation and upgrade as follows:

This means:

• If /var/jetpatch-temp has restrictive permissions on an endpoint, initial installation will fail but upgrades will succeed as long as /tmp is writable.
• Changing the temp path configuration does not affect upgrade behavior.
• The temp path configuration persists across JetPatch console upgrades — it does not need to be re-applied after upgrading the JetPatch server.

Configuration File Location

For Versions Before 5.0

Edit the following file on the JetPatch server:

For Version 5.0 and Later

Configuration Steps

For Linux Endpoints

Add the following lines to the top of the configuration file (after <root>), replacing "REAL PATH TO TEMP DIR" with the desired tmp path (e.g., /var/tmp):

For Windows Endpoints

Add the following lines to the top of the configuration file (after <root>), replacing "REAL PATH TO TEMP DIR" with the desired tmp path (e.g., C:\Windows\temp):

Applying the Changes

After saving the changes to the configuration file, restart the appropriate service:

Required Permissions

The configured temp directory must exist on the target endpoint before JetPatch attempts to use it, and the JetPatch user (the account assigned to that endpoint) must have read, write, and execute permissions on it.

To set the correct permissions on the default path:

chmod 777 /var/jetpatch-temp

Or to scope it to the JetPatch user's group:

chown root:<jetpatch-user-group> /var/jetpatch-temp
chmod 775 /var/jetpatch-temp

Note: Permissions on /var/jetpatch-temp are not set by JetPatch automatically. They must be configured by a root/sudo user on each target machine. If the directory has incorrect permissions, initial connector installation will fail with a Permission denied error even when the JetPatch user has full sudo privileges — this is because the permission check happens at the file copy stage, before any sudo escalation.

To verify the JetPatch user can write to the directory:

sudo -u <jetpatch-user> bash -c 'echo test > /var/jetpatch-temp/test.sh && rm /var/jetpatch-temp/test.sh && echo OK'