| Anonymous | Login | Signup for a new account | 11-10-2008 12:34 PST |
| Main | My View | View Issues | Change Log | Docs |
| Viewing Issue Simple Details [ Jump to Notes ] | [ View Advanced ] [ Issue History ] [ Print ] | ||||||||
| ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||
| 0004324 | [BusyBox] Standards Compliance | major | always | 07-25-08 10:03 | 09-20-08 09:23 | ||||
| Reporter | corp186 | View Status | public | ||||||
| Assigned To | BusyBox | ||||||||
| Priority | normal | Resolution | fixed | ||||||
| Status | closed | Product Version | svn | ||||||
| Summary | 0004324: Busybox ASH cannot trap | ||||||||
| Description |
The following script hangs up with kill -HUP %1 from the current shellm but not with kill -HUP <processid> from another shell. Without the trap, it does react to signals from another shell, but of course it does not run the signal handler. This is a bug, right? Is there any way to make the script handle a signla sent from another shell> #!/bin/sh cleanup () { echo "cleaning" } trap cleanup HUP echo "sleeping " sleep 100000 echo "done" |
||||||||
| Additional Information |
This is basically reopening bug 0000994. The submitted was on the right track but forgot an important piece of the puzzle. When vda ran the test script, everything seemed fine. This is probably because when vda ran it, /bin/sh was symlinked to /bin/busybox. If you execute the script from within ASH with /bin/sh symlinked to busybox (for ASH), you can reproduce the issue of the trap not working. |
||||||||
| Attached Files |
|
||||||||
|
|
|||||||||
| Copyright © 2000 - 2006 Mantis Group |