Comments (2)
The start of rc.local and runparts has been changed, and moved, in this release to allow them to run in the background. Previously they ran in the foreground and blocked PID 1, meaning basically no calls to initctl
could be made from processes running in these scripts. However, since their introduction in Finit, they've always run at the end of runlevel S. So we're not likely to change the semantics now.
You write: "rc.local is run as the second thing in runlevel 2 (just after getty setup), not as the last thing as it should be." -- I'm not sure if "last thing" refers to runlevel 2 or S, but the only guarantee we can make is to run them after all run/tasks in runlevel S have completed, and the compromise right now is to run them in the change to the next runlevel. This can definitely be improved upon, e.g., to add a .conf flag to ask Finit to wait for them to complete before even attempting to start anything in a multiuser runlevel.
Now, as far as I can see, I've not made any statement about starting getty at the end of runlevel 2? They start in parallel with everything else in their declared runlevel(s), e.g., contrib/debian/finit.d/available/getty.conf
:
# Consoles to start getty on when system is up
tty [12345] /dev/tty1 linux noclear nowait
tty [2345] /dev/tty2 linux nowait
tty [2345] /dev/tty3 linux nowait
tty [2345] /dev/tty4 linux nowait
tty [2345] /dev/tty5 linux nowait
tty [2345] /dev/tty6 linux nowait
This is why progress output is disabled when leaving runlevel S, to avoid clobbering the console. There is also no point in waiting for Finit to show the progress of every background daemon starting up before allowing the user to log in. I'm just trying to explain how Finit works, we're not trying to be SysV init compatible or a 1:1 replacement, which I get the feeling you sort of are expecting here.
from finit.
I've changed the title of this issue to "Does finit start rc.local and gettys too early?" because I believe this was more of a question that would fit better in the Q&A section in Discussions instead of as a bug report. I believe have answered that question now and I've also checked with systemd, which behaves in a similar fashion (WantedBy=multi-user.target
), by default. Anything else is distribution specific and should probably not use rc.local
but a pure Finit run/task/service using the synchronization primitives we provide.
from finit.
Related Issues (20)
- task with untriggered condition in runlevel S blocks boot HOT 5
- unexpected service restart on initctl reload, notify-related? HOT 4
- dbus and runparts not working
- Finit v4.5 drops all but first word in sourced service environment
- All internal conditions get stuck in flux after initctl reload
- Explicit declaration of PID style readiness notification
- Variables declared with `set NAME=VAL` set in environment with leading `set `
- Build error using clang 17 on musl (call to undeclared function 'basename') HOT 1
- Processes depends on notify:pid did not stop when their parent process was killed HOT 3
- tmpfiles.d feature does not work for statically-linked Finit et al. HOT 2
- dBus server HOT 3
- finit hangs during system shutting down HOT 6
- Spell out unsupported command or change to initctl error string
- Mounting filesystems from /etc/finit "OK" even though mount call fails HOT 3
- sysctl with complex values fails HOT 1
- initctl touch does not respect -n flag
- initctl touch does not support template services
- Possible undefined behavior when --with-fstab=no is set HOT 3
- Parsing active consoles fails HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from finit.