Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 1377

Summary: Use fork() instead of vfork()
Product: [Retired] Red Hat Raw Hide Reporter: enrico.scholz
Component: apmdAssignee: Erik Troan <ewt>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: low Docs Contact:
Priority: high    
Version: 1.0   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 1999-03-18 19:38:31 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description enrico.scholz 1999-03-01 10:18:18 UTC
Current apmd doesn't work very with the new initscripts,
which are relying that the called daemon goes into
background by itself.

apmd uses vfork() to go into background, but the libc-manual
says "Instead, the child process created with `vfork' shares
its parent's address space until it calls `_exit' or one of
the `exec' functions. In the meantime, the parent process
suspends execution". That's why apmd will not fork into
background and a fork() instead of vfork() at apmd.c:342
will reallow a "daemon apmd".

I have detected an apmd-3.0 (labeled as beta) which is using
fork() instead of vfork() too.

Comment 1 Cristian Gafton 1999-03-18 19:38:59 UTC
Fixed in the current beta