3 ms·
A tamed process cannot even call fork(2) unless the TAME_PROC flag is passed, in which case I'd assume the child process would then inherit a copy from the pare
by brynet 11y ago
A tamed process cannot even call fork(2) unless the TAME_PROC flag is passed, in which case I'd assume the child process would then inherit a copy from the parent as part of a normal fork(2) operation. It can be later revoked by the child, but it may want to keep it for kill(2).
- philsnow 11y agoI'm `cvs get`ting as fast as I can to read the rest of sys_fork.c to sate my curiosity, but CVS incredibly slow. I'm spoiled by how git packs the repo.
- philsnow 11y agoturned out to be way faster just to grab http://mirrors.sonic.net/pub/OpenBSD/5.7/sys.tar.gz http://mirrors.sonic.net/pub/OpenBSD/5.7/sys.tar.gz , if anybody else wants to poke around and doesn't want to wait for cvs.
- glass- 11y agoYou can also view the source on the cvs web mirror: http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/ http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/
- stsp 11y agoSounds like you're doing something unnecessarily more complicated than this: $ time cvs -d anoncvs@anoncvs1.ca.openbsd.org:/cvs export -rHEAD src/sys/kern/kern_fork.c U src/sys/kern/kern_fork.c 0m2.73s real 0m0.06s user 0m0.04s system
- philsnow 11y agoYep, I was grabbing `src` instead of `src/sys/kern/kern_fork.c`. I've completely forgotten how to CVS, and I'm okay with that.
- stsp 11y agoPerhaps you'll like this, then: https://github.com/ustuehler/git-cvs https://github.com/ustuehler/git-cvs
- Pyxl101 11y agoWhat are the reasons why CVS is still in use?
- steveklabnik 11y ago1. it works 2. they're used to it 3. there isn't enough reason to change 4. lots of infrastructure would need rebuilt if they changed
- stsp 11y agoBecause we're already too busy with porting our code base to Ruby.