Fons Adriaensen <fons@xxxxxxxxxxxxxxx> writes: > 1. The whole idea of using daemons to provide > 'persistence' is fundamentally wrong. If I want > something to be persistent I will configure it, > and that configuration should be just **data** > in a file. Allowing daemons to take that role > is as stupid as accepting executable content > in mail. jackd autolanched by libjack is not less a daemon. It is detached. Only you miss the log file. I.e. if jack server is autostarted by launching jackd when jack application is started you get no feedback from jack server unless you start all applications from commandline so you can see the stdout. I thing this is fundamentally wrong. Also fundamentally wrong is to reinvent the wheel (dbus in this case). > 2. If autostart is to be useful it should at > least be possible to configure the server that > gets autostarted. This seems to be impossible. > The obvious place to put such a configuration, > ~/.jackdrc, is completely ignored by jackd, > despite that file's name. jackd parameters are read by libjack when jackd is launched. So do you want want jackd to read settings or not? Are you opposed just to jackd writting the settings file not to reading it? -- Nedko Arnaudov <GnuPG KeyID: DE1716B0>
Attachment:
pgpQ42yAtY2up.pgp
Description: PGP signature
_______________________________________________ Linux-audio-user mailing list Linux-audio-user@xxxxxxxxxxxxxxxxxxxx http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user
