The service starts and tries to connect but the other
system is up far enough yet to receive connections so it
just fails. The only solution so far is to restart the
service manually later, which is
On 02/12/2020 16:09, Richard Shaw
wrote:
Nope,
it's an external networked device. They always "boot up" at the
same time, but the computer which runs the service boots up faster
than the device I need to connect to.
What difference does that make - wh
On 22/11/2020 16:12, Solomon Peachy wrote:
Showcase, sure, but there's a long, long, long tail of barely-maintained
software in use that won't get updated to use PW natively anytime soon.
If ever.
FFS, most of the software I use today doesn't even use PA directly; it
uses ALSA, which gets route
My reply got a lot longer than I originally planned to write.
TL;DR - Having the software working is just the tip of the iceberg. The
other 9/10ths needs to be a concentrated effort on documentation and
driving adoption of the new API and not relying on the compatibility
layer. Otherwise it wi
On 18/11/2020 13:28, Luca BRUNO wrote:
A dynamic default is being tackled directly at kernel level.
There is a currently in-progress patch on linux-fsdevel for this, first
revision is at
https://patchwork.kernel.org/project/linux-fsdevel/patch/20201026204418.23197-1-long...@redhat.com/.
For furth
. I've not rebooted my machine
overnight and netbeans is now up to 13,000 watches and tracker-miner
upto 4,500. So in less than 24 hours I have exceeded 16K watches.
Perhaps an new default value in the region of 32K - 64K would be more
appropriate?
