On January 11, 2026 2:18:42 PM PST, Nick Couchman <[email protected]> wrote: >On Sun, Jan 11, 2026 at 10:14 AM Adam Hajdul <[email protected]> wrote: >> >> Thank you for info. >> Is there anywhere info about this behaviour specified? Or should i ask on >> developers mail list for devs to comment and confirm? >> Thanks again! >> >> On Fri, Jan 9, 2026 at 2:10 PM Arnaud bourree <[email protected]> >> wrote: >>> >>> Hi, >>> >>> I did something similar with one user "actor" and others "whatcher". >>> For that, I define one connection RW for the actor recording session and >>> one sharing profile RO for watchers without recording. >>> Then I'd have one recording per session, but watchers cannot join before >>> actor nor stay after >>> >>> Regards, >>> >>> Arnaud >>> >>> Le ven. 9 janv. 2026 à 11:12, Adam Hajdul <[email protected]> a écrit : >>>> >>>> Hello All, >>>> >>>> I am writing custom application based on guacd 1.6.0. >>>> I am parsing guacamole protocol on my own. >>>> I am working with session recording and session joining. >>>> Joining existing guacamole sessions works for me. Recording session of a >>>> single user/connection works for me. >>>> I have a problem for recording multiple users/clients joined same session. >>>> >>>> As, after initial connection is done, clients/users can connect and >>>> disconnect freely until last one leaves, I would like to have recording >>>> file created for every user separately. >>>> On the initial connection, I see log "Recording of session will be saved >>>> to..." but not after joining (i use different recording name in protocol >>>> msg exchange). >>>> Before I share more logs and details, I would like to ask whether its >>>> possible at all? >>>> What is the behaviour of guacd for such scenarios? >>>> Maybe it keeps single recording for entire lifetime of guacamole session? >>>> If yes, is it possible to split it? >>>> I wasnt able to grasp that from protocol documentation. >>>> > >Adam, >The recording of a connection is done at the connection level (client, >in guacd terms) and not at the user level. I think this has a couple >of implications for what you're asking: >* There is only ever a single recording for a connection (client), >and, if configured, it starts when the connection (client) starts >(when the first user, the connection owner, connects), and ends when >the connection (client) ends (when the last user disconnects). >* Recordings are not associated with any particular user on a >connection - the closest association would be with the connection >owner, since that's the user who starts the connection, but there are >not, nor is there any current mechanism for, creating a recording for >each individual user. > >Implementing the functionality that I think you're requesting is >possible, but it would require changes in the guacd code to move the >recording functionality out of the client part of the code and over to >the user part of the code, and would also require some additional >handling of naming of the recordings to make sure that unique >recordings are created for each user. > >Maybe you could describe in more detail why you want separate >recordings for each user - what use-case you're trying to meet that >would require that? > >-Nick > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [email protected] >For additional commands, e-mail: [email protected] >
Each user sharing an active connection also receives the exact same data as all other users (with the exception of things like file transfer), so recording connections on a per user basis would mostly produce redundant copies of the same recording. - Mike --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
