https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283163

--- Comment #9 from v...@fbsd.ru ---
(In reply to Konstantin Belousov from comment #8)

Yes, I understand it, but, prison0 is different from other jails, 

i.e. `ps ax` in prison0 - shows processes from all jails, and normaly kill from
prison0 will successfuly send a signal to process in other jail.

# sysctl security.jail.param.jid
security.jail.param.jid: 0

# ps axJ4 -o jid,pid,tty,state,command
JID   PID TTY STAT COMMAND
  4 10800 -   SNsJ /usr/sbin/syslogd -ss -c
  4 10833 -   INsJ /usr/sbin/cron -s
  4 10869 -   INsJ nginx: master process /usr/local/sbin/nginx
  4 55913 -   INJ  nginx: worker process (nginx)
  4 55914 -   INJ  nginx: worker process (nginx)
  4 55915 -   INJ  nginx: worker process (nginx)
  4 55916 -   INJ  nginx: worker process (nginx)
  4 55917 -   INJ  nginx: worker process (nginx)
  4 55918 -   INJ  nginx: worker process (nginx)
  4 55919 -   INJ  nginx: worker process (nginx)
  4 55920 -   INJ  nginx: worker process (nginx)

# kill -15 10869

# ps axJ4 -o jid,pid,tty,state,command
JID   PID TTY STAT COMMAND
  4 10800 -   INsJ /usr/sbin/syslogd -ss -c
  4 10833 -   SNsJ /usr/sbin/cron -s
#

so, for prison0, prison_proc_iterate() will go only through processes of
prison0 or through all system processes?

if the first, then kill(sig, -1) will not sent signal to processes in other
jails, 
if the second, then I've confused with name prison_proc_iterate()

(that is why I am askin)

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to