>
> > At present, no - the recordings must be located at the
> > ${HISTORY_PATH}/${HSITORY_UUID} location.
>
> "/var/lib/guacamole/recordings/" is the default path with correct permissions
> in guacamole.properties. Including "chown -R" for the folder.
>
> Thus "/var/lib/guacamole/recordings/servername" is same as
> "/var/lib/guacamole/recordings/${HISTORY_PATH}", i don't see why it is not
> getting listed in UI.
Not quite. ${HISTORY_PATH} _is_ the value from guacamole.properties.
So, if you put the following in guacamole.properties:
recording-search-path: /guacamole/recordings
then the ${HISTORY_PATH} token will be "/guacamole/recordings". If you
do not specify any value, then ${HISTORY_PATH} will be
/var/lib/guacamole/recordings. If you want the recordings to be
retrieved from /var/lib/guacamole/recordings/servername, then you need
to specify the following in guacamole.properties:
recording-search-path: /var/lib/guacamole/recordings/servername
It's important that the recordings be stored at the path specified by
"recording-search-path" in guacamole.properties. Also, you _must_ have
${HISTORY_UUID} as part of the recording path, since that's how the
extension associates the past connection entries in the database with
the recording files. So, if you want the the recordings to be stored
at /var/lib/guacamole/recordings/servername, you put that as
"recording-search-path" in guacamole.properties, and then in your
connections you specify ${HISTORY_PATH}/${HISTORY_UUID} as the
recording path, and give it whatever recording name you'd like.
This is covered in fairly good detail in the manual, including
explaining how the extension uses location, UUID, etc.
https://guacamole.apache.org/doc/gug/recording-playback.html
-Nick
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
