On 28/01/2005, at 6:23 AM, Andy Litzinger wrote:
>
> I did get a reply from Anshuman Karwar, who wrote hacked the clogin to
> create the nslogin script. He is running almost the same netscaler
> code revision as me and it works for him. Since he wrote the nslogin
> code, I don't know if he is using a new/different version than what is
> included in the Rancid build.
>
> anyway, I agree that it seems like nslogin is having trouble
> recognizing the prompt. Is there anyway to have rancid/ the login
> scrips dump out any more verbose info about where it is dying or
> having trouble?
>
> -andy
yes, this can be done:
$ export NOPIPE=1
$ nsrancid -d -l hostname
the output to the terminal, along with the output written into file
hostname.raw should get things started.
cheers,
-andrew
>
> I did get a reply from Anshuman Karwar, who wrote hacked the clogin to
> create the nslogin script. He is running almost the same netscaler
> code revision as me and it works for him. Since he wrote the nslogin
> code, I don't know if he is using a new/different version than what is
> included in the Rancid build.
>
> anyway, I agree that it seems like nslogin is having trouble
> recognizing the prompt. Is there anyway to have rancid/ the login
> scrips dump out any more verbose info about where it is dying or
> having trouble?
>
> -andy
yes, this can be done:
$ export NOPIPE=1
$ nsrancid -d -l hostname
the output to the terminal, along with the output written into file
hostname.raw should get things started.
cheers,
-andrew