Re: winSCP Connection Problem after Target Server runs script command
A have responded on the Super User:
https://superuser.com/q/1156759/213663
https://superuser.com/q/1156759/213663
- martin
Post a reply
Before posting, please read how to report bug or request support effectively.
Bug reports without an attached log file are usually useless.
Topic review
- Myo Min Thein
Re: winSCP Connection Problem after Target Server runs script command
Sorry for my incomplete question.
I've uploaded winSCP logs.
I posted same question on "https://superuser.com" to notify more developers.
Sorry for your inconvenience.
Thanks
Myo Min Thein
I've uploaded winSCP logs.
I posted same question on "https://superuser.com" to notify more developers.
Sorry for your inconvenience.
Thanks
Myo Min Thein
- martin
Re: winSCP Connection Problem after Target Server runs script command
Please attach a full session log file showing the problem (using the latest version of WinSCP).
To generate the session log file, enable logging, log in to your server and do the operation and only the operation that causes the error. Submit the log with your post as an attachment. Note that passwords and passphrases not stored in the log. You may want to remove other data you consider sensitive though, such as host names, IP addresses, account names or file names (unless they are relevant to the problem). If you do not want to post the log publicly, you can mark the attachment as private.
- Myo Min Thein
winSCP Connection Problem after Target Server runs script command
Hello guys,
I am new to winSCP.
I would like to ask you about winSCP's limitations and side effects.
WinSCP Version: 5.9.3
Protocol: SFTP
I inserted "script command" in target server to track user operations.
Here is the "script command"
.bash_profile
That command runs first whenever user's terminal starts opening.
After I inserted the command in target server, I connected target server via winSCP.
Even winSCP can be opened, I can't open winSCP's Terminal.
Please refer the following picture for error and root@10.1.9.207_env.log.
(<invalid hyperlink removed by admin>)
I found on winSCP's official site that
My understanding is
When winSCP's terminal opens, script command runs in that terminal automatically.
After script commands runs, error occurred as shown in picture(1).
I executed "script command" while the command haven't inserted in target server as environment variable.
I got error message as following picture and root@10.1.9.207_terminal.log.
(<invalid hyperlink removed by admin>)
May I know the followings!
Thanks
Myo Min Thein
I am new to winSCP.
I would like to ask you about winSCP's limitations and side effects.
WinSCP Version: 5.9.3
Protocol: SFTP
I inserted "script command" in target server to track user operations.
Here is the "script command"
.bash_profile
{
......
script -f /tmp/`date +%Y%m%d_%H%M%S`_$USER.log
[EOF]
}That command runs first whenever user's terminal starts opening.
After I inserted the command in target server, I connected target server via winSCP.
Even winSCP can be opened, I can't open winSCP's Terminal.
Please refer the following picture for error and root@10.1.9.207_env.log.
(<invalid hyperlink removed by admin>)
I found on winSCP's official site that
winSCP does not support commands that require terminal emulation or user input.
My understanding is
When winSCP's terminal opens, script command runs in that terminal automatically.
After script commands runs, error occurred as shown in picture(1).
I executed "script command" while the command haven't inserted in target server as environment variable.
I got error message as following picture and root@10.1.9.207_terminal.log.
(<invalid hyperlink removed by admin>)
May I know the followings!
How does "script command" concerns with winSCP's limitation?
What's the effect of "script command" on winSCP?
What's the effect of "script command" on winSCP?
Thanks
Myo Min Thein