MobileRead Forums - View Single Post - ssh shell/ftp access for PocketBook Pro readers

rkomar · 10-05-2015, 10:04 AM

The sshd.log file is only created when the sshd daemon is started in the sshd_start.app script. I don't see how it would be created when the device starts up (unless the device automatically runs the sshd_start.app script for some reason).

In the sshd_start.app script, change the "-q" to a "-d" in the line:

Code:

	-q -e 1> "$SSHDIR"/sshd.log 2> "$SSHDIR"/sshd.log

and it should output more debugging information to the log file. Perhaps you will be able to see the problem then. Note that the information may not have been written to the log file yet if the sshd daemon is still running. The system may be buffering the output before writing it to the log file. In that case, you need to stop the daemon with the sshd_stop.app script before the sshd.log file is updated.

10-05-2015, 10:04 AM	#61
rkomar Wizard Posts: 3,058 Karma: 18821071 Join Date: Oct 2010 Location: Sudbury, ON, Canada Device: PRS-505, PB 902, PRS-T1, PB 623, PB 840, PB 633	The sshd.log file is only created when the sshd daemon is started in the sshd_start.app script. I don't see how it would be created when the device starts up (unless the device automatically runs the sshd_start.app script for some reason). In the sshd_start.app script, change the "-q" to a "-d" in the line: Code: -q -e 1> "$SSHDIR"/sshd.log 2> "$SSHDIR"/sshd.log and it should output more debugging information to the log file. Perhaps you will be able to see the problem then. Note that the information may not have been written to the log file yet if the sshd daemon is still running. The system may be buffering the output before writing it to the log file. In that case, you need to stop the daemon with the sshd_stop.app script before the sshd.log file is updated.