Bug 1377 - Use fork() instead of vfork()
Summary: Use fork() instead of vfork()
Alias: None
Product: Red Hat Raw Hide
Classification: Retired
Component: apmd
Version: 1.0
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Erik Troan
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 1999-03-01 10:18 UTC by enrico.scholz
Modified: 2008-05-01 15:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 1999-03-18 19:38:31 UTC

Attachments (Terms of Use)

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

Note You need to log in before you can comment on or make changes to this bug.