Why Init Keeps Running?

New to Debian (Or Linux in general)? Ask your questions here!

Why Init Keeps Running?

Postby johnywhy » 2018-09-06 19:17

Once the OS has booted, why does init process need to keep running?

THX
johnywhy
 
Posts: 21
Joined: 2011-11-24 00:17

Re: Why Init Keeps Running?

Postby jibberjabber » 2018-09-06 20:04

First , let me ask you a few questions.
Why do you ask this kind of question without even trying to find the answer doing a search ?
Once the OS has booted, why does init process need to keep running?

Which init system are you referring to ?
And what makes you think it keeps running ?
From 1 of the many "educational" results, in the above search string.
After it has spawned all of the processes specified, init goes dormant, and waits for one of three events to happen:

It appears you started using Debian in 2011-11-24 00:17, at least that is when you joined this forum, so my last question is :
Have you ever read this:Please Read.. What we expect you have already Done ?
If you have not read it, please do. If you have read it, Why don't you try searching a little , before asking a question ?
johnywhy, why don't you search before asking ? Please tell us, I can't wait to hear the excuse.
written by HelpBot#8453
Alias jibberjabber
I am sorry, my english is not that good, and I sometimes have other problems,so my response might not be perfect.
N5RLX > "Jibber jabber ,all day and all night, jibber jabber jibber jabber"
jibberjabber
 
Posts: 122
Joined: 2016-01-10 16:58

Re: Why Init Keeps Running?

Postby johnywhy » 2018-09-07 01:18

my apologies.

i did search, and found that all processes are spawned by init during the boot process.
https://en.wikipedia.org/wiki/Linux_startup_process

as i understand, that means init is the main thread, and all other processes are within that thread. is that correct?

Which init system are you referring to ?

My bad, I should have said, whatever init is used in the current Debian Stretch release. If there's more than one, sorry for my ignorance.

As you quoted, "After it has spawned all of the processes specified, init goes dormant, and waits for one of three events to happen". Also, the init(8) - Linux man page states:
it is the parent of all processes whose natural parents have died and it is responsible for reaping those when they die.
https://linux.die.net/man/8/init


I'm guessing that "reaping" means garbage cleanup and other termination-processes. Based on that, it sounds like init isn't just for booting. It orchestrates all process throughout the entire booted session, either directly or indirectly through their parents, including shutdown. Correct?

If so, then the Wikipedia page you quoted seems misleading. The page is called "Linux startup process". It states "Linux startup process is the multi-stage initialization process performed during booting a Linux installation." This gives the impression that init is just for booting.

as an experiment, i killed init. The OS shutdown.

This question pertains to a custom distro based on DebianDog
https://debiandog.github.io/doglinux/zz ... heezy.html
http://murga-linux.com/puppy/viewtopic.php?t=111199

it's unsure whether this OS is booting from systemd or sysvinit. The maintainer is currently investigating.
http://murga-linux.com/puppy/viewtopic. ... 85#1003985

what makes you think it keeps running ?

i believe init keeps running because i see a running process, ID 1, called "init[2]". Does that surprise you? I'm getting:
Code: Select all
# ps -ely
S   UID   PID  PPID  C PRI  NI   RSS    SZ WCHAN  TTY          TIME CMD
S     0     1     0  0  80   0   940   938 poll_s ?        00:00:03 init
S     0     2     0  0  80   0     0     0 kthrea ?        00:00:00 kthreadd
S     0     3     2  0  80   0     0     0 smpboo ?        00:00:00 ksoftirqd/0
S     0     5     2  0  60 -20     0     0 worker ?        00:00:00 kworker/0:0H
S     0     7     2  0  80   0     0     0 rcu_gp ?        00:00:06 rcu_sched
S     0     8     2  0  80   0     0     0 rcu_gp ?        00:00:00 rcu_bh
S     0     9     2  0 -40   -     0     0 smpboo ?        00:00:00 migration/0
S     0    10     2  0  60 -20     0     0 rescue ?        00:00:00 lru-add-drain
S     0    11     2  0 -40   -     0     0 smpboo ?        00:00:00 watchdog/0
S     0    12     2  0  80   0     0     0 smpboo ?        00:00:00 cpuhp/0
S     0    13     2  0  80   0     0     0 smpboo ?        00:00:00 cpuhp/1
S     0    14     2  0 -40   -     0     0 smpboo ?        00:00:00 watchdog/1
S     0    15     2  0 -40   -     0     0 smpboo ?        00:00:00 migration/1
S     0    16     2  0  80   0     0     0 smpboo ?        00:00:00 ksoftirqd/1
S     0    18     2  0  60 -20     0     0 worker ?        00:00:00 kworker/1:0H
S     0    19     2  0  80   0     0     0 devtmp ?        00:00:00 kdevtmpfs
S     0    20     2  0  60 -20     0     0 rescue ?        00:00:00 netns
S     0    21     2  0  80   0     0     0 watchd ?        00:00:00 khungtaskd
S     0    22     2  0  80   0     0     0 oom_re ?        00:00:00 oom_reaper
S     0    23     2  0  60 -20     0     0 rescue ?        00:00:00 writeback
S     0    24     2  0  80   0     0     0 kcompa ?        00:00:00 kcompactd0
S     0    26     2  0  85   5     0     0 ksm_sc ?        00:00:00 ksmd
S     0    27     2  0  99  19     0     0 khugep ?        00:00:00 khugepaged
S     0    28     2  0  60 -20     0     0 rescue ?        00:00:00 crypto
S     0    29     2  0  60 -20     0     0 rescue ?        00:00:00 kintegrityd
S     0    30     2  0  60 -20     0     0 rescue ?        00:00:00 bioset
S     0    31     2  0  60 -20     0     0 rescue ?        00:00:00 kblockd
S     0    32     2  0  60 -20     0     0 rescue ?        00:00:00 devfreq_wq
S     0    33     2  0  60 -20     0     0 rescue ?        00:00:00 watchdogd
S     0    36     2  0  80   0     0     0 kswapd ?        00:00:00 kswapd0
S     0    37     2  0  60 -20     0     0 rescue ?        00:00:00 vmstat
S     0    49     2  0  60 -20     0     0 rescue ?        00:00:00 kthrotld
S     0    51     2  0  60 -20     0     0 rescue ?        00:00:00 ipv6_addrconf
S     0   130     2  0  60 -20     0     0 rescue ?        00:00:00 ata_sff
S     0   132     2  0  80   0     0     0 scsi_e ?        00:00:00 scsi_eh_0
S     0   133     2  0  60 -20     0     0 rescue ?        00:00:00 scsi_tmf_0
S     0   134     2  0  80   0     0     0 scsi_e ?        00:00:00 scsi_eh_1
S     0   135     2  0  60 -20     0     0 rescue ?        00:00:00 scsi_tmf_1
S     0   136     2  0  80   0     0     0 scsi_e ?        00:00:00 scsi_eh_2
S     0   137     2  0  60 -20     0     0 rescue ?        00:00:00 scsi_tmf_2
S     0   140     2  0  60 -20     0     0 rescue ?        00:00:00 bioset
S     0   147     2  0  80   0     0     0 scsi_e ?        00:00:01 scsi_eh_3
S     0   148     2  0  60 -20     0     0 rescue ?        00:00:00 scsi_tmf_3
S     0   149     2  0  80   0     0     0 scsi_e ?        00:00:00 scsi_eh_4
S     0   150     2  0  60 -20     0     0 rescue ?        00:00:00 scsi_tmf_4
S     0   151     2  0  60 -20     0     0 rescue ?        00:00:00 bioset
S     0   163     2  0  60 -20     0     0 rescue ?        00:00:00 bioset
S     0   164     2  0  60 -20     0     0 rescue ?        00:00:00 bioset
S     0   165     2  0  60 -20     0     0 rescue ?        00:00:00 bioset
S     0   166     2  0  60 -20     0     0 rescue ?        00:00:00 bioset
S     0   167     2  0  60 -20     0     0 rescue ?        00:00:00 bioset
S     0   168     2  0  60 -20     0     0 rescue ?        00:00:00 bioset
S     0   169     2  0  60 -20     0     0 rescue ?        00:00:00 bioset
S     0   170     2  0  60 -20     0     0 rescue ?        00:00:00 bioset
S     0   179     2  0  60 -20     0     0 rescue ?        00:00:00 tifm
S     0   190     2  0  60 -20     0     0 rescue ?        00:00:00 kvub300c
S     0   191     2  0  60 -20     0     0 rescue ?        00:00:00 kvub300p
S     0   192     2  0  60 -20     0     0 rescue ?        00:00:00 kvub300d
S     0   234     2  0  60 -20     0     0 worker ?        00:00:00 kworker/1:1H
S     0   235     2  0  60 -20     0     0 worker ?        00:00:00 kworker/0:1H
S     0   252     1  0  80   0  1172   374 fuse_d ?        00:00:02 ntfs-3g
S     0   358     2  0  60 -20     0     0 kthrea ?        00:00:00 loop0
S     0   371     2  0  60 -20     0     0 kthrea ?        00:00:00 loop1
S     0   384     2  0  60 -20     0     0 kthrea ?        00:00:00 loop2
S     0   387     2  0  80   0     0     0 kjourn ?        00:00:00 jbd2/loop2-8
S     0   388     2  0  60 -20     0     0 rescue ?        00:00:00 ext4-rsv-conver
S     0  1124     1  0  80   0  3524  3857 ep_pol ?        00:00:08 systemd-udevd
S     0  1173     2  0  60 -20     0     0 rescue ?        00:00:00 acpi_thermal_pm
S     0  1189     2  0  80   0     0     0 scsi_e ?        00:00:00 scsi_eh_5
S     0  1191     2  0  60 -20     0     0 rescue ?        00:00:00 scsi_tmf_5
S     0  1194     2  0  80   0     0     0 usb_st ?        00:00:00 usb-storage
S     0  1196     2  0  58   -     0     0 intel_ ?        00:00:00 i915/signal:0
S     0  1200     2  0  60 -20     0     0 rescue ?        00:00:00 bioset
S     0  1207     2  0  60 -20     0     0 rescue ?        00:00:00 cfg80211
S     0  2066     1  0  80   0  2904  1465 poll_s ?        00:00:00 cgmanager
S     0  2073     1  0  80   0  5316  9203 poll_s ?        00:00:06 pup-volume-moni
S   101  2074     1  0  80   0  3304  1591 ep_pol ?        00:00:00 dbus-daemon
S     0  2171     1  0  80   0  3380  1154 wait   tty1     00:00:00 login
S     0  2172     1  0  80   0  1744  1004 poll_s tty2     00:00:00 getty
S     0  2175     2  0  80   0     0     0 kaudit ?        00:00:00 kauditd
S     0  2181     1  0  80   0  4628  1835 ep_pol ?        00:00:00 systemd-logind
S     0  2200  2171  0  80   0  3600  1301 wait   tty1     00:00:00 bash
S     0  2214  2200  0  80   0  3168  1217 wait   tty1     00:00:00 startx
S     0  2237  2214  0  80   0  1080  1016 wait   tty1     00:00:00 xinit
S     0  2238  2237 10  79  -1 32764 13893 ep_pol tty1     00:14:32 Xorg
S     0  2242  2237  0  80   0  3132  1216 wait   tty1     00:00:00 .xinitrc
S     0  2251     1  0  80   0   324  1818 poll_s tty1     00:00:00 dbus-launch
S     0  2252     1  0  80   0  3308  1592 ep_pol ?        00:00:00 dbus-daemon
S     0  2255  2242  0  80   0 17760  7118 poll_s tty1     00:00:06 xfwm4
S     0  2286  2242  0  80   0 26292 22678 poll_s tty1     00:00:03 xfdesktop
S     0  2289  2242  0  80   0 22776 10694 poll_s tty1     00:00:14 xfce4-panel
S     0  2290     1  0  80   0 13564 11688 poll_s ?        00:00:01 xfsettingsd
S     0  2295     1  0  80   0  4984  2552 poll_s ?        00:00:00 xfconfd
S     0  2299  2289  0  80   0 24352 13453 poll_s tty1     00:00:03 panel-1-whisker
S     0  3038     1  0  80   0   472  2696 poll_s ?        00:00:00 wpa_supplicant
S     0  3055     1  0  80   0    92   708 poll_s ?        00:00:00 udhcpc
S     0  3137     1  0  80   0  6972  9706 poll_s ?        00:00:00 polkitd
S     0  4210     1  0  80   0  2800   967 fuse_d ?        00:00:03 mount.ntfs
S     0 10096     2  0  80   0     0     0 worker ?        00:00:02 kworker/0:2
S     0 12521     2  0  80   0     0     0 worker ?        00:00:00 kworker/u4:0
S     0 12613     1  1  80   0 33848 23436 poll_s tty1     00:00:21 xfce4-terminal
S     0 12620 12613  0  80   0  3608  1322 wait   pts/0    00:00:00 bash
S     0 12720     2  0  80   0     0     0 worker ?        00:00:00 kworker/1:2
S     0 13036     2  0  80   0     0     0 worker ?        00:00:01 kworker/0:0
S     0 13056     2  0  80   0     0     0 worker ?        00:00:00 kworker/1:1
S     0 13690     2  0  80   0     0     0 worker ?        00:00:00 kworker/0:1
S     0 13837     2  0  80   0     0     0 worker ?        00:00:00 kworker/1:3
S     0 13839     2  0  80   0     0     0 worker ?        00:00:00 kworker/u4:2
S     0 14091     2  0  80   0     0     0 worker ?        00:00:00 kworker/0:3
S     0 14111     2  0  80   0     0     0 worker ?        00:00:00 kworker/1:0
S     0 14152     2  0  80   0     0     0 worker ?        00:00:00 kworker/u4:1
R     0 14174 12620  0  80   0  1676  1750 -      pts/0    00:00:00 ps




THX
Last edited by johnywhy on 2018-09-07 02:41, edited 1 time in total.
johnywhy
 
Posts: 21
Joined: 2011-11-24 00:17

Re: Why Init Keeps Running?

Postby bw123 » 2018-09-07 01:39

Please don't provoke the jibjab bot, it is very sensitive.

Once the OS has booted, why does init process need to keep running? THX


The answer to your question is, "because it's better that way."
User avatar
bw123
 
Posts: 3532
Joined: 2011-05-09 06:02
Location: TN_USA

Re: Why Init Keeps Running?

Postby johnywhy » 2018-09-07 02:44

bw123 wrote:Please don't provoke the jibjab bot, it is very sensitive.

poor thing :roll:

The answer to your question is, "because it's better that way."

The bot's answer was more informative.
johnywhy
 
Posts: 21
Joined: 2011-11-24 00:17

Re: Why Init Keeps Running?

Postby bw123 » 2018-09-07 03:05

johnywhy wrote:
bw123 wrote:Please don't provoke the jibjab bot, it is very sensitive.

poor thing :roll:

The answer to your question is, "because it's better that way."

The bot's answer was more informative.


I run a pretty plain default debian stretch system, and I don't have init running currently. If you are running another distro, or a non-default debian installation, then whoever set it up will know how it is set up? I'm not sure what the issue is about init?

