Hi,
just a little note...
when we use a ssh tunnel to transfer data from the client to the image-server, I see the client runs a 'sleep 14400' on the image-server to keep up the encrypted connection... but if you perform installations with many clients (of if you perform very frequently installations) a hudge amount of ugly "sleep" tasks will be created on the image-server.
Well... this is not a problem, but what do you think if we open a tunnel using the -N option? In this way the ssh-tunnel will be up until the client reboots and no tasks will be forked on the image-server. And I don't see any reason to keep the timeout...
If you like this, I could apply this patch...
Bye, -Andrea
-- Andrea Righi System Management Group - CINECA - http://www.cineca.it Via Magnanelli 6/3 40033 Casalecchio di Reno (BO) - Italy e-mail: [EMAIL PROTECTED]
--- initrd_source/skel/etc/init.d/functions~ 2004-12-25 06:22:04.000000000
+0100
+++ initrd_source/skel/etc/init.d/functions 2005-01-29 12:40:52.000000000
+0100
@@ -1142,9 +1142,6 @@
if [ ! -z $PRIVATE_KEY ]; then
# With the prep ready, start the ssh tunnel connection.
- # the sleep command executes remotely. Just need something long here
- # as the connection will be severed when the newly imaged client
reboots
- # 14400 = 4 hours...if we're not imaged by then....oh boy!
#
# Determine if we should run interactive and set redirection options
appropriately.
# So if the key is blank, go interactive. (Suggested by Don Stocks
<[EMAIL PROTECTED]>)
@@ -1156,7 +1153,7 @@
REDIRECTION_OPTIONS=""
fi
- CMD="ssh -l $SSH_USER -n -f -L873:127.0.0.1:873 $IMAGESERVER sleep
14400 $REDIRECTION_OPTIONS"
+ CMD="ssh -N -l $SSH_USER -n -f -L873:127.0.0.1:873 $IMAGESERVER
$REDIRECTION_OPTIONS"
echo $CMD
$CMD || shellout
