384 karma · joined September 14, 2014
My feeling is that nobody uses signal driven I/O because signal handling is error prone and complicated. In fact, a very common pattern is to only set a flag in the signal handler, which is checked at defined points in the main program... not completely dissimilar from doing non-blocking calls at defined points in the main program.
With only the first one you couldn't modify values of a vector using nice [] syntax. With only the second one you couldn't use the same nice [] syntax on const vectors. So you need both. The implementation can be identical, but the method signature is different. You end up with such duplicate functions all the time for accessor methods.
Linux allows you to configure the limit at /proc/sys/vm/mmap_min_addr.
The problems mentioned in that article result from software that thinks this limit is set in stone. Such software encodes data in these upper bits, and then later masks it away before accessing the pointer.
This is only memory safety, not using other optimizations related to undefined behavior will add a bunch more overhead.
1: https://windsorsradweg.files.wordpress.com/2012/01/cropped-d...
if ! ansible-playbook ... ; then
echo -e "\e[1;31m""Error when executing ansible!""\e[0m"
exit 1
fi
But generally when I need to work around errexit, I tend to add something like " || true" or " || xyz_failed=true" to the end of the command line instead of turning it off and on again.Even if they claim something more specific than literally any job at all, they'll probably count anyone doing something related to IT (if only for a week).
I've also read about boot camps hiring their alumni as teachers/tutors for a bit if they can't find a job. I always assumed that's mostly to be able to count those people as successfully placed.
(Note: I have no idea how exactly mongo implements deletion.)
It's also an incentive to avoid going to the doctor unless you really need to. Something that I'm not sure helps with healthcare costs in the long run.
The default ACLs make sure that any newly created files can be accessed by both users.
setfacl -m u:NON-OWNER:rwX,d:u:NON-ONWER:rwX,d:u:OWNER:rwX DIR
(Allows NON-OWNER to read, write, execute if already executable for anyone to that directory, and allows NON-OWNER and OWNER to do the same for newly created files.)> All it relies on is the assumption that the architecture uses a call stack to implement function frames.
Does this mean it will treat live objects as dead when the only reference is stored in a register?
* playing audio from/to another Bluetooth device (with bluez)
* playing audio on a PulseAudio server running somewhere on the network
* transparent encoding of audio output as DTS (for surround support over SPDIF)
I also seem to remember plain ALSA having trouble with multiple applications playing sound at the same time, which is just pathetic.
I'm sure some of these could in theory be built on top of ALSA, but fact is that today's Linux distributions use PulseAudio, and for me it always worked well.