Difference between revisions of "Process identifier (PID)"
Jump to navigation
Jump to search
Tags: Mobile web edit, Mobile edit |
|||
| Line 4: | Line 4: | ||
Apr 08 08:44:48 SERVER systemd[1]: [[nginx.service]]: Failed to parse PID from file [[/run]]/nginx.pid: Invalid argument | Apr 08 08:44:48 SERVER systemd[1]: [[nginx.service]]: Failed to parse PID from file [[/run]]/nginx.pid: Invalid argument | ||
| − | + | In [[WSL]] | |
| + | System has not been booted with systemd as init system (PID 1). Can't operate. | ||
| + | Failed to connect to bus: Host is down | ||
Revision as of 12:34, 21 October 2021
This article is a Draft. Help us to complete it.
Apr 08 08:44:48 SERVER systemd[1]: nginx.service: Failed to parse PID from file /run/nginx.pid: Invalid argument
In WSL
System has not been booted with systemd as init system (PID 1). Can't operate. Failed to connect to bus: Host is down
Related terms
/proc/$PID/cmdline /proc/$pid/fd
See also
- Process, zombie process, fork, thread:
ps,tree,pstree,ps axf,proc,pwdx,which,watch,sar -q,tload,uptime, Interrupts,pgrep,tasklist(Windows), Zombie process,pstack,docker ps,docker-compose ps,jobs,acct,process mrelease,pidstat, IPC,pidof - Linux Kernel: namespaces, Cgroups, OOM, proc, Linux Kernel changelog,
sysctl, userfaultfd, Grub, ENOSPC, ENOMEM, DKMS, syscall, Transparent huge pages, smatch, sysfs, vm.swappiness, CFS, Runlevel, Jens Axboe, Consistent Network Device Naming, Initial ramdisk (initrd),modprobe, MTD, Linux Kernel vulnerabilities,/sys/kernel/, KernelCare,unix://, Data Plane Development Kit (DPDK)
Advertising:
