I would like to automate the SI getimage tool (si_getimage command) in a script so that the server first does an SSH to the golden client to run si_prepareclient, and then it calls si_getimage.
However, the si_prepareclient requires a --server argument, and since we have several subnets on our SI server, we're missing some logic to determine the SI-servername for any golden client name. I have looked through the SystemImager directories and commands without finding any information about the SI-servername. Question: Does anyone have a small utility to run on either the server or the golden client which determines the SI server name? I could image that one of two commands like this need to be written: 1) SI server: si_getservername goldenclient-name 2) Golden client: si_getservername # the goldenclient-name is obvious Of course I can do some dirty hacks to solve the problem in an ad-hoc fashion, but I'm curious how to let SystemImager tell me this information? One solution could be for installed clients to create a small file /etc/systemimager/IMAGE_SERVER containing the servername, and this could be done in a custom post-install script like this example: # Get the Systemimager variables . /tmp/post-install/variables.txt echo $IMAGESERVER > /etc/systemimager/IMAGE_SERVER But it's perhaps not the most elegant solution... -- Ole Holm Nielsen Department of Physics, Technical University of Denmark ------------------------------------------------------------------------------ Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects _______________________________________________ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
