At 10:57 pm, Wednesday, October 9 2002, Voytek Eymont mumbled:
> thanks, Mike (I was kinda hoping I can kill the console, rather than the
> process) (anyhow, I needed to know how to identify and kill, anyway)
>
You can certain kill the console, you just need to kill the shell, rather
than, say, the editor.
steven pts/4 :0.0 23:27 2.00s 0.02s 0.02s bash
So, we take that line from 'w' (most useful command), and use ps:
steven@broken:~$ ps ax | grep pts/4
12998 pts/4 S 0:00 bash
13024 pts/5 S 0:00 grep pts/4
Now we have the PID, we can wield kill. (Note bash doesn't react to a HUP,
so send it a SIGKILL with 'kill -KILL' or 'kill -9'.
> say looking at ps ax:
>
> do I really need apdm running on a what meant to be a 'server' ?
>
> can I take it out, or should I leave it running ?
>
If you mean apmd, or the power management daemon, it's up to you. You can
disable it, or if you'd rather not run it, you can disable it. apmd doesn't
really listen on any unix or TCP sockets, so there is no harm in leaving it
running,
--
Steve
I've lost my sig!
--
SLUG - Sydney Linux User's Group - http://slug.org.au/
More Info: http://lists.slug.org.au/listinfo/slug
