Re: Where is documentation on bash "wait"?

Re: Where is documentation on bash "wait"?

[Eric Blake]

> I tried info and man and could not find any information on wait. I want to
> (using bash)

Did you try 'man wait'?  That would have pointed you to 'man bash', where
as a bash builtin, wait is properly documented.  Also, 'info bash' will tell you
about bash builtins, or you can try 'help wait' for a short synopsis.

> 
> (1) How do I wait for multiple children and wake up when the first one dies?

wait

> 
> (2) Examine the status code of the dead child and possibly spawn a new one?

I don't know of any way in POSIX to do this, but it is not really specific to
cygwin, so you might try asking a more appropriate mailing list.

--
Eric Blake
volunteer cygwin bash maintainer



--
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/

Re: Where is documentation on bash "wait"?

[Bas van Gompel]

Op Sat, 15 Oct 2005 17:45:06 +0000 schreef Eric Blake
in <101520051745.25630.43514022000160940000641E22007614380A050E040D0C079D0A@comcast.net>:
[What the...]
: > I tried info and man and could not find any information on wait. I want to
: > (using bash)
:
:  Did you try 'man wait'?  That would have pointed you to 'man bash', where

Did /you/ try it?

It complains about not finding bash.1.
Do you have a copy of bash.1 lying around somewhere?

To get this to work as I think it is intended, I need to:

1) gunzip /usr/share/man/man1/bash.1.gz and
   /usr/share/man/man1/bash_builtins.1.gz

2) patch /usr/share/man/man1/bash_builtins.1 like so:
--- /usr/share/man/man1/bash_builtins.1~	2005-10-15 21:27:52.000000000 +0200
+++ /usr/share/man/man1/bash_builtins.1	2005-10-15 21:44:33.770000000 +0200
@@ -10,6 +10,6 @@
 ulimit, umask, unalias, unset, wait \- bash built-in commands, see \fBbash\fR(1)
 .SH BASH BUILTIN COMMANDS
 .nr zZ 1
-.so bash.1
+.so man1/bash.1
 .SH SEE ALSO
 bash(1), sh(1)

3) re-gzip /usr/share/man/man1/bash_builtins.1, but not bash.1


For some reason it doesn't work with a gzipped bash.1.
(A bug in man? It looks like it doesn't gunzip in this case.)

[...]


L8r,

Buzz.
-- 
  ) |  | ---/ ---/  Yes, this | This message consists of true | I do not
--  |  |   /    /   really is |   and false bits entirely.    | mail for
  ) |  |  /    /    a 72 by 4 +-------------------------------+ any1 but
--  \--| /--- /---  .sigfile. |   |perl -pe "s.u(z)\1.as."    | me. 4^re

--
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/

Re: Where is documentation on bash "wait"?

[Eric Blake]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

According to Bas van Gompel on 10/15/2005 2:46 PM:
> 
> Did /you/ try it?

Yes, as bash maintainer, I /did/ try it.  However, I didn't realize that
there was a typo in the upstream bash_builtins.1 manpage; I just supposed
that the text that was there was all it needed - thanks for catching that,
and I will forward it upstream.

> 
> It complains about not finding bash.1.

I haven't seen man complain - I wonder what your setup is that got a
complaint about the typo in the .so?

> Do you have a copy of bash.1 lying around somewhere?

cygwin man pages are purposefully compressed, so it should be bash.1.gz.