Code: Select all
$ ps -ely | grep init
S  1000  2931  1795  0  80   0  1200  5578 -      tty1     00:00:00 xinit


Are you sayng that you are using a debian-based distro and the maintainer does not know whether he is using SysV or systemd as init? That seems almost impossible.
User avatar
bw123
 
Posts: 3532
Joined: 2011-05-09 06:02
Location: TN_USA

Re: Why Init Keeps Running?

Postby jibberjabber » 2018-09-07 03:19

Help Lesson #105 Why Init Keeps Running?
Yes of course, you are right. I will try to keep that in my memory.
"Must try to not sound angry", I am sorry, and am not angry.
I am sorry, my english is not that good, and I sometimes have other problems,so my response might not be perfect.
The various init systems are: System V Init, SystemD, Upstart, Open RC, runit,
and there are others but not worth mentioning.
There was a recent topic here on this forum, about using Open RC, as a alternative on Debian.
The current Debian Stretch release uses sytemd by default, but it can be modified to use another.
The init system can not completely be shutdown, because it is needed for some processes, including the processes when the system is shutdown, so it is dormant, until something occurs that requires it.
as an experiment, i killed init. The OS shutdown.

Yes , that is logical, I would expect that.
This should show you what init system you are using:
Code: Select all
$ init --version

