Le 18/03/2013 14:24, Michael Van Canneyt a écrit :
On Mon, 18 Mar 2013, Antonio Fortuny wrote:
Hi Folks.
Where do I use oldlinux from ?
Don't use oldlinux.
I'd like to use the Fork function but Lazarus tells me
IpDaemon.lpr(0,0) Fatal: Can not find unit oldlinux used by IpDaemon.
whereas
On Mon, 18 Mar 2013, Antonio Fortuny wrote:
Hi Folks.
Where do I use oldlinux from ?
Don't use oldlinux.
I'd like to use the Fork function but Lazarus tells me
IpDaemon.lpr(0,0) Fatal: Can not find unit oldlinux used by IpDaemon.
whereas the source unit is in /usr/share/focsrc/linux but n
Hi Folks.
Where do I use oldlinux from ?
I'd like to use the Fork function but Lazarus tells me
IpDaemon.lpr(0,0) Fatal: Can not find unit oldlinux used by IpDaemon.
whereas the source unit is in /usr/share/focsrc/linux but no .O and .ppu
neither
Antonio
--
> On dinsdag, sep 16, 2003, at 15:34 Europe/Brussels, Marco van de Voort
> wrote:
>
> >> This has nothing to do with unix <-> BeOS. For example, Solaris is
> >> definitely Unix and also uses the concept of light weight processes.
> >
> > Light weight processes are a Unix feature.
>
> Not all Uni
On dinsdag, sep 16, 2003, at 15:34 Europe/Brussels, Marco van de Voort
wrote:
This has nothing to do with unix <-> BeOS. For example, Solaris is
definitely Unix and also uses the concept of light weight processes.
Light weight processes are a Unix feature.
Not all Unixes have light weight process
> On dinsdag, sep 16, 2003, at 14:55 Europe/Brussels, Matt Emson wrote:
>
> > Got you. So the correct term would be 'multiprocess'. I always forget
> > that
> > UNIX considers processes to be seperate to threads. BeOS does things
> > slightly differently. We have the notion of 'teams'. A thread b
On dinsdag, sep 16, 2003, at 14:55 Europe/Brussels, Matt Emson wrote:
Got you. So the correct term would be 'multiprocess'. I always forget
that
UNIX considers processes to be seperate to threads. BeOS does things
slightly differently. We have the notion of 'teams'. A thread belongs
to a
'team'.
> Multithreaded applications share the same memory space.
> Forked applications are truly separate applications, they have a different
memory
> space.
Got you. So the correct term would be 'multiprocess'. I always forget that
UNIX considers processes to be seperate to threads. BeOS does things
sli
On Tue, 16 Sep 2003, Matt Emson wrote:
> Michael, forgive me if I am wrong - I am not a Unix buff - but I was under
> the impression that forking was a method for creating multithreaded unix
> apps?!? Everytime you fork() you end up with two seperate processes running
> concurrently. You differe
Michael, forgive me if I am wrong - I am not a Unix buff - but I was under
the impression that forking was a method for creating multithreaded unix
apps?!? Everytime you fork() you end up with two seperate processes running
concurrently. You differentiate between them by chacking the result given b
On Tue, 16 Sep 2003, [iso-8859-2] Balázs Csaba wrote:
> I want to use fork to make multithread application for sockets and I would
> like to fork it to run in dameon mode.
Multithread is not possible with Fork()
> Can I fork the forked program? With call fork I get 0 in result in child.
This
Title: Üzenet
I want to use fork
to make multithread application for sockets and I would like to fork it to run
in dameon mode.
Can I fork the
forked program? With call fork I get 0 in result in
child.
#Tsch : Balázs Csaba
12 matches
Mail list logo
