Ticket #288 (closed defect: fixed)
initng for users
| Reported by: | denis.knauf@… | Owned by: | initng@… |
|---|---|---|---|
| Priority: | high | Milestone: | |
| Component: | Feature Requests Initng Source | Version: | unspecified |
| Severity: | normal | Keywords: | |
| Cc: |
Description (last modified by trigger) (diff)
at the moment, only the system can user initng, not the users. no my suggestion: if initng has started all services, it looks, which user is member in group "initng". then it looks, which of these users have a directory "~user/.initng" (, or "/var/spool/initng/user"). now it starts all services, which are listed in a runlevel-file of the user. but on every start, first, initng change the uid and gid to the user-uid and user-main-gid. the reason for this: i want to make it possible, that users can start on booting own services. doodled or fetchmail are possible to start as daemon, which are must be started as this user, how wants this. the indirect-way, a daemon/doodled, which starts the services for the users, is unclean and unflexibel.
Change History
comment:2 Changed 8 years ago by neuron@…
that'd need a lot of work, as you'd also need to have support for multiple users.
I imagine it wouldn't be too hard to do with a plugin, and starting daemons as user/daemon, and uid/gid set to the correct user. And very simply if a user try to start a system service he'd get a "permission denied" or another failure.
ngc must be suided and must control, which user there try to use it. options are user/system-specific. if a user-service depends on a system-service, which isn't started, the user-service will not be started. only if the system-service runs, user-service can run. users aren't allowed to start system-services.