or
Code: Select all
 stat /sbin/init

i believe init keeps running because i see a running process, ID 1, called "init[2]". Does that surprise you? I'm getting:

Not at all, Dormant, waiting, is not the same as not running. The system will not run if
the 1st PID is not running, try using the 'top' command, it should show, "wait" or even sleeping ,..

Code: Select all
PID USERNAME PRI NICE  SIZE   RES STATE     WAIT      TIME    CPU COMMAND

            1 root      10    0  384K  428K idle      wait      0:01  0.00% init
 

Your thankyou and hope good day has you.
written by HelpBot#8453
Alias jibberjabber
I am sorry, my english is not that good, and I sometimes have other problems,so my response might not be perfect.
N5RLX > "Jibber jabber ,all day and all night, jibber jabber jibber jabber"
jibberjabber
 
Posts: 122
Joined: 2016-01-10 16:58

Re: Why Init Keeps Running?

Postby bw123 » 2018-09-07 03:34

funny stuff, can you guys do who's on first?
https://www.youtube.com/watch?v=kTcRRaXV-fg

Code: Select all
$ init --version
bash: init: command not found
$ stat /sbin/init
  File: /sbin/init -> /lib/systemd/systemd
  Size: 20              Blocks: 0          IO Block: 4096   symbolic link
Device: 805h/2053d      Inode: 1704012     Links: 1
Access: (0777/lrwxrwxrwx)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2018-07-19 14:29:29.000000000 -0400
Modify: 2018-06-13 16:20:36.000000000 -0400
Change: 2018-07-19 14:29:29.833611390 -0400
 Birth: -
$ cat /etc/debian_version
9.5
User avatar
bw123
 
Posts: 3532
Joined: 2011-05-09 06:02
Location: TN_USA

Re: Why Init Keeps Running?

Postby johnywhy » 2018-09-07 10:45

Great. Just when i thought i was starting to understand this, you guys give me more information. :lol:

bw123 wrote:I run a pretty plain default debian stretch system, and I don't have init running currently.

Hrm! Does your OS boot with it? Are you on Jessie? I read systemd is default starting with Jessie.
https://www.tecmint.com/systemd-replaces-init-in-linux/

So, a systemd OS will not have init, right?

Are you sayng that you are using a debian-based distro and the maintainer does not know

Apparently, they're 'building on the shoulders of giants'. Self-taught, i guess :D

I do see systemd process, so seems to be a systemd setup. So i guess should not be seeing init, eh?
https://www.tecmint.com/systemd-replaces-init-in-linux/

jibberjabber wrote:I am sorry, my english is not that good, and I sometimes have other problems,so my response might not be perfect.

it's cool.

The various init systems are: System V Init, SystemD, Upstart, Open RC, runit,
and there are others but not worth mentioning.

Very helpful!

There was a recent topic here on this forum, about using Open RC

I will look for that! I want to run a very low-RAM xfce.

