66-info

This command displays information about trees and services.

Interface

Main interface

	66-info [ -h help ] [ -T tree ] [ -S service ]

Tree sub interface

	66-info [ -T ] [ -h help ] [ -c | -C ] [ -v verbosity ] [ -l live ] [ -r recurse ] [ -d depth ] tree

Service sub interface

	66-info [ -S ] [ -h help ] [ -c | -C ] [ -v verbosity ] [ -l live ] [ -p n lines ] [ -r recurse ] [ -d depth ] service

66-info displays detailed information about a tree or a specific service depending on the options passed.

Main Options

-h : prints this help.
-T : asks for tree information.
-S : asks for service information.

Tree sub options

-h : prints this help.
-c : disable colorization.
-C : force colorization.
-v verbosity : increases/decreases the verbosity of the command. 1(Default): Only print error messages. 2: Also print warning messages. 3: Also print debugging messages.
-l live : changes the supervision directory of service to live. By default this will be %%livedir%%. The default can also be changed at compile time by passing the --livedir=live option to ./configure. An existing absolute path is expected and should be within a writable filesystem - likely a RAM filesystem—see 66-scandir.
-r : shows the dependency graph of tree in reverse mode.
-d depth : limits the depth of the dependency graph visualisation; defaults to 1.

(!) If tree is not specified 66-info will display information about all available trees for the current owner of the process.

Service sub options

-h : prints this help.
-c : disable colorization.
-C : force colorization.
-v verbosity : increases/decreases the verbosity of the command. 1(Default): Only print error messages. 2: Also print warning messages. 3: Also print debugging messages.
-l live : changes the supervision directory of service to live. By default this will be %%livedir%%. The default can also be changed at compile time by passing the --livedir=live option to ./configure. An existing absolute path is expected and should be within a writable filesystem - likely a RAM filesystem—see 66-scandir.
-p n lines : prints the n last lines from the associated log file of the service.
-r : shows the dependency graph of service in reverse mode.
-d depth : limits the depth of the dependency graph visualisation; defaults to 1.

Tree output display example

The command 66-info -T boot as root user on the Obarun default system displays the following where boot is the tree used to properly boot the machine:

   
	               boot           
	Initialized: yes | Current: no
	Contains:       | Enabled: no
	├─(0,Enabled,oneshot) system-hostname
	├─(0,Enabled,oneshot) mount-run
	├─(0,Enabled,oneshot) populate-run
	├─(0,Enabled,oneshot) mount-tmp
	├─(0,Enabled,oneshot) populate-tmp
	├─(0,Enabled,oneshot) mount-proc
	├─(0,Enabled,oneshot) mount-sys
	├─(0,Enabled,oneshot) populate-sys
	├─(0,Enabled,oneshot) mount-dev
	├─(0,Enabled,oneshot) mount-pts
	├─(0,Enabled,oneshot) mount-shm
	├─(0,Enabled,oneshot) populate-dev
	├─(0,Enabled,bundle) 00
	├─(0,Enabled,oneshot) modules-kernel
	├─(490,Enabled,longrun) udevd
	├─(0,Enabled,oneshot) udevadm
	├─(0,Enabled,oneshot) devices-crypttab
	├─(0,Enabled,oneshot) system-hwclock
	├─(0,Enabled,oneshot) system-random
	├─(0,Enabled,oneshot) modules-system
	├─(0,Enabled,oneshot) system-sysctl
	├─(0,Enabled,oneshot) system-fontnkey
	├─(0,Enabled,oneshot) devices-dmraid
	├─(0,Enabled,oneshot) devices-btrfs
	├─(0,Enabled,oneshot) devices-lvm
	├─(0,Enabled,bundle) system-Devices
	├─(0,Enabled,oneshot) system-fsck
	├─(0,Enabled,oneshot) mount-fstab
	├─(0,Enabled,bundle) all-System
	├─(0,Enabled,oneshot) mount-rw
	├─(0,Enabled,oneshot) local-iptables
	├─(0,Enabled,oneshot) local-ip6tables
	├─(0,Enabled,oneshot) local-loop
	├─(0,Enabled,oneshot) local-time
	├─(0,Enabled,oneshot) local-authfiles
	├─(0,Enabled,oneshot) local-tmpfiles
	├─(0,Enabled,oneshot) local-rc
	├─(0,Enabled,oneshot) local-dmesg
	├─(0,Enabled,bundle) all-Local
	├─(0,Enabled,oneshot) mount-cgroups
	├─(0,Enabled,oneshot) mount-swap
	├─(0,Enabled,oneshot) mount-zfs
	├─(0,Enabled,bundle) all-Mount
	├─(0,Enabled,oneshot) all-Runtime
	├─(0,Enabled,bundle) All
	└─(254,Enabled,classic) tty12

