16 Dec
2006
16 Dec
'06
6:56 a.m.
Hi,
I am adding a Daemon mode to jackEQ and have most of the code in place now.
I am stuck at the point where the daemon starts up and keeps going.
Essentially I need the daemon mode equivalent of gtk_main() that keeps
ticking over until the app is told to stop or otherwise shutdown.
I have not threaded the app at this point so hopefully there is a very
simple solution.
Any thoughts on this are appreciated.
Cheers.
--
Patrick Shirkey - Boost Hardware Ltd.
Http://www.boosthardware.com
Http://lau.linuxaudio.org - The Linux Audio Users guide
========================================
"Anything your mind can see you can manifest physically, then it will
become reality" - Macka B
16 Dec
16 Dec
7:14 a.m.
On Sat, 2006-12-16 at 17:56 +0700, Patrick Shirkey wrote:
Hi,
I am adding a Daemon mode to jackEQ and have most of the code in place now.
I am stuck at the point where the daemon starts up and keeps going.
Essentially I need the daemon mode equivalent of gtk_main() that keeps
ticking over until the app is told to stop or otherwise shutdown.
I have not threaded the app at this point so hopefully there is a very
simple solution.
So the only thread that needs to do anything is the JACK thread? In that
case you can just add something like
... init code ...
bool run = true;
while (run) sleep(10000);
... cleanup code ...
in the main thread, after setting up JACK. If you want to be nice you
can add signal handlers for SIGHUP and SIGINT that set 'run' to false.
--
Lars Luthman - please encrypt any email sent to me if possible
PGP key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x04C77E2E
Fingerprint: FCA7 C790 19B9 322D EB7A E1B3 4371 4650 04C7 7E2E
7:18 a.m.
On Sat, 2006-12-16 at 12:14 +0100, Lars Luthman wrote:
On Sat, 2006-12-16 at 17:56 +0700, Patrick Shirkey
wrote:
Ehm, and in that case you better change the sleep time to 1 or use
usleep() and specify microseconds instead. You wouldn't want to wait for
hours after trying to stop the program.
Or is sleep() interrupted by signals even if there are signal handlers
for them?
--
Lars Luthman - please encrypt any email sent to me if possible
PGP key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x04C77E2E
Fingerprint: FCA7 C790 19B9 322D EB7A E1B3 4371 4650 04C7 7E2E
Hi,
I am adding a Daemon mode to jackEQ and have most of the code in place now.
I am stuck at the point where the daemon starts up and keeps going.
Essentially I need the daemon mode equivalent of gtk_main() that keeps
ticking over until the app is told to stop or otherwise shutdown.
I have not threaded the app at this point so hopefully there is a very
simple solution.
So the only thread that needs to do anything is the JACK thread? In that
case you can just add something like
... init code ...
bool run = true;
while (run) sleep(10000);
... cleanup code ...
in the main thread, after setting up JACK. If you want to be nice you
can add signal handlers for SIGHUP and SIGINT that set 'run' to false.
9:49 a.m.
Lars Luthman wrote:
On Sat, 2006-12-16 at 12:14 +0100, Lars Luthman
wrote:
Thanks for the pointer Lars.
However I'm using c so this code doesn't work. I have modified it like so:
int run = TRUE;
while (run)
sleep(10000);
but that just gives a segv. It runs for about a second then gives up.
I'm also looking at the code for jackd and have spotted this function:
sigwait (&signals, &sig);
so I added some new bits and pieces like so:
static sigset_t signals;
int main(int argc, char *argv[])
{
int run;
int sig;
sigset_t allsignals;
sigemptyset (&signals);
sigaddset(&signals, SIGHUP);
sigaddset(&signals, SIGINT);
sigaddset(&signals, SIGQUIT);
sigaddset(&signals, SIGPIPE);
sigaddset(&signals, SIGTERM);
sigfillset (&allsignals);
process_init();
run = TRUE;
while (run)
sigwait (&signals, &sig);
return 0;
}
but that also returns segv at sigwait(). If I put a printf after sigwait
it doesn't print. Before is ok.
I'm not sure how to proceed from here.
Cheers.
--
Patrick Shirkey - Boost Hardware Ltd.
Http://www.boosthardware.com
Http://lau.linuxaudio.org - The Linux Audio Users guide
========================================
"Anything your mind can see you can manifest physically, then it will
become reality" - Macka B
On Sat, 2006-12-16 at 17:56 +0700, Patrick
Shirkey wrote:
Ehm, and in that case you better change the sleep time to 1 or use
usleep() and specify microseconds instead. You wouldn't want to wait for
hours after trying to stop the program.
Or is sleep() interrupted by signals even if there are signal handlers
for them?
Hi,
I am adding a Daemon mode to jackEQ and have most of the code in place now.
I am stuck at the point where the daemon starts up and keeps going.
Essentially I need the daemon mode equivalent of gtk_main() that keeps
ticking over until the app is told to stop or otherwise shutdown.
I have not threaded the app at this point so hopefully there is a very
simple solution.
So the only thread that needs to do anything is the JACK thread?
In that
case you can just add something like
... init code ...
bool run = true;
while (run) sleep(10000);
... cleanup code ...
in the main thread, after setting up JACK. If you want to be nice you
can add signal handlers for SIGHUP and SIGINT that set 'run' to false.
10 a.m.
On Sat, 2006-12-16 at 20:48 +0700, Patrick Shirkey wrote:
Thanks for the pointer Lars.
However I'm using c so this code doesn't work. I have modified it like so:
int run = TRUE;
while (run)
sleep(10000);
but that just gives a segv. It runs for about a second then gives up.
I'm also looking at the code for jackd and have spotted this function:
sigwait (&signals, &sig);
so I added some new bits and pieces like so:
static sigset_t signals;
int main(int argc, char *argv[])
{
int run;
int sig;
sigset_t allsignals;
sigemptyset (&signals);
sigaddset(&signals, SIGHUP);
sigaddset(&signals, SIGINT);
sigaddset(&signals, SIGQUIT);
sigaddset(&signals, SIGPIPE);
sigaddset(&signals, SIGTERM);
sigfillset (&allsignals);
process_init();
run = TRUE;
while (run)
sigwait (&signals, &sig);
return 0;
}
but that also returns segv at sigwait(). If I put a printf after sigwait
it doesn't print. Before is ok.
That code compiles and runs fine here (after adding #include <signal.h>
and commenting out process_init()). The problem is probably somewhere
else in your code. I'd try running it in valgrind to spot any memory
bugs (with JACK in softmode and using the dummy driver).
--
Lars Luthman - please encrypt any email sent to me if possible
PGP key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x04C77E2E
Fingerprint: FCA7 C790 19B9 322D EB7A E1B3 4371 4650 04C7 7E2E
10:05 a.m.
Hi list
Patrick Shirkey a écrit :
int run = TRUE;
while (run)
sleep(10000);
The easiest one for this construct is probably pause(2) instead of
sleep() with some random value, but is marked deprecated in favor of
sigsuspend(2).
while (run)
sigwait (&signals, &sig);
From manpages, sigwait(3) seems to disable signal handlers, whereas
sigsuspend(2) lets them run, use what you need though.
sigwait is threads related.
but that also returns segv at sigwait(). If I put a
printf after sigwait
it doesn't print. Before is ok.
You must have some data still referenced after cleanup, aren't there
some callback systems you forgot to disable somewhere ?
Cheers
--
Nipo <nipo(a)ssji.net>
17 Dec
17 Dec
10:41 a.m.
Nicolas Pouillon wrote:
You must have some data still referenced after cleanup, aren't there
some callback systems you forgot to disable somewhere ?
Yep, was missing a global. Been a while since I worked on this code...
Thanks for the help everyone.
Cheers.
--
Patrick Shirkey - Boost Hardware Ltd.
Http://www.boosthardware.com
Http://lau.linuxaudio.org - The Linux Audio Users guide
========================================
"Anything your mind can see you can manifest physically, then it will
become reality" - Macka B
16 Dec
16 Dec
9:40 a.m.
On Sat, 16 Dec 2006 17:56:23 +0700
Patrick Shirkey <pshirkey(a)boosthardware.com> wrote:
Hi,
I am adding a Daemon mode to jackEQ and have most of the code in
place now.
I am stuck at the point where the daemon starts up and keeps going.
Essentially I need the daemon mode equivalent of gtk_main() that
keeps ticking over until the app is told to stop or otherwise
shutdown.
I think you could use a Glib main loop :
http://developer.gnome.org/doc/API/2.0/glib/glib-The-Main-Event-Loop.html
HTH
--
David
6541
days inactive
6542
days old
linux-audio-dev@lists.linuxaudio.org
7 comments
4 participants
participants (4)
-
David -
Lars Luthman -
Nicolas Pouillon -
Patrick Shirkey