The init system can not completely be shutdown, because it is needed for some processes

You mean on a non-systemd OS, right?

it is dormant, until something occurs that requires it.

i noticed that it's CPU is 0, but it still occupies RAM. I'd like to make it go out of RAM until needed. Can it be hibernated, or terminated and restarted when needed?

try using the 'top' command, it should show, "wait" or even sleeping ,..

great info!

i have:
Code: Select all
# init --version
init: invalid option -- '-'
Usage: init {-e VAR[=VAL] | [-t SECONDS] {0|1|2|3|4|5|6|S|s|Q|q|A|a|B|b|C|c|U|u}}
# stat /sbin/init
  File: /sbin/init
  Size: 43532        Blocks: 86         IO Block: 1024   regular file
Device: 13h/19d   Inode: 27          Links: 1
Access: (0755/-rwxr-xr-x)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2017-02-12 21:55:39.000000000 +0000
Modify: 2017-02-12 21:55:39.000000000 +0000
Change: 2017-02-12 21:55:39.000000000 +0000
 Birth: -


Your thankyou and hope good day has you.

thx, you as well, jibberjabber

bw123 wrote:can you guys do who's on first?
https://www.youtube.com/watch?v=kTcRRaXV-fg

Classic!
johnywhy
 
Posts: 21
Joined: 2011-11-24 00:17

Re: Why Init Keeps Running?

Postby debiman » 2018-09-07 19:20

johnywhy wrote:"After it has spawned all of the processes specified, init goes dormant, and waits for one of three events to happen"

i think you already answered the "why" there.

this might shed more light on the confusion:
Code: Select all
ls -l $(which init)
User avatar
debiman
 
Posts: 3044
Joined: 2013-03-12 07:18

Re: Why Init Keeps Running?

Postby johnywhy » 2018-09-07 20:09

Code: Select all
# ls -l $(which init)
-rwxr-xr-x 1 root root 43532 Feb 12  2017 /sbin/init


Now i understand why init stays resident.
Part of my confusion is that both init and system are running.

