00:48:40 <tm512> I'm trying to get virtual_oss set up as a loopback device so that I can record system audio, using the command: virtual_oss -S -C 2 -c 2 -r 48000 -b 16 -s 1024 -f /dev/dsp3 -l ldsp
00:48:57 <tm512> but recording from /dev/ldsp then gives nothing but silence
01:08:29 <tm512> maybe I'm not understanding what -f does. I thought it meant that the loopback device would route the sound being played back through /dev/dsp3
01:10:23 <tm512> is it actually just forwarding the audio from the loopback to the main pcm device, while providing that for recording on the loopback?
01:11:39 <tm512> -f /dev/dsp3 seems equivalent to -P /dev/dsp3 -R /dev/dsp3, so what exactly is happening with dsp3's recording stream?
01:21:33 <ivy> ant-x: you can pass (a copy of) an open fd to another process using sendmsg()
01:21:43 <ivy> over a Unix domain socket
01:22:36 <ivy> and yes, httpd would be the client, blocklistd is the server
01:24:36 <ant-x> And there should be an interface pre-determined between the client and server, right?
01:24:52 <ant-x> re: httpd as a client -- understood that much from <https://www.obsessivecomputingdisorder.com/posts/blacklistd-guide/> .
01:25:59 <ivy> if you mean a protocol, yes, all IPC (or RPC) requires both sides agree on a protocol, or nothing could be communicated