search for: _hosts

...list || hosts="$hosts $hostlist" + if [ -n "$found" ]; then + error_message "Warning: $host does appear to be in zone $zone already" + else + [ -z "$hosts" ] && hosts=$hostlist || hosts="$hosts $hostlist" + fi fi eval ${z}_hosts=\"$hosts\" @@ -7088,7 +7092,6 @@ fi fi done < ${STATEDIR}/chains - progress_message "$newhost added to zone $zone" done @@ -7184,7 +7187,7 @@ fi done - [ -n "$found" ] || error_message "Warning: $1 does not appear to be...

...her I keep getting this message: RSA1 key fingerprint is fa:a2:ac:d6:58:a6:48:0b:cc:13:ea:b7:d5:bd:fd:de. Are you sure you want to continue connecting (yes/no)? When I choose yes to the above message it just keeps looping through, never actually allowing me to connect and never creating the known _hosts file which I believe it should. I realize that I need a known_hosts file since that is what is in my config, but how does this file get created? I created the known_hosts file manually by cat'ng the ssh_host_key.pub and redirecting it to another then editing it and adding the servername and I...

Morning... Attached are two files. The first (smb.session) shows one user connecting to two different shares on a remote server using *no* password... The second is the smb.conf file found on that remote server, running Solaris 2.6, and Samba 2.0.3 ... I'm *really* hoping that its something that we're overlooking as far as configuration is concerned...or else there is one helluva