On Wed, Dec 27, 2017 at 04:44:19PM +0100, David Runge wrote: > Do you have an alternative suggestion that is packageable? It's not entirely clear to me what you understand by 'packageable'... But what I mean is this: - If creating a 'realtime' group (and associated limits) is 'packageable', then so is creating an 'audio' group, it's just a different name. - So if either is done, I'd say the 'audio' option is the better one, because it doesn't interfere with realtime limits required by e.g. video or sdr, which may be different. So my preferred way is that groups should reflect classes of applications or activity (like audio, video,...), and not individual limits. In other words I don't really agree with your [3] which suggest using 'realtime' as the group name. Jack, or audio isn't the only application that may require realtime. What group name should the others use if Jack has already taken 'realtime' ? Something different which you may understand better than I do : I noticed after a recent update that the usb-modeswitch for my Huawei LTE stick didn't work anymore. I now have to do this manually in the script that starts my internet connection using wvdial. Can this be related to systemd-sysuser ? If so, what is the 'official' solution ? Ciao, -- FA A world of exhaustive, reliable metadata would be an utopia. It's also a pipe-dream, founded on self-delusion, nerd hubris and hysterically inflated market opportunities. (Cory Doctorow)
