> -----Original Message----- > i am running > sys-apps/coreutils-5.2.1
Well, I'm not sure exactly what might be causing sleep to be issuing a SIGUSR1 signal, but here's a few suggestions: 1. coreutils-5.3 is available from ftp://ftp.gnu.org/gnu/coreutils/coreutils-5.3.tar.gz so you might want to download it, build it, and install into /usr/local. It might be a resolved issue... 2. coreutils-5.2.1 appears to have new ebuilds available (r1 through r4). Emerging one of these may fix the problem. 3. I unpacked coreutils and did a brief walkthrough of the code but could not find that it was referencing SIGUSR1 at all. I noticed that your script simply calls 'sleep'. Calling sleep by name may not be calling /bin/sleep, it might be referencing a different sleep in your path or an alternate shell function. You could try replacing the simple 'sleep 2' with '/bin/sleep 2' to see if it has any effect. Dave -- [email protected] mailing list