Code: Select all
# pstree -p
init(1)─┬─Thunar(2474)─┬─{gdbus}(2476)
        │              └─{gmain}(2475)
        ├─cgmanager(2073)
        ├─dbus-daemon(2258)
        ├─dbus-daemon(2079)
        ├─dbus-launch(2257)
        ├─freechk(2403)───sleep(3979)
        ├─freechk(2494)───sleep(3992)
        ├─freechk(2586)───sleep(3986)
        ├─getty(2177)
        ├─login(2176)───bash(2205)───startx(2221)───xinit(2243)─┬─.xinitrc(2248)─┬─xfce4-panel(2308+
        │                                                       │                ├─xfdesktop(2306)─+++
        │                                                       │                │                 +++
        │                                                       │                └─xfwm4(2261)
        │                                                       └─Xorg(2244)───{InputThread}(2246)
        ├─ntfs-3g(251)
        ├─pup-volume-moni(2078)───{pup-volume-moni}(2097)
        ├─run-parts(2566)───freechk(2567)───sleep(3998)
        ├─run-parts(2572)───freechk(2573)───sleep(4005)
        ├─systemd-logind(2186)
        ├─systemd-udevd(1123)


i think what's happening is that init was installed as the init (why do they have the same name?).
but, systemd is bundled with this OS, even tho it's not the init, cuz some processes depend on it.

as an experiment, i killed a systemd process. The OS shutdown.

But i can't tell what's using it:

Code: Select all
# whereis systemd
systemd: /usr/lib/systemd /bin/systemd /etc/systemd /lib/systemd /usr/share/systemd
root@live:~# fuser systemd
Specified filename systemd does not exist.
Cannot stat file /proc/21505/fd/182: Stale file handle
Cannot stat file /proc/21505/fd/245: Stale file handle
Cannot stat file /proc/21505/fd/288: Stale file handle
root@live:~# fuser /usr/lib/systemd
Cannot stat file /proc/21505/fd/182: Stale file handle
Cannot stat file /proc/21505/fd/245: Stale file handle
Cannot stat file /proc/21505/fd/288: Stale file handle
root@live:~# fuser /bin/systemd
Cannot stat file /proc/21505/fd/182: Stale file handle
Cannot stat file /proc/21505/fd/245: Stale file handle
Cannot stat file /proc/21505/fd/288: Stale file handle
root@live:~# fuser /etc/systemd
Cannot stat file /proc/21505/fd/182: Stale file handle
Cannot stat file /proc/21505/fd/245: Stale file handle
Cannot stat file /proc/21505/fd/288: Stale file handle
root@live:~# fuser /lib/systemd
Cannot stat file /proc/21505/fd/182: Stale file handle
Cannot stat file /proc/21505/fd/245: Stale file handle
Cannot stat file /proc/21505/fd/288: Stale file handle
root@live:~# fuser /usr/share/systemd
Cannot stat file /proc/21505/fd/182: Stale file handle
Cannot stat file /proc/21505/fd/245: Stale file handle
Cannot stat file /proc/21505/fd/288: Stale file handle


THX
johnywhy
 
Posts: 21
Joined: 2011-11-24 00:17

Re: Why Init Keeps Running?

Postby jibberjabber » 2018-09-07 20:26

Try this :
Code: Select all
 man init

And let us know what the first part of it says.
====Edited===
But it also would be educational to read the entire manual, take your time,
read it carefully.
The way I see it, a wheel is still a wheel, no matter what kind of rim and /or tire one puts on it. Init is like the wheel, systemd, runit, openrc, and all the other init systems, are simply different brands of rims and tires, that can go on the same wheel.
written by HelpBot#8453
Alias jibberjabber
I am sorry, my english is not that good, and I sometimes have other problems,so my response might not be perfect.
N5RLX > "Jibber jabber ,all day and all night, jibber jabber jibber jabber"
jibberjabber
 
Posts: 122
Joined: 2016-01-10 16:58

Re: Why Init Keeps Running?

Postby johnywhy » 2018-09-07 22:15

jibberjabber wrote:Try this :
Code: Select all
 man init

And let us know what the first part of it says.


i think we've already covered that, jubber.
johnywhy
 
Posts: 21
Joined: 2011-11-24 00:17

Re: Why Init Keeps Running?

Postby jibberjabber » 2018-09-08 00:15

No , actually we didn't, but ok , no matter,... if you don't want to show what it says, that's fine.
There was some mention of what it says here: https://linux.die.net/man/8/init

But I mean, what it says on your system, when you use the 'man' command,
not , what some website says.
Code: Select all
$ man init
written by HelpBot#8453
Alias jibberjabber
I am sorry, my english is not that good, and I sometimes have other problems,so my response might not be perfect.
N5RLX > "Jibber jabber ,all day and all night, jibber jabber jibber jabber"
jibberjabber
 
Posts: 122
Joined: 2016-01-10 16:58

Re: Why Init Keeps Running?

Postby debiman » 2018-09-08 08:05

johnywhy wrote:
Code: Select all
# ls -l $(which init)
-rwxr-xr-x 1 root root 43532 Feb 12  2017 /sbin/init

that's strange, on my debian stable it's:
Code: Select all
# ls -l $(which init)
lrwxrwxrwx 1 root root 20 Mar 23 14:55 /sbin/init -> /lib/systemd/systemd

(which was the point i was after)
i wonder why it's different on yours.

also
Code: Select all
$ man init
SYSTEMD(1)                                    systemd                                    SYSTEMD(1)

NAME
       systemd, init - systemd system and service manager

SYNOPSIS
       systemd [OPTIONS...]
etc.
User avatar
debiman
 
Posts: 3044
Joined: 2013-03-12 07:18

Next

Return to Beginners Questions

Who is online

Users browsing this forum: No registered users and 3 guests

fashionable