2 ms·
I mean, if they really only work when not running at the same time, they do something really really shady, so I would not really use them on production systems
by kaba0 6y ago
I mean, if they really only work when not running at the same time, they do something really really shady, so I would not really use them on production systems even in serial unless I figure out what exactly is wrong with them. It may very well be the case that they are buggy even in serial, it just not as obvious/doesn’t happen that often that way.
Nonetheless, parallelism is an additional feature (in my opinion, greatly appreciated), but it can be turned off. Additional functionality is rarely bad over not having it.
- scbrg 6y ago> if they really only work when not running at the same time, they do something really really shady They configured firewall rules using iptables. I'm not sure I consider configuring firewall rules at startup using an init script "really really shady". Turns out (quite unsurprisingly) that you can't run multiple instances of the iptables command simultaneously. I don't really want to get into the whole debate about whether parallelizing startup scripts is better or not. I'm not saying it's not, but that's beside the point. The point was that parallelizing startup scripts leads to a set of problems that didn't exist before. It's annoying to see people argue that those problems don't exist. It's like arguing that the problem of flat tyres aren't more common for people driving cars than they are for people riding horses. It's utter nonsense, no matter how many other advantages cars may have.
- hnarn 6y agoWho is arguing that these problems don't exist?