On Mon, Jul 7, 2008 at 11:03 PM, G Hasse <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I have a small demo app. This works on FreeBSD but I can't
> get to work on Linux. I know that in Linux setsid will fail
> if the child has the same session_id as the parent. So on
> Linux you must fork twice. But it
Hi,
2008/7/7 G Hasse <[EMAIL PROTECTED]>:
> I have a small demo app. This works on FreeBSD but I can't
> get to work on Linux.
I tried your code on my Ubuntu machine and it works fine. I had to add:
// needed for fork()
#include
// needed for umask()
#include
#include
near the top, but that
On Mon, Jul 07, 2008 at 10:58:36PM -0400, James Scott Jr wrote:
> G,
>
> The basic design decision to use fork() as a way to do work in the
> background flawed. fork()ing is not practical for gtk program. While
> fork() has been a valid option for many non-gui programs in the absence
> of thread
On Tue, Jul 08, 2008 at 10:17:53AM +0200, Gabriele Greco wrote:
> On Mon, Jul 7, 2008 at 11:03 PM, G Hasse <[EMAIL PROTECTED]> wrote:
>
> > Hello,
> >
> > I have a small demo app. This works on FreeBSD but I can't
> > get to work on Linux. I know that in Linux setsid will fail
> > if the child has
G Hasse wrote:
> But I realy NEED to create a longlived process (running for a week or
> month) and be able to quit the GUI whenever I like. The glib is
> just a wrapper - and i don't se the solution...
>
> I realy WANT to lose contact with the child process. And there
> is to mutch data from the
Dave Howorth schrieb:
> G Hasse wrote:
>> But I realy NEED to create a longlived process (running for a week or
>> month)
[snip]
> IMHO, in this circumstance, you still shouldn't have the GUI start the
> long-lived process. You'll probably want some other mechanism to
> [re]start the process in the
Hi,
I want to execute an external program using g_spawn_async_with_pipes.
This program outputs ASCII to stdout, which I want to catch using
g_child_watch_add.
This works fine, but if the data exceeds a certain amount of data
apparently the pipe gets 'full', causing the ext. program to wait with
out
G,
I've seen most of the other responses, and better understand what you
are trying to do. And like others -- fork() is not recommended.
I had similar problem and resolved it in this codeset.
http://gfhcm.sourceforge.net -- a monitor for the [EMAIL PROTECTED] project
First, like you I needed
On Tue, 2008-07-08 at 23:23 +0200, G Hasse wrote:
> On Tue, Jul 08, 2008 at 01:52:00PM -0400, James Scott Jr wrote:
> > G,
> >
> > I've seen most of the other responses, and better understand what you
> > are trying to do. And like others -- fork() is not recommended.
>
> I can't belive this..
