Bug 29504

Summary: nohup(1) page is confusing about SIGQUIT
Product: Documentation Reporter: Gary W. Swearingen <swear>
Component: Books & ArticlesAssignee: freebsd-bugs (Nobody) <bugs>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Latest   
Hardware: Any   
OS: Any   

Description Gary W. Swearingen 2001-08-07 17:10:04 UTC 
The "Description" says "The signal SIGQUIT may also be set to be
ignored."  This could mean
1) "the user may set it..." (if so, it should say how);
2) "the signal MIGHT be ignored, but we don't know";
3) "the signal is currently ignored but that might change"
(which is the same as "2" as far as the user is concerned).

I.e., it is unclear what it means.
================

Fix: 

Determine how the program behaves and rewrite the sentence.
How-To-Repeat: n/a
================
Comment 1 dd freebsd_committer freebsd_triage 2001-08-11 21:07:08 UTC 
Responsible Changed
From-To: gnats-admin->freebsd-bugs

misfiled
Comment 2 Mike Barcroft freebsd_committer freebsd_triage 2001-08-23 04:15:45 UTC 
State Changed
From-To: open->closed


This has been fixed in -CURRENT and -STABLE with my last commit to 
nohup(1) which removes the ability to ignore SIGQUIT.  The change  
also makes nohup(1) more standards compliant.