lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Mon, 20 Nov 2006 21:38:39 +0100 (MET) From: Jan Engelhardt <jengelh@...ux01.gwdg.de> To: Simon Richter <Simon.Richter@...yros.de> cc: linux-kernel@...r.kernel.org Subject: Re: RFC: implement daemon() in the kernel On Nov 20 2006 14:20, Simon Richter wrote: > > - a reverse vfork() > >The child process is created and suspended, the parent continues to run >until it calls exec() or _exit(). The good thing here is that it should >be easy to implement as the infrastructure for suspending a process >until another exits already exists. How about the Cygwin way, i.e. 'suspend' the parent and let the child run after fork. Your case: If it exec()s within a specific time limit, fine. If not, you can follow the suggestion to copy its entire memory space. -`J' -- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists