mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Jon Ringle <jon@ringle.org>
To: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: Re: [ptxdist] kill missing RT signals
Date: Fri, 11 Apr 2014 12:01:14 -0400	[thread overview]
Message-ID: <CAMwGMjzdkrLXAr87axydGWvE=J60c5pjdvmoPJR12MxLPUcZPg@mail.gmail.com> (raw)
In-Reply-To: <CAMwGMjzoHy38jEErQ10GQJ4fL0NwNh8sX1=EBMp2CNLbhB8Jjg@mail.gmail.com>

On Fri, Apr 11, 2014 at 11:34 AM, Jon Ringle <jon@ringle.org> wrote:
> Ok... I've a little confused about this. It seems like I have 2
> different versions of kill installed on my target, but I can't figure
> out where the 1st one is located:
>
> root@ec1k:/# kill -l
>  1) SIGHUP       2) SIGINT       3) SIGQUIT      4) SIGILL
>  5) SIGTRAP      6) SIGABRT      7) SIGBUS       8) SIGFPE
>  9) SIGKILL     10) SIGUSR1     11) SIGSEGV     12) SIGUSR2
> 13) SIGPIPE     14) SIGALRM     15) SIGTERM     16) SIGSTKFLT
> 17) SIGCHLD     18) SIGCONT     19) SIGSTOP     20) SIGTSTP
> 21) SIGTTIN     22) SIGTTOU     23) SIGURG      24) SIGXCPU
> 25) SIGXFSZ     26) SIGVTALRM   27) SIGPROF     28) SIGWINCH
> 29) SIGIO       30) SIGPWR      31) SIGSYS
> root@ec1k:/# which kill
> /bin/kill
> root@ec1k:/# /bin/kill -l
>  1) HUP
>  2) INT
>  3) QUIT
>  4) ILL
>  5) TRAP
>  6) ABRT
>  7) BUS
>  8) FPE
>  9) KILL
> 10) USR1
> 11) SEGV
> 12) USR2
> 13) PIPE
> 14) ALRM
> 15) TERM
> 16) STKFLT
> 17) CHLD
> 18) CONT
> 19) STOP
> 20) TSTP
> 21) TTIN
> 22) TTOU
> 23) URG
> 24) XCPU
> 25) XFSZ
> 26) VTALRM
> 27) PROF
> 28) WINCH
> 29) POLL
> 30) PWR
> 31) SYS
> 32) RTMIN
> 64) RTMAX

I didn't realize until now that bash has a builtin kill command, which
is what it seems that is what was running on my 1st 'kill -l'
invocation above.

Jon

-- 
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2014-04-11 16:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-11  0:58 Jon Ringle
2014-04-11 15:34 ` Jon Ringle
2014-04-11 16:01   ` Jon Ringle [this message]
2014-04-12  7:29     ` Robert Schwebel
2014-04-15 15:33     ` Michael Olbrich

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAMwGMjzdkrLXAr87axydGWvE=J60c5pjdvmoPJR12MxLPUcZPg@mail.gmail.com' \
    --to=jon@ringle.org \
    --cc=ptxdist@pengutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox