Is it normal for an OS to have over 100 processes running at all times even when my computer is idle?

Is it normal for an OS to have over 100 processes running at all times even when my computer is idle?

Attached: windows-10-october-2018-update.jpg (1600x900, 117K)

On Windows yes.
On any other OS no.

systemctl now and tell me you have below 100 daemons/services running

If nothing's processing, is your computer really running?

depends on what you would count as a process

no, but that's what happens when the OS is coded by pajeets

>systemctl

OpenBSD doesn't have this problem.

>muh systemd

It’s your machine. :Dont want that many running when idling? Control what it does.

>systemctl now and tell me you have below 100 daemons/services running

systemctl -state=running

not even 20:

init.scope
session-1.scope
dbus.service
dhcpcd.service
[email protected]
lvm2-lvmetad.service
polkit.service
rtkit-daemon.service
systemd-journald.service
systemd-logind.service
systemd-udevd.service
[email protected]
dbus.socket
lvm2-lvmetad.socket
systemd-journald-audit.socket
systemd-journald-dev-log.socket
systemd-journald.socket
systemd-udevd-control.socket
systemd-udevd-kernel.socket

Does it inconvenience you in any way? Are you noticing performance issues as a result of background processes?

The big problem with Windows is not the huge number of processes running all the time, it's that it continously reads and writes to disk even when the system is idle.

We noticed at work how the harddrives of Windows machines kept dying years before the same drives in our Linux machines.

26:
init.scope
session-1.scope
cronie.service
dbus.service
[email protected]
lvm2-lvmetad.service
ModemManager.service
polkit.service
rtkit-daemon.service
systemd-journald.service
systemd-logind.service
systemd-networkd.service
systemd-resolved.service
systemd-timesyncd.service
systemd-udevd.service
udisks2.service
upower.service
[email protected]
dbus.socket
lvm2-lvmetad.socket
systemd-journald-audit.socket
systemd-journald-dev-log.socket
systemd-journald.socket
systemd-networkd.socket
systemd-udevd-control.socket
systemd-udevd-kernel.socket

21
colord.service loaded active running Manage, Install and Generate
dbus.service loaded active running D-Bus System Message Bus
dhcpcd.service loaded active running dhcpcd on all interfaces
[email protected] loaded active running Getty on tty1
httpd.service loaded active running Apache Web Server
lvm2-lvmetad.service loaded active running LVM2 metadata daemon
polkit.service loaded active running Authorization Manager
rtkit-daemon.service loaded active running RealtimeKit Scheduling Polic
systemd-journald.service loaded active running Journal Service
systemd-logind.service loaded active running Login Service
systemd-udevd.service loaded active running udev Kernel Device Manager
udisks2.service loaded active running Disk Manager
upower.service loaded active running Daemon for power management
[email protected] loaded active running User Manager for UID 1000
dbus.socket loaded active running D-Bus System Message Bus Soc
lvm2-lvmetad.socket loaded active running LVM2 metadata daemon socket
systemd-journald-audit.socket loaded active running Journal Audit Socket
systemd-journald-dev-log.socket loaded active running Journal Socket (/dev/log)
systemd-journald.socket loaded active running Journal Socket
systemd-udevd-control.socket loaded active running udev Control Socket
systemd-udevd-kernel.socket loaded active running udev Kernel Socket

Attached: 2019-03-29-130454_453x237_scrot.png (453x237, 19K)

currently 52

>Windows
>OS
Windows itself is a service

Which ones are necessary?

Yeah, why not?

>another tech-illiterate who thinks systemd is bad

>systemd is good goyim

only two processes in elevators: up and down

>using Windows 10
Nobody is this stupid, right?

>m-muh suckless I'm so cool guyz I hate systemd xDddddd

This

Yes OP, this is totally normal for a Windows operating system. A Unix based OS however...

39.
at-spi-bus-laun
at-spi2-registr
avahi-daemon
bash
brltty
console-kit-dae
cron
cups-browsed
cupsd
dbus-daemon
dbus-daemon
dbus-launch
dconf-service
dhclient
dockerd
elogind
exim4
gpm
gvfs-udisks2-vo
gvfsd
gvfsd-metadata
gvfsd-trash
irqbalance
login
packagekitd
polkitd
pulseaudio
rsyslogd
rtkit-daemon
sd_dummy
sd_espeak-ng
sd_generic
speech-dispatch
sh
sh
sshd
tor
udevd
udiskd
xbindkeys

Not that user but the only reason I use devuan on my thinkpad (instead of debian) is because I found that I have slightly better battery life, and the only reason I use it on my desktop is because I use it on my thinkpad

What, are your Linux boxes not logging anything lol

mactoddler

Of course they are, but those small writes are not even noticeable, meanwhile the Windows systems are churning 24/7, they just never stop reading/writing to the harddrive.

Why doesn’t dark mode work on my pc? FAK!

>guaranteed (you)'s

When I first got my laptop win8.1 I think it had some bloat number around 60 or so, now its around 30 and I have unnecessary things running like font caching. It could be too many, it sounds like to many but I don't know your setup.

>is it normal for an OS which almost does everything on your PC to have processes running at all time?
>"b-but muh void headless install only has 20!!! (two digits!!!!) whilst BLOATED Winshit has 100 (THREE digits!!!!)
Why is the amount of processes important? Windows could have 100 light processes and Linux could have just 10 demanding ones, you just don't know.
If you want your drives to auto-Mount guess what: you need a process running all the time. If you want your notifications you need a deamon running all the time waiting for applications to spout their d-bus messages or some shit.
Since Windows has a lot of features it needs to constantly perform operations in the background. If you want a barebone all-manual system then switch to Linux or something like that

System has not been booted with systemd as init system (PID 1). Can't operate.

>132 loaded units listed
tfw memejaro

Doesn't mean those are all running, let alone the fact that not every unit is a service

brainlet here how to make it to list only those running?
systemctl | grep running | wc -l

returns 33, is it it?

systemctl --type=service --state=running
At the end of the output it shows how many those are.

Win 7 master race reporting. I don't have this problem. Sounds like a Win 10 issue.

10 that actually map to currently running processes

don't forget to check --user too.

I hope you mean `ps -e | wc -l`

# systemctl
systemctl: command not found

Having more processes inherently adds overhead to the kernel scheduler. If the scheduler wasn't checking on every process, multitasking would never work.

Now, of course, one process hogging 99% of the country time is probably worse than 1000 idle processes. But to say there is no problem with many processes running, is simply incorrect.

By the way you technically don't need a process for automounting because it can be in a kernel module that mounts based on hardware events. However usually this isn't the way that it's done for various reasons. Being inside the kernel still uses cpu time, just less, and adds more problems, plus it probably results in a process spawning when something can be mounted. But nevertheless, a feature like automounting needn't be a process. Technically, being in the kernel should save processing time usually, but other issues come along that generally decide whether something ends up a service. Dbus style IPC is an example of something that's been debated forever, and there have been in-kernel dbus modules but they never got upstreamed.

>sysctl

21 total
11 with --user

>hostnamectl

Yes. Now stop asking questions.

Yes actually.

>On Windows 10 yes.
Fixed.