Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
hi,
in system v there are no worker process.why in systemd we have worker process?
a worker process is used by an user mode process when this process work in kernel mode?
during the process life a process can run in user mode or kernel mode.in kernel mode the process has elevated privileges.right?
hi,
in system v there are no worker process.why in systemd we have worker process?
I don't know which processes you mean, but the difference between System V initialization and systemd is that systemd does much more than just starting and stopping services.
Quote:
during the process life a process can run in user mode or kernel mode.in kernel mode the process has elevated privileges.right?
"Elevated privileges" is usually understood as "superuser privileges". The process doesn't change its ID to superuser when it enters the kernel. Instead, the CPU changes state so that it can execute privileged instructions and access protected memory areas.
On Slackware with KDE, which most decidedly does not use SystemD but rather uses a BSD-style init system, there are "kworker" processes.
These are kernel processes, i.e. all their code resides in the kernel. They should be marked like this: [kworker]. I believe they perform various asynchronous tasks, perhaps garbage collection and the like, and indeed have nothing to do with systemd or any other service initialization or management framework.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.