I have a helpful "kick this out of HNQ" flag on physics, but 1. that doesn't mean the mod complied, 2. it was handled 2 days after the flag, so it's possible that it had already expired on its own by then.
Ahh, a kick would create an event: "When moderators kick a post off the HNQ list there will be a delay of up to fifteen minutes or so as the list is cached but the question will be removed the next time it runs. In addition, an event will be logged in the post timeline and edit history that indicates when it was removed and by whom. "
@JeffSchaller I can try, although it's still unclear whether the linked questions are exact dupes (because the whole UPnP thing might mean that one of their output devices is not actually an output device)
I have some questions, and appreciate if someone could enlighten me
Does anyone know some books or other references that explain how to understand the order between request (or releases) of different mutexes in a synchronized multiprocess or multithread program?
Thanks in advance!
p.s. Is it just me that it is very hard to reason about a program with multiple mutexes
Tim, you've been told (as have others) that dumping questions in /dev/chat from other sites is not kosher. Willing visitors to Software Engineering will see the questions there.
I have a system I'm managing (running RHEL 8) that has multiple users in our small office, who log into it in various ways -- locally at the console, remotely via SSH and NoMachine Workstation. When I do updates that include a new kernel, or for some other reason I need to reboot the machine, I'd...
@JeffSchaller hmm... will that work well with LDAP users? Can we always assume that they''ll have a UID >1000? Also, that rules out root, of course,but the OP might be OK with it
Well, except I can't see anything in the settings, as I mentioned earlier. But Krita has a config menu where you can play around and see debug info (x, y coordinates and pressure percentages)
@AndrasDeak Learning about computer stuff is worthwhile in general. But one has to be selective. To be more specific, learning about hardware device drivers is rarely worthwhile, because that knowledge is very specific and particular, and not something that is more generally useful as part of a broader corpus of knowledge.
Some other things are worth learning about, because then you understand them better. And computer stuff is usually easy to learn, because it's simple and predictable, though humans are good at making it all much more complicated than it needs to be.
Also just a p would do the same, maybe? I read these in the manpage once but whenever I tried to use something like it (without looking it up) it never works (read: I misremember)
@terdon "Of course, you could adjust the ps columns to taste, perhaps to add the translated username and process start time (ps -eo pid,uid,user,start,args)" ...
my assumption (!) is that they're looking for evidence of interactive user processes. Just seeing a username isn't as informative for a reboot as "4-day old idle bash process"
@FaheemMitha I found another book on C++ that seems excellent and well suited for experienced programmers; it's called "C++ Crash Course" and it's from 2019.
Very readable, but based on this comment (the reason it's not on the stackoverflow list of C++ books) I probably won't continue. Reading easily the wrong info isn't much help.
Still might look at it for syntax questions, it seems good for that. So yeah, as a reference, maybe.