Hi, Now that I am trying to run jack1 (instead of jack2), I see that my clients get zombified very fast. (Typically even before doing anything useful.) The JACK wiki points this out as a difference (that jack2 is more tolerant), but it also says that this behaviour is configurable. Well, I tried to, but without success. Jack messages: ====================== 15:33:43.894 /usr/bin/jackd --nozombies -dalsa -dhw:1 -r44100 -p128 -n2 -Xraw jackd 0.121.2 Copyright 2001-2009 Paul Davis, Stephane Letz, Jack O'Quinn, Torben Hohn and others. jackd comes with ABSOLUTELY NO WARRANTY This is free software, and you are welcome to redistribute it under certain conditions; see the file COPYING for details JACK compiled with System V SHM support. loading driver .. apparent rate = 44100 creating alsa driver ... hw:1|hw:1|128|2|44100|0|0|nomon|swmeter|-|32bit control device hw:1 configuring for 44100Hz, period = 128 frames (2.9 ms), buffer = 2 periods ALSA: final selected sample format for capture: 24bit little-endian ALSA: use 2 periods for capture 15:33:43.923 JACK was started with PID=19792. ALSA: final selected sample format for playback: 24bit little-endian ALSA: use 2 periods for playback scan: added port hw:1,0,0 in-hw-1-0-0-AudioBox-USB-MIDI-1 scan: added port hw:1,0,0 out-hw-1-0-0-AudioBox-USB-MIDI-1 scan: opened port hw:1,0,0 in-hw-1-0-0-AudioBox-USB-MIDI-1 scan: opened port hw:1,0,0 out-hw-1-0-0-AudioBox-USB-MIDI-1 15:33:45.955 JACK connection change. 15:33:45.958 Server configuration saved to "/home/pianist/.jackdrc". 15:33:45.959 Statistics reset. 15:33:45.974 Client activated. 15:33:45.976 Buffer size change (128). 15:33:50.310 JACK connection graph change. 15:33:50.337 ALSA connection graph change. 15:33:50.379 JACK connection change. 15:33:50.395 JACK connection graph change. subgraph starting at Kontakt 5 timed out (subgraph_wait_fd=17, status = 0, state = Running, pollret = 0 revents = 0x0) **** alsa_pcm: xrun of at least 0.109 msecs 15:33:54.967 JACK connection graph change. bad status (-1) for client Kontakt 5 handling event (type = 5) 15:33:54.974 XRUN callback (1). 15:33:55.013 JACK connection change. ====================== As you can see, I started jackd with the --nozombies parameter. Meanwhile, wine/wineasio/kontakt says: ======================= jack_client_thread zombified - exiting from JACK ======================== * * * Of course, ideally, I would not get xruns; I intend to tune my system (wine-rt, etc), but still, how do I configure jack1 not to zombify the problematic clients? (The exact version of jack1 is svn revision 4538, which is the latest version in Debian.) Thank you for your help: Kristof