Bug 529 - tl-ssh-all/tl-rsync-all doesn't always work on agent machines
Summary: tl-ssh-all/tl-rsync-all doesn't always work on agent machines
Status: ASSIGNED
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: Misc (show other bugs)
Version: trunk
Hardware: PC Linux
: P2 Enhancement
Target Milestone: LowPrio
Assignee: Bugzilla mail exporter
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-04-27 16:03 CEST by Erik Forsberg
Modified: 2022-04-05 13:00 CEST (History)
0 users

See Also:
Acceptance Criteria:

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

Description Erik Forsberg cendio 2004-04-27 16:03:51 CEST 
tl-scp-all might need to synchronize files from a machine that is not running
vsmserver. Find out how we can fetch info about what agents are available from
an agent machine.
Comment 1 Peter Åstrand cendio 2004-08-03 14:39:53 CEST 
Agent machines has the parameter /vsmagent/master_hostname. tl-scp-all could
contact the vsmserver via XMLRPC and ask for the list of agent hosts comprising
the cluster.
Comment 2 Peter Åstrand cendio 2004-11-23 15:44:58 CET 
Probably, the strategy should be to first try to read
/vsmserver/terminalservers, and if it doesn't exist, then try to contact the vsm
server with XMLRPC. This allows the user to run tl-rsync-all on the master, even
though vsmserver is stopped. Also, if the user wants to distribute the
/vsmserver/terminalservers parameter to all hosts instead of using XMLRPC, then
can do so.
Note You need to log in before you can comment on or make changes to this bug.