When I run ps -e, I see a lot of processes that I have no clue what they do. I only run one server off this machine, so is it possible to cut down on all of these processes? Are they system critical? They seem to start everytime the VDS starts, so I don't know.
~# ps -e
PID TTY TIME CMD
1 ? 00:00:01 init
2 ? 00:00:00 kthreadd
3 ? 00:00:07 ksoftirqd/0
5 ? 00:00:00 kworker/u:0
6 ? 00:00:00 migration/0
7 ? 00:00:00 watchdog/0
8 ? 00:00:00 migration/1
9 ? 00:00:00 kworker/1:0
10 ? 00:00:00 ksoftirqd/1
12 ? 00:00:00 watchdog/1
13 ? 00:00:00 migration/2
14 ? 00:00:00 kworker/2:0
15 ? 00:00:00 ksoftirqd/2
16 ? 00:00:00 watchdog/2
17 ? 00:00:00 migration/3
19 ? 00:00:00 ksoftirqd/3
20 ? 00:00:00 watchdog/3
21 ? 00:00:00 migration/4
22 ? 00:00:00 kworker/4:0
23 ? 00:00:00 ksoftirqd/4
24 ? 00:00:00 watchdog/4
25 ? 00:00:00 migration/5
27 ? 00:00:00 ksoftirqd/5
28 ? 00:00:00 watchdog/5
29 ? 00:00:00 migration/6
31 ? 00:00:00 ksoftirqd/6
32 ? 00:00:00 watchdog/6
33 ? 00:00:00 migration/7
35 ? 00:00:00 ksoftirqd/7
36 ? 00:00:00 watchdog/7
37 ? 00:00:00 cpuset
38 ? 00:00:00 khelper
39 ? 00:00:00 kdevtmpfs
40 ? 00:00:00 netns
41 ? 00:00:00 kworker/u:1
42 ? 00:00:00 xenwatch
43 ? 00:00:00 xenbus
44 ? 00:00:00 sync_supers
45 ? 00:00:00 bdi-default
46 ? 00:00:00 kintegrityd
47 ? 00:00:00 kblockd
48 ? 00:00:00 ata_sff
49 ? 00:00:00 khubd
50 ? 00:00:00 md
51 ? 00:00:01 kworker/1:1
52 ? 00:00:00 kworker/2:1
53 ? 00:00:00 kworker/3:1
54 ? 00:00:00 kworker/4:1
55 ? 00:00:00 kworker/5:1
56 ? 00:00:00 kworker/6:1
57 ? 00:00:00 kworker/7:1
59 ? 00:00:00 khungtaskd
60 ? 00:00:42 kswapd0
61 ? 00:00:00 ksmd
62 ? 00:00:00 khugepaged
63 ? 00:00:00 fsnotify_mark
64 ? 00:00:00 ecryptfs-kthrea
65 ? 00:00:00 crypto
73 ? 00:00:00 kthrotld
74 ? 00:00:00 scsi_eh_0
75 ? 00:01:04 scsi_eh_1
96 ? 00:00:00 devfreq_wq
98 ? 00:00:01 jbd2/xvda2-8
99 ? 00:00:00 ext4-dio-unwrit
184 ? 00:00:00 upstart-udev-br
186 ? 00:00:00 udevd
316 ? 00:00:00 udevd
317 ? 00:00:00 udevd
360 ? 00:00:00 kpsmoused
365 ? 00:00:00 kworker/5:2
366 ? 00:00:00 kworker/7:2
368 ? 00:00:00 kworker/3:2
374 ? 00:00:00 kworker/6:2
413 ? 00:00:00 upstart-socket-
621 ? 00:00:04 jbd2/xvdb1-8
622 ? 00:00:00 ext4-dio-unwrit
635 ? 00:00:00 jbd2/xvda1-8
636 ? 00:00:00 ext4-dio-unwrit
665 ? 00:00:00 sshd
675 ? 00:00:00 dbus-daemon
687 ? 00:00:00 bluetoothd
702 ? 00:00:00 krfcommd
705 ? 00:00:03 rsyslogd
758 tty4 00:00:00 getty
766 tty5 00:00:00 getty
777 tty2 00:00:00 getty
779 tty3 00:00:00 getty
783 tty6 00:00:00 getty
789 ? 00:00:00 acpid
795 ? 00:00:24 irqbalance
800 ? 00:00:00 whoopsie
805 ? 00:00:00 cron
806 ? 00:00:00 atd
828 tty1 00:00:00 getty
830 ? 00:00:08 flush-202:0
831 ? 00:00:19 flush-202:16
836 ? 00:00:00 console-kit-dae
903 ? 00:00:00 polkitd
11389 ? 00:00:00 sshd
11581 pts/1 00:00:00 bash
13535 ? 00:00:00 kworker/0:3
16970 ? 00:00:00 kworker/0:0
27238 ? 00:00:01 kworker/0:1
27271 ? 00:00:00 sshd
27414 pts/2 00:00:00 bash
27666 pts/2 00:00:00 ps
31976 ? 00:00:01 kworker/0:2
Startup Linux Processes
-
- New to forums
- Posts: 4
- https://www.youtube.com/channel/UC40BgXanDqOYoVCYFDSTfHA
- Joined: Wed Dec 18, 2013 3:13 am
Re: Startup Linux Processes
Many of those are kernel worker threads that should be left on. Others are system-critical daemons. The only ones here that I think you could consider turning off would be the irqbalance service and cpuset.
Re: Startup Linux Processes
Thanks for your response. I appreciate it.