Bug 1143 - Run scripts at VNC connect/disconnect
Summary: Run scripts at VNC connect/disconnect
Status: CLOSED WONTFIX
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: VNC (show other bugs)
Version: trunk
Hardware: PC Linux
: P2 Enhancement
Target Milestone: 4.18.0
Assignee: Bugzilla mail exporter
URL:
Keywords:
: 2466 (view as bug list)
Depends on:
Blocks:
 
Reported: 2005-02-24 11:44 CET by Erik Forsberg
Modified: 2024-09-04 09:59 CEST (History)
1 user (show)

See Also:
Acceptance Criteria:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Comment 2 Peter Åstrand cendio 2007-03-29 17:23:29 CEST 
The time estimation assumes that the implementation will be done in Xvnc (or perhaps Xvnc/vncconfig). It could fork off a process that executes scripts in a xconnect.d/xdisconnect.d directory. To me, this looks fairly easy to implement.
Comment 3 Pierre Ossman cendio 2013-04-08 09:30:01 CEST 
Hmmm... There is a notification system already in place for connect events (VncExtQueryConnectNotifyEvent).
Comment 4 Pierre Ossman cendio 2020-01-20 09:39:17 CET 
Note that sessionreconnect.d already exists, but that is run as root on the master. The issue here is about running things in the session as the user.
Comment 6 Pierre Ossman cendio 2024-09-04 09:57:13 CEST 
*** Bug 2466 has been marked as a duplicate of this bug. ***
Comment 7 Pierre Ossman cendio 2024-09-04 09:59:46 CEST 
There is no clearly specified use case here, and it merely *might* be part of the solution for things like bug 493 or bug 7605.

Closing this bug in favour of focusing the discussion on the specific use cases we want to solve (i.e. the other open bugs).
Note You need to log in before you can comment on or make changes to this bug.