Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Sat, 2 Jul 2005 20:57:49 -0700 (PDT) From: daemon AT ISI DOT EDU Message-Id: <200507030357.j633vnb14395@gamma.isi.edu> To: cygwin AT cygwin DOT com Subject: Re: Qestion about Bash Fork Resource Temporily Unavailable for NS2.28 and NS2.27 References: <6 DOT 2 DOT 1 DOT 2 DOT 0 DOT 20050701114811 DOT 03d3eb08 AT pop DOT prospeed DOT net> <20050701204659 DOT 17344 DOT qmail AT web30106 DOT mail DOT mud DOT yahoo DOT com> <6 DOT 2 DOT 1 DOT 2 DOT 0 DOT 20050702234055 DOT 03c5a930 AT pop DOT prospeed DOT net> In-Reply-To: <6.2.1.2.0.20050702234055.03c5a930@pop.prospeed.net> X-Loop: ns-users AT isi DOT edu X-ISI-4-38-10-MailScanner: Found to be clean X-MailScanner-From: daemon Note-from-DJ: This may be spam Welcome to posting to the ns-users mailing list! We automatically send this message to every new person who sends mail to the list. You should only receive it once. My apologies if the program contacts you twice, perhaps because you have multiple e-mail addresses or send mail from multiple machines. If you are an experienced ns-user who simply has not posted since we started using this responder, our apologies for inconveniencing you with this message. This message is intended to help inform users and cut down on redundant posts, which benefits everyone. Please look at the attached list of ns Frequently Asked Questions. If it answers your question, great! You're done. If not, please RE-SEND your original message to ns-users AT isi DOT edu. A copy of your original message is included below for reference. You will NOT have to do re-send your message every time you post, only the FIRST time you send from a new account. The goal is to quickly help new users find the FAQ (hopefully answering their question). Thanks, -the ns development team ---------------------------------------- The Network Simulator ns-2: Frequently Asked Questions (This FAQ is also on the web at http://www.isi.edu/nsnam/ns/ns-faq.html.) * _Where do I get ns?_ From the ns web site at http://www.isi.edu/nsnam/ns/ns.html and the download page http://www.isi.edu/nsnam/ns/ns-tests.html. * _What platforms does ns run on and what kind of hardware do I need?_ Please see "where to start" on the building ns web page: http://www.isi.edu/nsnam/ns/ns-build.html#start. * _What should I do if I have trouble downloading/extracting ns?_ This question is answered in detail at http://www.isi.edu/nsnam/ns/ns-problems.html#downloading. * _What should I do if I encounter problems building ns?_ Check: 1. the README that comes in the distribution (very brief), 2. the "installation problems, bug fixes and help" web page http://www.isi.edu/nsnam/ns/ns-problems.html, 3. the archives of the ns-users mailing list http://www.isi.edu/nsnam/ns/ns-lists.html, 4. post a bug report (see below) http://www.isi.edu/cgi-bin/nsnam/reportbug.cgi. * _What do I do after I successfully build ns?_ + Put the path to your ns executable into your PATH environment + Put the path to your otcl into your LD_LIBRARY_PATH environment + Put the path to your tcl library into your TCL_LIBRARY environment * _Where can I find documentation for ns?_ All documentation is linked from the main ns web page http://www.isi.edu/nsnam/ns/. Documentation includes a tutorial (originally from Marc Greis) and a reference manual (ns notes and documentation). * _Words, words, words... that documentation is nice, but where are some sample scripts I can start from?_ Many sample scripts can be found in the ns distribution in ~ns-2/tcl/ex and ~ns-2/tcl/test. * _What protocols does ns support?_ A lot! Almost all variants of TCP, several forms of multicast, wired networking, several ad hoc routing protocols and propagation models (but not cellular phones), data diffusion, satellite, and other stuff. See the documentation (described above) for details, or download ns and look. * _How do I know that ns correctly implements these protocols?_ Ns has validation tests that cover many protocols, see http://www.isi.edu/nsnam/ns/ns-tests.html. However, ultimately users are responsible for verifying that ns is accurate for their purposes---since we cannot foresee all the ways ns may be used, we cannot test all cases with all inputs. * _Are there any contributed/additional protocols not in the main distribution?_ Yes, please see the contributed code web page http://www.isi.edu/nsnam/ns/ns-contributed.html. The mailing list archives can also be helpful (see below). * _How should I get started doing something (like implementing a new protocol or trying an experiment)?_ We recommend that you look through the tutorial (see documentation, above), then start with an example program that is most similar to yours (in the tutorial, or in tcl/ex or tcl/test in the distribution), and then start changing things. * _What should I do to compile ns to reflect my changes if I've modified some .cc or .h files?_ go to ns directory and run "make" or "make depend; make" * _How do I subscribe to the ns-users mailing list? How do I search old list archives? I can't take any more---how do I get off this list?_ To subscribe or unsubscribe, see http://www.isi.edu/nsnam/ns/ns-lists.html. The list archive is at http://www.isi.edu/nsnam/ns/ns-lists.html. * _What if I have a question that's not answered here?_ If you've checked the installation problems and bug fixes web page (http://www.isi.edu/nsnam/ns/ns-problems.html) and there's no answer to your question, you may want to file a bug report or post a question to the ns-user's mailing list. First, you should check the archive of the list at http://www.isi.edu/nsnam/ns/ns-lists.html. Your question may already be answered there. If not, you can post a bug report using the web form at http://www.isi.edu/cgi-bin/nsnam/reportbug.cgi. If your question is NOT about ns implementation bugs, you may wish to post to the list. First you should subscribe. Subscription instructions are at http://www.isi.edu/nsnam/ns/ns-lists.html. _Please note that mail sent to the list is publicly distributed and archived. _If you have concerns about your message being made public (spam harvesting of your address), please consider that _before_ posting. We cannot remove messages from reciepient's mailboxes or the public archive after they're posted. When posting bug reports, please _always_ include information including at least (the bug report form includes spaces for these): + what version of ns you're using, + what operating system you're running on (not just Linux or Solaris, but RedHat version 7.0 or Solaris 2.4---send us the output of "uname -a"), + what specific behavior you see (if ns doesn't compile, what's the specific error; if TCP does something strange, what exactly did it do [send a pointer to a packet trace]), + what behavior you expected to see (if ns doesn't compile this is obvious, but if TCP does something strange, why is it strange, where is the TCP spec violated?), + pointers to your script detailed output files, + a statement that "yes, I've read the FAQ, ns-problems page, and manual and I couldn't find the answer there" (or a statement about why you didn't do that yet :-) A reminder about mailing list etiquette: + Please check the web pages and list archives before posting your question. + Please keep the body of your post to simple ASCII, not HTML. + Please do _not_ send large attachments (if what you have is bigger than a few kilobytes, put it on a web page and send a URL) + Before posting a question like "did people see my post" or "the list seems down", please check the archives (you can answer this question more accurately by checking yourself rather than asking). + Please don't post subscribe/unsubscribe requests directly to the list, use the lists' information page. (see the web page mentioned above for details). _________________________________________________________________ ---------------------------------------- From lh-no-personal-replies-please AT cygwin DOT com Sat Jul 2 20:57:48 2005 Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by gamma.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id j633vAr14139 for ; Sat, 2 Jul 2005 20:57:10 -0700 (PDT) Received: from mail.prospeed.net (mail.prospeed.net [12.46.111.140]) by vapor.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id j633uoA17514 for ; Sat, 2 Jul 2005 20:56:51 -0700 (PDT) Received: from enterprise-e.cygwin.com (lhall.prospeed.net [12.46.110.44] (may be forged)) by mail.prospeed.net (8.13.0/8.13.0) with ESMTP id j633uLO9004900; Sat, 2 Jul 2005 23:56:32 -0400 Reply-To: Cygwin List Message-Id: <6 DOT 2 DOT 1 DOT 2 DOT 0 DOT 20050702234055 DOT 03c5a930 AT pop DOT prospeed DOT net> X-Mailer: QUALCOMM Windows Eudora Version 6.2.1.2 Date: Sat, 02 Jul 2005 23:56:07 -0400 To: Question NS , Cygwin List , twall AT oculustech DOT com, ns-users AT ISI DOT EDU From: Larry Hall Subject: Re: Qestion about Bash Fork Resource Temporily Unavailable for NS2.28 and NS2.27 In-Reply-To: <20050701204659 DOT 17344 DOT qmail AT web30106 DOT mail DOT mud DOT yahoo DOT com> References: <6 DOT 2 DOT 1 DOT 2 DOT 0 DOT 20050701114811 DOT 03d3eb08 AT pop DOT prospeed DOT net> <20050701204659 DOT 17344 DOT qmail AT web30106 DOT mail DOT mud DOT yahoo DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-ISI-4-39-6-MailScanner: Found to be clean X-ISI-4-38-10-MailScanner: Found to be clean X-MailScanner-From: lh-no-personal-replies-please AT cygwin DOT com At 04:46 PM 7/1/2005, you wrote: >Hi, all, > >While I restart cygwin after I failed to install >NS2.27 or NS2.28, it shows, >bash: /usr/bin/id: Resource temporarily unavailable > 6 [main] bash 62528 fork_parent: child 62624 >died waiting for longjmp befo >re initialization >bash: fork: Bad file descriptor > >Then I restarted it, it shows >bash: fork: Resource temporarily unavailable > >Your help is appreciated! Well, I've reviewed your cygcheck output and didn't find anything there which was obviously wrong. I'm assuming that the version of 'bash' you have installed now is the same version as the one you see this problem with (i.e. bash 2.05b-17 and not the test version 3.0-2). If that is the case, then you've answered Brian's (very good) question. You might want to take a look at Eric Blake's message on a somewhat related thread: The last paragraph may be applicable to your situation. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 838 Washington Street (508) 893-9889 - FAX Holliston, MA 01746 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/