![]() |
|
FreeBSD Ports and Packages Installation and upgrading of ports and packages on FreeBSD. |
![]() |
|
Thread Tools | Display Modes |
|
|||
![]()
Hi!
By reading sndiod(8) (and OpenBSD FAQ), starting it as: # sndiod -L- is enough to permit remote connections, but that's not true at FreeBSD. If I use -L flag, I get two problems at once: remote machines are unable to use snd@myhostname/0 and rsnd@myhostname/0 devices and host machine is unable to use snd/0 and rsnd/0 devices, my host machine is muted! (not globally, only applications which use sndio are muted, applications using other backends are not muted)
__________________
mazocomp$ uname -a OpenBSD mazocomp.lan 6.3 GENERIC.MP#47 amd64 mazocomp$ |
|
|||
![]()
Issue closed. Starting sndiod(8) with flags requires to specify devices explicitly, in my case:
# sndiod -f rsnd/1 -L- But in OpenBSD case (from FAQ), `# rcctl set sndiod flags -L-` will set -L- flag without specifying devices... Damn, documentation is not clear.
__________________
mazocomp$ uname -a OpenBSD mazocomp.lan 6.3 GENERIC.MP#47 amd64 mazocomp$ |
![]() |
Tags |
remote, sndiod |
Thread Tools | |
Display Modes | |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
sndio instead of jackd? | Funkygoby | OpenBSD General | 4 | 19th August 2015 11:06 AM |
sndio and USB headphones | tehsean | OpenBSD General | 3 | 18th February 2013 04:59 AM |
ssh X while host is using X server .. possible ? | daemonfowl | OpenBSD Security | 3 | 25th July 2012 03:07 AM |
ssh/rdesktop into host behind NAT | JMJ_coder | General software and network | 18 | 13th January 2009 08:19 PM |
Updating FreeBSD Jails after rebuilding world on host | anomie | Guides | 0 | 10th September 2008 03:23 AM |