By default the first service displayed is the first service started, the second one is the second started and so on.

The first line give you the name of the tree, Initialized tells if the tree was initialized with 66-init tool, Current tells if the tree is the current one or not—see 66-tree -c and Enabled reveals the state of the tree—see 66-tree -E. For each service the first number found between '()' bracket is the corresponding pid of the service, the second one is the state of the service, the type of the service is shown next to it. Finally the name of the service is displayed.

By default the dependency graph is rendered in order of execution. In this example the 'classic' tty12 is the last finished service and 'oneshot' filesystem is the first one executed. You can reverse the rendered order with the -r option.

Service output display example

The command sudo 66-info -S -d3 00 displays the following where 00 is the name of the service:

	                00                     
	on tree : boot
	status : Enabled, nothing to display
	type : bundle
	description : Set the hostname and mount filesystem
	source : %%service_system%%/boot/mount/
	run at : %%livedir%%/tree/0/boot/servicedirs/00
	             contents                  
	├─(0,Enabled,oneshot) system-hostname
	├─(0,Enabled,oneshot) mount-run
	├─(0,Enabled,oneshot) populate-run
	│ └─(0,Enabled,oneshot) mount-run
	├─(0,Enabled,oneshot) mount-tmp
	├─(0,Enabled,oneshot) populate-tmp
	│ └─(0,Enabled,oneshot) mount-tmp
	├─(0,Enabled,oneshot) mount-proc
	├─(0,Enabled,oneshot) mount-sys
	│ └─(0,Enabled,oneshot) mount-proc
	├─(0,Enabled,oneshot) populate-sys
	│ ├─(0,Enabled,oneshot) mount-proc
	│ └─(0,Enabled,oneshot) mount-sys
	├─(0,Enabled,oneshot) mount-dev
	│ └─(0,Enabled,oneshot) mount-sys
	├─(0,Enabled,oneshot) mount-pts
	│ └─(0,Enabled,oneshot) mount-dev
	├─(0,Enabled,oneshot) mount-shm
	│ └─(0,Enabled,oneshot) mount-dev
	└─(0,Enabled,oneshot) populate-dev
	  └─(0,Enabled,oneshot) mount-dev

Let's take another example, the command sudo 66-info -S -p5 ntpd displays the following:

	                ntpd                     
	on tree : root
	status : Disabled, up (pid 786) 2380 seconds
	type : classic
	description : ntpd daemon
	source : %%service_adm%%
	run at : %%livedir%%/scandir/0/ntpd
	            dependencies                 
	└─(785,Disabled,classic) ntpd-log
	              scripts                    
	start script : foreground { mkdir -p  -m 0755 ${dir_run} } 
	execl-cmdline -s { ntpd ${cmd_args} } 
	            environment                  
	dir_run=!/run/openntpd
	cmd_args=!-d -s
	              logger                     
	logger associated : ntpd-log
	log destination : %%system_log%%/ntpd 
	             log file                    	
	2019-03-18 06:50:21.749572500  adjtimex returns frequency of 0.000000ppm
	2019-03-18 06:50:21.764241500  ntp engine ready
	2019-03-18 06:50:21.847440500  adjtimex adjusted frequency by 16.428986ppm
	2019-03-18 06:50:21.847479500  set local clock to Mon Mar 18 06:50:21 +11 2019 (offset 0.000000s)

In our case :

ntpd : name of the service. Main section where general informations is displayed.
on tree : service enable on tree root.
status : status of the service.
type : type of the service.
description : short description of the service.
source : origin of the frontend service file used to enable the service.
run at : location of the service into the scandir.
dependencies : dependencies informations section. This section will display a graphical tree on the service dependencies.
scripts : scripts informations section. This will display the command executed at start and stop process.
start script : command line executed at start process. If a stop section was set an additionnal field called stop script will be displayed with the corresponding command line executed at stop process.
environment : environment informations section. Display the environment variables set at %%service_admconf%% or $HOME/%%service_userconf%% depending of the owner of the process.
logger : logger informations section.
logger associated : name of the service logger.
log destination : destination of the logger file.
the last part display the last 5 line of the logger file.

Note: 66-info use color to output the informations, the previous examples do not reflect the veritable output concerning the colors.