> std.process is woefully unmaintained. Lars K is developing a new
version,
> and I am really really late getting a windows version to him so it
can be
> included in phobos. It includes simple methods to create a sub-
process,
> which should solve your issue.
> I think this shall be my next "Spar
On Thu, 02 Jun 2011 11:43:50 -0400, Guillermo Estrada
wrote:
Hi, been developing in D a lot but first time in news groups, I
thought this might be the place.
I'm trying to make a fork bomb in D (of course no fork cause target
its windows platform) but anyway. I did one a while ago using D1 a
> So, if you can't find something that really seems like it should
> be in Phobos, open an enhancement request on it on bugzilla:
> d.puremagic.com/issues/
> Jonathan M Davis
As expected spawnvp() creates child process that exit with the father,
just as system(). exec*() replaces the parent proces
== Quote from Jonathan M Davis (jmdavisp...@gmx.com)'s article
> On 2011-06-02 09:14, Guillermo Estrada wrote:
> > == Quote from Ali Çehreli (acehr...@yahoo.com)'s article
> >
> > > On 06/02/2011 08:51 AM, Guillermo Estrada wrote:
> > > >> The exec* family of functions cause the new app to replace
On 2011-06-02 09:14, Guillermo Estrada wrote:
> == Quote from Ali Çehreli (acehr...@yahoo.com)'s article
>
> > On 06/02/2011 08:51 AM, Guillermo Estrada wrote:
> > >> The exec* family of functions cause the new app to replace the
> > >
> > > current process. So after the execv, the loop doesn't
On 2011-06-02 08:59, Ali Çehreli wrote:
> On 06/02/2011 08:51 AM, Guillermo Estrada wrote:
> >> The exec* family of functions cause the new app to replace the
> >
> > current process. So after the execv, the loop doesn't exist.
> >
> > Any way to spawn the process without killing himself?
>
> W
== Quote from Ali Çehreli (acehr...@yahoo.com)'s article
> On 06/02/2011 08:51 AM, Guillermo Estrada wrote:
> >> The exec* family of functions cause the new app to replace the
> > current process. So after the execv, the loop doesn't exist.
> >
> > Any way to spawn the process without killing hims
On 06/02/2011 08:51 AM, Guillermo Estrada wrote:
The exec* family of functions cause the new app to replace the
current process. So after the execv, the loop doesn't exist.
Any way to spawn the process without killing himself?
Would std.process.system or std.process.shell work?
Ali
> The exec* family of functions cause the new app to replace the
current process. So after the execv, the loop doesn't exist.
Any way to spawn the process without killing himself?
On 6/2/2011 8:43 AM, Guillermo Estrada wrote:
> Hi, been developing in D a lot but first time in news groups, I
> thought this might be the place.
>
> I'm trying to make a fork bomb in D (of course no fork cause target
> its windows platform) but anyway. I did one a while ago using D1 and
> Tango
Hi, been developing in D a lot but first time in news groups, I
thought this might be the place.
I'm trying to make a fork bomb in D (of course no fork cause target
its windows platform) but anyway. I did one a while ago using D1 and
Tango and all ran perfectly, I'm trying to migrate my whole dev
11 matches
Mail list logo
