Hello,
I am experimenting a little with systemd and trying to define a new
intermediate runlevel, a runlevel between basic.target and
multi-user.target. This means that I want the services which are required
by my new runlevel to be started after all services from basic.target have
been started
Hello,
I am experimenting a little with systemd and trying to define a new
intermediate runlevel, a runlevel between basic.target and
multi-user.target. This means that I want the services which are
required
by my new runlevel to be started after all services from basic.target
have
been
Hello,
So, if the original unit file multi-user.target contains
After=basic.target rescue.service rescue.target
this after does not really mean anything and jobs wanted or required
by
multi-user.target can already be started when some jobs from
basic.target
have not been started???
Hello,
So, if the original unit file multi-user.target contains
After=basic.target rescue.service rescue.target
this after does not really mean anything and jobs wanted or required
by
multi-user.target can already be started when some jobs from
basic.target
have not been started???
Hello,
Then, I still do not understand why my definition of a new target did
not
work. What is the difference between multi-user.target waiting for
basic.target on the one hand and new.target waiting for basic.target and
multi-user.target waiting for new.target on the other hand, aside from
Hello,
Dimitri John Ledkov dimitri.j.led...@intel.com wrote:
I want a program to be run at boot time without any other systemd
services
starting concurrently. The program needs the services from basic.target
and may influence everything in multi-user.target and later targets, so
I
guess
Hello,
I wrote:
Sounds like you want to create intermediate.target, change
default.target to point at it, boot all the way up to
intermediate.target, and at that point isolate or start
multi-user.target.
I chose that solution, because from all possible solutions for the
desired boot
Hello,
Why does systemd start this service before /var is mounted, though the
service should be executed after remote-fs.target, and remote-fs.target
comes after local-fs.target?
Because remote-fs.target is not part of initial transaction.
And why is this different in my
Hello,
/usr/local/sbin/local is a bash script which calls several functions.
When
one of these functions fails, i.e. returns another value than zero, the
script calls this function:
die() {
STRING=$1
echo 2 Error occured in function ${STRING}
echo Press any key to reboot (sorry for
Hello,
I created a new target, defined by this target file:
[Unit]
Description=LOCAL
Requires=multi-user.target
After=multi-user.target
Conflicts=rescue.target
AllowIsolate=yes
The new target only depends on one new service. The service is defined by:
[Unit]
Description=LOCAL
Hello,
while searching through the internet for information on how to change
the session type after it has already been started, I found this:
https://github.com/systemd/systemd/issues/14489
Now I am wondering how SetType is supposed to be used. To try it out, I
logged in on textual tty and
11 matches
Mail list logo