> 
> To get this to work as I think it is intended, I need to:
> 
> 
> For some reason it doesn't work with a gzipped bash.1.
> (A bug in man? It looks like it doesn't gunzip in this case.)

Yes, man could be improved to follow .so that have alternate extensions
(so that .so man1/bash.1 follows man1/bash.1.gz) - you may want to report
that to the upstream man list.

Meanwhile, I've corrected my local copy of bash to work in spite of the
cygwin gzipping; the next bash release will have the slick trick of inline
referencing to the bash builtins section, thanks to your patch pointing
that out to me.

- --
Life is short - so eat dessert first!

Eric Blake             ebb9@byu.net
volunteer cygwin bash maintainer
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDUXCZ84KuGfSFAYARAihEAJ9WEMJVS+MG74XExh+BS6fTAdI5xgCbB2QA
DE+hMj+DSE7yXs4Z/dqhrK0=
=d6U6
-----END PGP SIGNATURE-----

--
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/

Re: Where is documentation on bash "wait"?

[Buzz]

Op Sat, 15 Oct 2005 15:11:53 -0600 schreef Eric Blake
in <43517099.5080908@byu.net>:
[Ahhh]
:
:  According to Bas van Gompel on 10/15/2005 2:46 PM:
: >
: > Did /you/ try it?
:
:  Yes, as bash maintainer, I /did/ try it.  However, I didn't realize that
:  there was a typo in the upstream bash_builtins.1 manpage; I just supposed
:  that the text that was there was all it needed - thanks for catching that,
:  and I will forward it upstream.

Thank you for doing this.

: > It complains about not finding bash.1.
:
:  I haven't seen man complain - I wonder what your setup is that got a
:  complaint about the typo in the .so?

I'd think it's quite normal... (On several systems) I get:
| <standard input>:14: can't open `bash.1': No such file or directory
| BASH_BUILTINS(1)                                              BASH_BUILTINS(1)
| [...]


: > Do you have a copy of bash.1 lying around somewhere?
:
:  cygwin man pages are purposefully compressed, so it should be bash.1.gz.

I'm aware of that. I was WAGging you didn't get the error, having a
(possibly stale) bash.1 about somewhere.

: > To get this to work as I think it is intended, I need to:
[...]
: > For some reason it doesn't work with a gzipped bash.1.
: > (A bug in man? It looks like it doesn't gunzip in this case.)
:
:  Yes, man could be improved to follow .so that have alternate extensions
:  (so that .so man1/bash.1 follows man1/bash.1.gz) - you may want to report
:  that to the upstream man list.

That would be even better. I was just thinking about having:
man1/bash.1.gz in the bash_builtins page (just like man1/wait.1
contains: ``.so man1/bash_builtins.1.gz'')

I was hoping for ``our'' man-maintainer, being much more knowledgeable
about such issues, to be proactive...
...If (s)he isn't I'll look into finding the upstream ``man''-list.

:  Meanwhile, I've corrected my local copy of bash to work in spite of the
:  cygwin gzipping; the next bash release will have the slick trick of inline
:  referencing to the bash builtins section, thanks to your patch pointing
:  that out to me.

I'm curious how that's gonna work. My ``man'', after i've edited
bash_builtins.1(.gz) to mention man1/bash.1.gz me, says:

| man1/bash.1.gz:1: warning: can't find character with input code 6
| man1/bash.1.gz:1: warning: can't find character with input code 3
| man1/bash.1.gz:1: warning: can't find character with input code 12
| man1/bash.1.gz:1: warning: can't find character with input code 127
| man1/bash.1.gz:1: warning [p 1, 2.3i]: cannot adjust line
| man1/bash.1.gz:1: warning [p 1, 2.5i]: cannot adjust line
| groff: troff: Signal 11
| grotty:<standard input>:163:warning: no final `x stop' command
| BASH_BUILTINS(1)                                              BASH_BUILTINS(1)
| [...]


L8r,

Buzz.
-- 
  ) |  | ---/ ---/  Yes, this | This message consists of true | I do not
--  |  |   /    /   really is |   and false bits entirely.    | mail for
  ) |  |  /    /    a 72 by 4 +-------------------------------+ any1 but
--  \--| /--- /---  .sigfile. |   |perl -pe "s.u(z)\1.as."    | me. 4^re

--
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/

Re: Where is documentation on bash "wait"?

[Eric Blake]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

According to Buzz on 10/15/2005 9:46 PM:
> 
> : > Do you have a copy of bash.1 lying around somewhere?
> :
> :  cygwin man pages are purposefully compressed, so it should be bash.1.gz.
> 
> I'm aware of that. I was WAGging you didn't get the error, having a
> (possibly stale) bash.1 about somewhere.

Hmm, I do have /usr/local/man on my manpath, and it did indeed have
man1/bash.1, but I don't know if that affected things.

> I'm curious how that's gonna work. My ``man'', after i've edited
> bash_builtins.1(.gz) to mention man1/bash.1.gz me, says:
> 
> | man1/bash.1.gz:1: warning: can't find character with input code 6

It seems like man can cope with a .so that points to a .gz if that is the
only line, but has problems if the .so points to a .gz when embedded in
remaining text.  I'm not familiar enough with man to know what is going on
here, but it does seem like a man issue.  Meanwhile, I can distribute
bash.1 instead of bash.1.gz since that is all that works with the current
version of man.

- --
Life is short - so eat dessert first!

Eric Blake             ebb9@byu.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDUdCW84KuGfSFAYARApvbAKDRDVPBqr1rkGCOreqJmYRnyXHnRwCgvIq9
n1NazcT+c9tdi+e2kjsttxw=
=LRRL
-----END PGP SIGNATURE-----

--
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/

Re: Where is documentation on bash "wait"?

[Dr. Volker Zell]

>>>>> Buzz  writes:

    > I was hoping for ``our'' man-maintainer, being much more knowledgeable
    > about such issues, to be proactive...
    > ...If (s)he isn't I'll look into finding the upstream ``man''-list.

I will forward this issues to the upstream man maintainer.

Ciao
  Volker


--
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/

Re: Where is documentation on bash "wait"?

[Bas van Gompel]

Op Sun, 16 Oct 2005 12:11:00 +0200 schreef Dr. Volker Zell
in <82hdbh93gr.fsf@vzell-de.de.oracle.com>:
: >>>>> Buzz  writes:

:      > I was hoping for ``our'' man-maintainer, being much more knowledgeable
:      > about such issues, to be proactive...
:      > ...If (s)he isn't I'll look into finding the upstream ``man''-list.

:  I will forward this issues to the upstream man maintainer.

Great, thank you very much.


L8r,

Buzz.
-- 
  ) |  | ---/ ---/  Yes, this | This message consists of true | I do not
--  |  |   /    /   really is |   and false bits entirely.    | mail for
  ) |  |  /    /    a 72 by 4 +-------------------------------+ any1 but
--  \--| /--- /---  .sigfile. |   |perl -pe "s.u(z)\1.as."    | me. 4^re

--
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/

Re: Where is documentation on bash "wait"?

[Bas van Gompel]

Op Sat, 15 Oct 2005 22:01:26 -0600 schreef Eric Blake
in <4351D096.2050403@byu.net>:
:  According to Buzz on 10/15/2005 9:46 PM:
[(possibly stale) bash.1 about somewhere.]

:  Hmm, I do have /usr/local/man on my manpath, and it did indeed have
:  man1/bash.1, but I don't know if that affected things.

I don't think so, as long bash_builins.1.gz didn't have the dirname in
the .so.

: > I'm curious how that's gonna work. My ``man'', after i've edited
: > bash_builtins.1(.gz) to mention man1/bash.1.gz me, says:
: >
: > | man1/bash.1.gz:1: warning: can't find character with input code 6
:
:  It seems like man can cope with a .so that points to a .gz if that is the
:  only line, but has problems if the .so points to a .gz when embedded in
:  remaining text.

That appears to be an accurate description of this issue.

:   I'm not familiar enough with man to know what is going on
:  here, but it does seem like a man issue.

Indeed (same here).

:   Meanwhile, I can distribute
:  bash.1 instead of bash.1.gz since that is all that works with the current
:  version of man.

That does WJFFM. Thanks a lot for your efforts.

[...]


L8r,

Buzz.
-- 
  ) |  | ---/ ---/  Yes, this | This message consists of true | I do not
--  |  |   /    /   really is |   and false bits entirely.    | mail for
  ) |  |  /    /    a 72 by 4 +-------------------------------+ any1 but
--  \--| /--- /---  .sigfile. |   |perl -pe "s.u(z)\1.as."    | me. 4^re

--
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/

EventListening

[Peace Everyone]

I'm a noob with cygwin and have a question about EventListening, is 
there an interface or a class I can use? Or some add on libraries to 
include or do I have to write/implement my own EventListening Class?

Thank you for your answers
Peace Everyone

--
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/

Re: EventListening

[Larry Hall (Cygwin)]

Peace Everyone wrote:
> I'm a noob with cygwin and have a question about EventListening, is 
> there an interface or a class I can use? Or some add on libraries to 
> include or do I have to write/implement my own EventListening Class?

That's a good question.  I guess it depends on what kind of events you
want to listen for and where you believe the events are being generated.
You'll have to get much more specific about what you're trying to do
before someone on this list can offer you advice on this matter.

-- 
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/

Re: EventListening

[Peace Everyone]

Peace Everyone wrote:

>> I'm a noob with cygwin and have a question about EventListening, is 
>> there an interface or a class I can use? Or some add on libraries to 
>> include or do I have to write/implement my own EventListening Class?
>
>
> That's a good question.  I guess it depends on what kind of events you
> want to listen for and where you believe the events are being generated.
> You'll have to get much more specific about what you're trying to do
> before someone on this list can offer you advice on this matter.
>

Okey, It's like creating events in the (Console and Graphic)UI to inform 
the ENGINE which data is needed.

One alternative is the console based UI, u type one command and several 
options, from which u generate the adequate event to inform the ENGINE 
what data the GUI needs

The other alternative is the "real" graphic based UI, with all the cute 
little buttons and textfields in place of the console based UI....

I hope u now understand what I mean ;)

thanks for your answers
Peace Everyone

--
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/

Re: EventListening

[Larry Hall (Cygwin)]

Peace Everyone wrote:
> Peace Everyone wrote:
> 
>>> I'm a noob with cygwin and have a question about EventListening, is 
>>> there an interface or a class I can use? Or some add on libraries to 
>>> include or do I have to write/implement my own EventListening Class?
>>
>>
>>
>> That's a good question.  I guess it depends on what kind of events you
>> want to listen for and where you believe the events are being generated.
>> You'll have to get much more specific about what you're trying to do
>> before someone on this list can offer you advice on this matter.
>>
> 
> Okey, It's like creating events in the (Console and Graphic)UI to inform 
> the ENGINE which data is needed.
> 
> One alternative is the console based UI, u type one command and several 
> options, from which u generate the adequate event to inform the ENGINE 
> what data the GUI needs
> 
> The other alternative is the "real" graphic based UI, with all the cute 
> little buttons and textfields in place of the console based UI....
> 
> I hope u now understand what I mean ;)


I think I do.  And it is as I suspected.

You're asking about application functionality.  This isn't a Cygwin-specific
question so it is off-topic for this list.  I believe you're really looking
for a framework for application development.  You may want to have a look at
QT, wxWindows, GTK and friends and other such toolkits.  You'll find QT3 and
GTK packages as part of the Cygwin distribution but you should really see
each toolkit's web site for complete information on what's available and
how it can be used.


-- 
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/

Where is documentation on keyring?

[Siegfried Heintze]

I'm poking around in c:/cygwin/usr/share/doc/gnome-keyring-0.4.3 trying to
understand how to use this program called keyring.

Can I expect all Cygwin utilities to be already compiled and have a file
that contains a URL to the documentation? 

I could google for it, but I wanted to be assured that the copy I have from
Cygwin is the same program I find with google. (For example, active state
perl is quite different from Cygwin perl and Cygwin cvs is quite different
from cvsnt even though the name of the cvsnt client is still cvs.exe).

There is an INSTALL file, but do I need to install it after running the
Cygwin setup.exe? I could not find the source code directory anyway
(probably because I did not request to get the source).

Should I not be able to find a file in
c:/cygwin/usr/share/doc/gnome-keyring-0.4.3 that points me to some
directions on how to run the program that I presume is already compiled and
installed on my system?

Oh - I also tried info keyring and man keyring -- no luck there either.

OK, I give up: I'm googling for it: I'm getting something about palm
keyring. Hmmm... that is probably not it. What about
http://cvs.gnome.org/viewcvs/gnome-keyring-manager/ ? This does not tell me
much more than I already know.

I'm stuck. Can someone please point me to the documentation?

Thanks,
Siegfried


--
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/

Re: Where is documentation on keyring?

[René Berber]

Siegfried Heintze wrote:
[snip]
> I'm stuck. Can someone please point me to the documentation?

/usr/share/doc/Cygwin/gnome-keyring-0.4.5.README

-- 
René Berber


--
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/

Re: Where is documentation on keyring?

[Gerrit P. Haase]

Siegfried Heintze wrote:

> I'm stuck. Can someone please point me to the documentation?

There is not much more included as you can find in
/usr/share/doc/gnome-keyring-0.4.5/

Other Gnome applications hold their docs under /usr/share/gtk-doc where
it may be accessed by the Gnome help browser, however there is no
documentation included with this package.  I'll look if there is a
packaging problem.


Gerrit

--
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/

RE: Where is documentation on bash "wait"?

[Stephan Mueller]

Perhaps the problem is specific to your configuration -- man wait does
indeed point me to man bash, and the bash manpage does indeed cover wait
(I searched for SHELL BUILTIN COMMANDS based on early text in the page,
and then searched from the top of that section for wait -- worked like a
charm.

stephan();


-----Original Message-----
From: cygwin-owner@cygwin.com [mailto:cygwin-owner@cygwin.com] On Behalf
Of Bas van Gompel
Sent: Saturday, October 15, 2005 1:46 PM
To: cygwin@cygwin.com
Subject: Re: Where is documentation on bash "wait"?

Op Sat, 15 Oct 2005 17:45:06 +0000 schreef Eric Blake
in
<101520051745.25630.43514022000160940000641E22007614380A050E040D0C079D0A
@comcast.net>:
[What the...]
: > I tried info and man and could not find any information on wait. I
want to
: > (using bash)
:
:  Did you try 'man wait'?  That would have pointed you to 'man bash',
where

Did /you/ try it?

It complains about not finding bash.1.
Do you have a copy of bash.1 lying around somewhere?

To get this to work as I think it is intended, I need to:

1) gunzip /usr/share/man/man1/bash.1.gz and
   /usr/share/man/man1/bash_builtins.1.gz

2) patch /usr/share/man/man1/bash_builtins.1 like so:
--- /usr/share/man/man1/bash_builtins.1~	2005-10-15
21:27:52.000000000 +0200
+++ /usr/share/man/man1/bash_builtins.1	2005-10-15 21:44:33.770000000
+0200
@@ -10,6 +10,6 @@
 ulimit, umask, unalias, unset, wait \- bash built-in commands, see
\fBbash\fR(1)
 .SH BASH BUILTIN COMMANDS
 .nr zZ 1
-.so bash.1
+.so man1/bash.1
 .SH SEE ALSO
 bash(1), sh(1)

3) re-gzip /usr/share/man/man1/bash_builtins.1, but not bash.1


For some reason it doesn't work with a gzipped bash.1.
(A bug in man? It looks like it doesn't gunzip in this case.)

[...]


L8r,

Buzz.
-- 
  ) |  | ---/ ---/  Yes, this | This message consists of true | I do not
--  |  |   /    /   really is |   and false bits entirely.    | mail for
  ) |  |  /    /    a 72 by 4 +-------------------------------+ any1 but
--  \--| /--- /---  .sigfile. |   |perl -pe "s.u(z)\1.as."    | me. 4^re

--
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/


--
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/

Re: Where is documentation on bash "wait"?

[Andrew DeFaria]

Siegfried Heintze wrote:
> I tried info and man and could not find any information on wait. I 
> want to (using bash)
>
> (1) How do I wait for multiple children and wake up when the first one 
> dies?
>
> (2) Examine the status code of the dead child and possibly spawn a new 
> one?
>
> Where is the documentation on wait?
Wait's a builtin so the documentation is in the bash(1) man page.
-- 
I like kids, but I don't think I could eat a whole one.


--
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/

Where is documentation on bash "wait"?

[Siegfried Heintze]

I tried info and man and could not find any information on wait. I want to
(using bash)

(1) How do I wait for multiple children and wake up when the first one dies?

(2) Examine the status code of the dead child and possibly spawn a new one?

Where is the documentation on wait?

Thanks,
Siegfried


--
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/