Tomi Ollila writes:
> From: Tomi Ollila
>
> When shell executes background process using '&' the scheduling of
> that new process is arbitrary. It could be that smtp-dummy doesn't
> get execution time to listen() it's server socket until some other
> process attempts to connect() to it. The
Tomi Ollila writes:
> From: Tomi Ollila
>
> When shell executes background process using '&' the scheduling of
> that new process is arbitrary. It could be that smtp-dummy doesn't
> get execution time to listen() it's server socket until some other
> process attempts to connect() to it. The
Tomi Ollila tomi.oll...@iki.fi writes:
From: Tomi Ollila t...@iki.fi
When shell executes background process using '' the scheduling of
that new process is arbitrary. It could be that smtp-dummy doesn't
get execution time to listen() it's server socket until some other
process attempts to
Tomi Ollila tomi.oll...@iki.fi writes:
From: Tomi Ollila t...@iki.fi
When shell executes background process using '' the scheduling of
that new process is arbitrary. It could be that smtp-dummy doesn't
get execution time to listen() it's server socket until some other
process attempts to
Hi Tomi,
On Tue, Sep 18 2012, Tomi Ollila wrote:
> From: Tomi Ollila
>
> When shell executes background process using '&' the scheduling of
> that new process is arbitrary. It could be that smtp-dummy doesn't
> get execution time to listen() it's server socket until some other
> process attempts
From: Tomi Ollila
When shell executes background process using '&' the scheduling of
that new process is arbitrary. It could be that smtp-dummy doesn't
get execution time to listen() it's server socket until some other
process attempts to connect() to it. The --background option in