Yes, Corinna, I reverted this setting again to the default 384MB heap size
calling:
$ peflags --cygwin-heap=0 /usr/sbin/sshd.exe
and
$ peflags --cygwin-heap=0 /usr/bin/cygrunsrv.exe
Later on, someone has recommended me to downgrade cygrunsrv from 1.36-1 to
1.34-1. This helped, so now under cygwin1.dll 1.7.11 the sshd can be
started. However, the mechanism behaves strange reporting problems:
C:\>net start sshd
The CYGWIN sshd service is starting.
The CYGWIN sshd service could not be started.
The service did not report an error.
More help is available by typing NET HELPMSG 3534.
Having a look into the Event Viewer of my Win2k3 64bit machine, I
correspondingly find:
... `sshd' service stopped, exit status: 0.
This however is misleading, since I clearly see the sshd running now (I
made sure it was not running before), and indeed I can now connect using
slogin and sftp:
top - 14:41:26 up 21:27, 0 users, load average: 0.00, 0.00, 0.00
Tasks: 3 total, 1 running, 2 sleeping, 0 stopped, 0 zombie
top - 14:42:48 up 21:29, 1 user, load average: 0.00, 0.00, 0.00
Tasks: 7 total, 1 running, 6 sleeping, 0 stopped, 0 zombie
Cpu(s): 0.0% user, 0.4% system, 0.0% nice, 99.6% idle
Mem: 13630564k total, 2475144k used, 11155420k free, 0k buffers
Swap: 2095104k total, 56792k used, 2038312k free, 0k cached
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
14960 mylogin RT 0 5128 5272 1144 R 2 0.0 0:00.09 top
14616 mylogin RT 0 4668 4596 952 S 0 0.0 0:00.06 sftp-server
14132 cyg_serv RT 0 6380 6840 960 S 0 0.1 0:00.06 sshd
14460 mylogin RT 0 6596 7440 2064 S 0 0.1 0:00.14 tcsh
14104 mylogin RT 0 4336 3844 888 S 0 0.0 0:00.07 ash
14444 mylogin RT 0 6096 6796 2068 S 0 0.0 0:00.04 tcsh
14340 cyg_serv RT 0 9784 10m 1876 S 0 0.1 0:00.12 sshd
When I try to start sshd from Services menu accessible from the
Administrative Tools menu, I also get a message that the sshd has been
started and then stopped again (even though it actually runs). And in the
Status column no "Started" entry occurs.
Hope this report may help to fix these problems seemingly related to
cygwin1.dll 1.7.11 and cygrunsrv 1.36-1. Now I have downgraded to
cygrunsrv 1.34-1 and sshd can be used, whereas earlier I found that
cygrunsrv 1.36-1 and cygwin1.dll 1.7.9 (I had manually downgraded) also
made sshd launchable as service (but have not documented the messages, I
think similar misleading start-stop messages were given).
Thanks - Ulf-Dietrich
On Sun, 4 Mar 2012, it was written:
You wrote:
> $ peflags --cygwin-heap=1024 /usr/sbin/sshd.exe
Did you revert this setting? It's a hell of a lot of heap, which just
by itself can break fork. sshd doesn't need that much heap anyway.
Corinna
On Mar 3 20:16, Ulf-Dietrich Braumann wrote:
> On Sat, 3 Mar 2012, Larry Hall (Cygwin) wrote:
>
> >Try this:
> >http://cygwin.com/faq-nochunks.html#faq.using.fixing-fork-failures
>
> Thanks. Unfortunately, rebaseall did not help. I also tried
> peflagsall and a reboot, but no change. Also, I do not run programs
> mentioned in the BLODA (Big List Of Dodgy Apps). And, when I
> temporally replace the present cygwin1.dll version 1.7.11 with an
> old version 1.7.9 copied from another non-updated installation, the
> sshd again can be started as service, i.e. the fork problem does not
> occur.
>
> Any more ideas?
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
