Cannot fork: Resource temporarily unavailable
I am trying to rebuild the Cygwin tools under W98 and keep getting this
error message when running make:
Cannot fork: Resource temporarily unavailable.
Despite rebooting the machine and ensuring that sufficient swap space is
available this continues to recur.
This is the extract from the make.log
fi
make[2]: Leaving directory `/obj/i686-pc-cygwin/libiberty'
make[1]: Leaving directory `/obj/i686-pc-cygwin/libiberty'
Configuring in i686-pc-cygwin/winsup
loading cache ../config.cache
checking host system type... i686-pc-cygwin
checking target system type... i686-pc-cygwin
checking build system type... i686-pc-cygwin
checking for gcc... (cached) gcc -L/obj/i686-pc-cygwin/winsup
-L/obj/i686-pc-cygwin/winsup/cygwin -L/obj/i686-pc-cygwin/winsup/w32api/lib
-isystem /src/winsup/include -isystem /src/winsup/cygwin/include -isystem
/src/winsup/w32api/include -isystem /src/newlib/libc/sys/cygwin -isystem
/src/newlib/libc/sys/cygwin32 -B/obj/i686-pc-cygwin/newlib/ -isystem
/obj/i686-pc-cygwin/newlib/targ-include -isystem /src/newlib/libc/include
checking whether we are using GNU C... (cached) yes
checking whether gcc -L/obj/i686-pc-cygwin/winsup
-L/obj/i686-pc-cygwin/winsup/cygwin -L/obj/i686-pc-cygwin/winsup/w32api/lib
-isystem /src/winsup/include -isystem /src/winsup/cygwin/include -isystem
/src/winsup/w32api/include -isystem /src/newlib/libc/sys/cygwin -isystem
/src/newlib/libc/sys/cygwin32 -B/obj/i686-pc-cygwin/newlib/ -isystem
/obj/i686-pc-cygwin/newlib/targ-include -isystem /src/newlib/libc/include
accepts -g... (cached) yes
checking for g++... c++ -L/obj/i686-pc-cygwin/winsup
-L/obj/i686-pc-cygwin/winsup/cygwin -L/obj/i686-pc-cygwin/winsup/w32api/lib
-isystem /src/winsup/include -isystem /src/winsup/cygwin/include -isystem
/src/winsup/w32api/include -isystem /src/newlib/libc/sys/cygwin -isystem
/src/newlib/libc/sys/cygwin32 -B/obj/i686-pc-cygwin/newlib/ -isystem
/obj/i686-pc-cygwin/newlib/targ-include -isystem /src/newlib/libc/include
checking whether make sets ${MAKE}... (cached) yes
updating cache ../config.cache
creating ./config.status
/src/winsup/configure: Cannot fork: Resource temporarily unavailable
/src/winsup/configure: Cannot fork: Resource temporarily unavailable
make: *** [configure-target-winsup] Error 1
Can anyone offer me any advice.
Thanks.
> Best Regards
> Jim
> ___
> BT Computing Partners
> Intelligent Systems Management
> __
>
>
>
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
OpenSSH PublicKeyAuthentication failure using cygrunsrv
I have recently installed the latest Cygwin Version on my W2k test server along with the latest OpenSSH package. I find that if I manually start the sshd daemon I can login ok using PublicKeyAuthentication but when I create an NT Service using cygrunsrv that this fails (although password authentication is ok).I suspect that this may be a permissions problem but have run out of things to try. Here is the debug output from the sshd server using the loopback address. If anyone can offer any advice/suggestions,it would be much appreciated. Thanks. OpenSSH_3.6.1p1, SSH protocols 1.5/2.0, OpenSSL 0x0090701f debug1: Reading configuration data /etc/ssh_config debug1: Rhosts Authentication disabled, originating port will not be trusted. debug2: ssh_connect: needpriv 0 debug1: Connecting to hhh [81.134.40.222] port 22. debug1: Connection established. debug1: identity file /ssh/.ssh/identity type -1 debug1: identity file /ssh/.ssh/id_rsa type -1 debug3: Not a RSA1 key file /ssh/.ssh/id_dsa. debug2: key_type_from_name: unknown key type '-BEGIN' debug3: key_read: missing keytype debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug2: key_type_from_name: unknown key type '-END' debug3: key_read: missing keytype debug1: identity file /ssh/.ssh/id_dsa type 2 debug1: Remote protocol version 1.99, remote software version OpenSSH_3.6.1p1 debug1: match: OpenSSH_3.6.1p1 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_3.6.1p1 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha1,diffie-hellman-group1-sha1 debug2: kex_parse_kexinit: ssh-rsa,ssh-dss debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour,aes192-cbc,aes256-cbc,r [EMAIL PROTECTED] debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour,aes192-cbc,aes256-cbc,r [EMAIL PROTECTED] debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,hmac-ripemd160,[EMAIL PROTECTED],hmac-sha1-96,hm ac-md5-96 debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,hmac-ripemd160,[EMAIL PROTECTED],hmac-sha1-96,hm ac-md5-96 debug2: kex_parse_kexinit: none,zlib debug2: kex_parse_kexinit: none,zlib debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: first_kex_follows 0 debug2: kex_parse_kexinit: reserved 0 debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha1,diffie-hellman-group1-sha1 debug2: kex_parse_kexinit: ssh-rsa,ssh-dss debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour,aes192-cbc,aes256-cbc,r [EMAIL PROTECTED] debug2: kex_parse_kexinit: aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour,aes192-cbc,aes256-cbc,r [EMAIL PROTECTED] debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,hmac-ripemd160,[EMAIL PROTECTED],hmac-sha1-96,hm ac-md5-96 debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,hmac-ripemd160,[EMAIL PROTECTED],hmac-sha1-96,hm ac-md5-96 debug2: kex_parse_kexinit: none,zlib debug2: kex_parse_kexinit: none,zlib debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: first_kex_follows 0 debug2: kex_parse_kexinit: reserved 0 debug2: mac_init: found hmac-md5 debug1: kex: server->client aes128-cbc hmac-md5 none debug2: mac_init: found hmac-md5 debug1: kex: client->server aes128-cbc hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug2: dh_gen_key: priv key bits set: 115/256 debug2: bits set: 1595/3191 debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug3: check_host_in_hostfile: filename /ssh/.ssh/known_hosts debug3: check_host_in_hostfile: match line 1 debug3: check_host_in_hostfile: filename /ssh/.ssh/known_hosts debug3: check_host_in_hostfile: match line 3 debug1: Host 'hh' is known and matches the RSA host key. debug1: Found key in /ssh/.ssh/known_hosts:1 debug2: bits set: 1590/3191 debug1: ssh_rsa_verify: signature correct debug2: kex_derive_keys debug2: set_newkeys: mode 1 debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug2: set_newkeys: mode 0 debug1: SSH2_MSG_NEWKEYS received debug1: SSH2_MSG_SERVICE_REQUEST sent debug2: service_accept: ssh-userauth debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey,password,keyboard-interactive debug3: start over, passed a different list publickey,password,keyboard-interactive debug3: preferred publickey,keyboard-interactive,password debug3: authmethod_lookup publickey debug3: remaining preferred: keyboard-interactive,password debug3: authmethod_is_enabled publickey debug1: Next authentication method: public
cygwin1.dll
Sirs, We are proposing to use the Red Hat OpenSSH package on our NT/W2K servers but some concerns have been raised re. the Cygwin1.dll shared memory vulnerability. As the only Cygwin application running on these machines will be OpenSSH I am not sure how significant a risk may exist. Can you please explain how this vulnerabilty could be exploited so that we can determine what if any counter measures we could deploy. Thanks. > Best Regards > Jim > ___ > BTcd Computing Partners > Intelligent Systems Management > >___ -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: cygwin1.dll
Igor, Thanks for this info. The only Cygwin executables being installed will be those to support OpenSSH on that machine e.g. ssh-keygen,scp,sftp etc. I still do not have a clear understanding of how a user could "hijack" a cygwin process running as system account,effectively bypassing system security. Any info. would be most appreciated. Thanks. > Best Regards > Jim > ___ > BTcd Computing Partners > Intelligent Systems Management -Original Message- From: Igor Pechtchanski [mailto:[EMAIL PROTECTED]] Sent: 24 January 2003 16:36 To: Davidson,JA,Jim,YES82 R Cc: [EMAIL PROTECTED] Subject: Re: cygwin1.dll On Fri, 24 Jan 2003 [EMAIL PROTECTED] wrote: > Sirs, > We are proposing to use the Red Hat OpenSSH package on our NT/W2K servers > but some concerns > have been raised re. the Cygwin1.dll shared memory vulnerability. > As the only Cygwin application running on these machines will be OpenSSH I > am not sure how > significant a risk may exist. > Can you please explain how this vulnerabilty could be exploited so that we > can determine > what if any counter measures we could deploy. > Thanks. Jim, I'd like to correct one misconception in your message. You said that OpenSSH (I assume you mean sshd) will be "the only Cygwin application running on these machines". However, any time a user logs on, sshd will spawn a shell, and that will spawn whatever other applications the user runs. Some of them will most certainly be Cygwin applications. Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_[EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_[EMAIL PROTECTED] |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! Oh, boy, virtual memory! Now I'm gonna make myself a really *big* RAMdisk! -- /usr/games/fortune -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Cscript.exe no longer executable
Sirs, I recently installed the latest version of OpenSSH on our W2K test system which ships with Cygwin1.dll V 1.3.12. I now find that we can no longer execute any VBS scripts from an SSH session as the cscript.exe gives an error: "The application could not be initialized correctly (0xc005) Click on OK to terminate the application" when we try to initialise it. I have a work around from a previously reported problem which is to load an older version of the dll (1.3.10) which allows us to execute these scripts but unfortunately gives us another problem in that it takes around 30 seconds to setup the ssh connection. Can we have a fix for 1.3.12 to allow us to execute cscript.exe without suffering the delays in the login process. Thanks. > Jim > ___ > BT Computing Partners > Intelligent Systems Management >[EMAIL PROTECTED] > > ___ > > > -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
