miss handling of the SIGHUP signal for sshd when sshd is started with a relative path sshd_config file

[Peter Stuge]

Hello,

施威 wrote:
> root at sshpa6# /opt/ssh/sbin/sshd -f ./sshd_config                  ### ./sshd_config is a relative path
> root at sshpa6# ps -ef|grep sshd
>     root 12616     1  0 15:51:00 ?         0:00 /opt/ssh/sbin/sshd -f ./sshd_config
>     root 12618 17401  0 15:51:03 pts/tb    0:00 grep sshd
> root at sshpa6# kill -HUP 12616
> root at sshpa6# ps -ef|grep sshd
>     root 12620 17401  0 15:51:12 pts/tb    0:00 grep sshd        ### sshd is killed but not restarted as it should be.
> 
> 
> So is it a bug or a normal situation?

Good question. Can you check your log files to try to find more
information about why sshd is not started again?


//Peter