diagnostic logging and other bits...

Working on an evil solaris 5.7 box running ssh1, and am having loads of problems - is there any method for directly logging all transfer errors and response codes.

Seems to be a serious issue with the way the box itself is configured - and I'm trying to establish where the fault lies.


Also - an easier method of creating dummy files and folders for testing might be nice also.

Great product -

Cheers,

Scott

scottyman wrote:

Working on an evil solaris 5.7 box running ssh1, and am having loads of problems - is there any method for directly logging all transfer errors and response codes.

Logging feature is not enough? What other information do you have?

scottyman wrote:

Also - an easier method of creating dummy files and folders for testing might be nice also.

Can you explain this, please?

Yeah - sorry,
Just to clarify -
I'm not getting what appear to be valid response codes back in scp operations over ssh1 -
remote host is not using bash :( I don't know solaris, but it looks pretty bastardised, and logging does not appear to be logging fully... if at all, getting lines and lines and lines of null characters as soon as login is completed.

Re: files and folders, I don't seem to be able to create folders or even dummy files, have to manually create dummy files locally then upload them. Again - could be a problem with the remote server.

Will look tomorrow AM, and give you a sample of the log.

Ta,

Scott

scottyman wrote:

Re: files and folders, I don't seem to be able to create folders or even dummy files, have to manually create dummy files locally then upload them.

Dummy files cannot be created with WinSCP. But you can create new directory (for example using F7 hot key in Norton Commander interface).