Fons Adriaensen writes:
> 1. The whole idea of using daemons to provide
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
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?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.7 (GNU/Linux)
-----END PGP SIGNATURE-----