Re: traced or stopped process

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



2009/2/12 Hinko Kocevar <hinko.kocevar@xxxxxxxxxxxx>:
> Hi,
>
> On my embedded target system ps shows:
> # ps
>  PID USER       VSZ STAT COMMAND
>    1 root       792 S    init
>    2 root         0 SW<  [kthreadd]
>    3 root         0 SW<  [ksoftirqd/0]
>    4 root         0 SW<  [events/0]
>    5 root         0 SW<  [khelper]
>   27 root         0 SW<  [kblockd/0]
>   45 root         0 SW   [pdflush]
>   46 root         0 SW   [pdflush]
>   47 root         0 SW<  [kswapd0]
>   91 root         0 SW<  [aio/0]
>   95 root         0 SW<  [nfsiod]
>  201 root         0 SW<  [mtdblockd]
>  236 root         0 SW<  [rpciod/0]
>  240 root         0 SWN  [jffs2_gcd_mtd2]
>  358 root         0 SWN  [jffs2_gcd_mtd4]
>  369 root         0 SWN  [jffs2_gcd_mtd5]
>  380 root         0 SWN  [jffs2_gcd_mtd6]
>  391 root         0 SWN  [jffs2_gcd_mtd7]
>  402 root         0 SWN  [jffs2_gcd_mtd8]
>  456 root       792 S    /usr/sbin/httpd -c /etc/httpd.conf -p 4480 -h /www -f
>  463 root       816 S    /usr/sbin/dropbear -p 4422 -P /var/run/dropbear.pid -r /etc/dropbear/rsa.key -d /etc/dropbear/dss.key -F
>  475 root       800 S    /usr/sbin/crond -L /var/log/crond.log
>  495 root       800 S    -/bin/sh
>  516 root       880 S    /usr/sbin/dropbear -p 4422 -P /var/run/dropbear.pid -r /etc/dropbear/rsa.key -d /etc/dropbear/dss.key -F
>  517 root       808 S    -sh
>  522 root      7896 R    /program/taa2
>  529 root      7896 R    /program/taa2
>  532 root      7896 T    /program/taa2
>  533 root      7896 T    /program/taa2
>  534 root      7896 T    /program/taa2
>  537 root      7896 T    /program/taa2
>  660 root       880 S    /usr/sbin/dropbear -p 4422 -P /var/run/dropbear.pid -r /etc/dropbear/rsa.key -d /etc/dropbear/dss.key -F
>  661 root       808 S    -sh
>  676 root       792 R    ps
> # jobs
> # bg
> -sh: bg: No current job
> # fg
> -sh: fg: No current job
> #
>
>
> I'm curios how does /program/taa2 process enter
> traced or stopped mode (according to STAT = 'T')
> if one has *NOT* issued Ctrl + z or similar?

ehm, kill -STOP <pid of your process or thread>  or killall -STOP
<process name>?


> Is there a way to 'wake the process up' (make it runnable) from another ssh session ?

kill -CONT <pid of your process or thread> or killall -CONT <process name>

In all case, make sure the sender's uid is the same as the target
process' owner uid or you're root

regards,

Mulyadi.

--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx
Please read the FAQ at http://kernelnewbies.org/FAQ


[Index of Archives]     [Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]
  Powered by Linux