Skip to main content
Unix & Linux

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

5
  • did you try adding the redirect 2> /dev/null after the pkill sleep ?
    – rahul
    Commented Feb 14, 2015 at 6:22
  • 1
    @rahul: yes I did -- pkill isn't generating the message, bash is.
    – fearless_fool
    Commented Feb 14, 2015 at 6:23
  • I used kill instead of pkill and do not get the stderr. strange..
    – rahul
    Commented Feb 14, 2015 at 6:32
  • @rahul: could it be a built in vs non-built in thing? Did you try it with pkill as well?
    – fearless_fool
    Commented Feb 14, 2015 at 6:38
  • yes, i believe it is. I get the same error with pkill, but not with kill. While using kill, i used the pid instead of the proc name.
    – rahul
    Commented Feb 14, 2015 at 7:12