I'm new to systemd/systemctl as well.
I had a long delay with NetworkManager-wait-online.service and the delay
referred me to systemctl
systemctl feels more like working with a database. Interesting system to
get acquainted with.
On Sat, Feb 17, 2018 at 1:54 PM, john doe wrote:
> On 2/17/201
On 2/17/2018 1:53 PM, Jeffrin Jose wrote:
are you looking for path of a command ? "whereis systemctl"may be "systemd" is starting
point for all scripts during startupcheck "cd /etc/init.d/" which is atleast one place for startup
scripts
For service files:
/lib/systemd/system
--
John Doe
Thanks for all the great info. Looks like I have some reading to do.
You don't need to know that. What you need to know is how to reproduce
the output after login. As root run dmesg|grep -i "error" and also run
dmesg|grep -i "warning" and finally run dmesg|grep -i "fatal". You
might want to save those runs to files or maybe not.
On Sat, 17 Feb 2018,
Legion Po
Legion Post #52 wrote:
> Ok, I have a question. What is that script called that runs when you
> start up the system that causes all that text to come across the
> monitor? In that text I see a failure that references "systemct1
> network service" but can't find where that is located to check it ou
are you looking for path of a command ? "whereis systemctl"may be "systemd"
is starting point for all scripts during startupcheck "cd /etc/init.d/" which
is atleast one place for startup scripts
--software engineerrajagiri school of engineering and technology
On Saturday 17 February 2018, 6
6 matches
Mail list logo
