Joerg Anslik wrote:
> Hi,
>
>
>> That would be a good argument for not including a DISABLE facility :-)
>> Sometimes simplicity is the better solution and features only add
>> confusion.
>
>
> I'd suggest I just start implementing checks rsp. on-the-fly merging
> of /etc/defaults/services and /etc/services. Once I'm familiar with
> the corresponding code, we could give whatever disable feature we want
> some second thoughts, but for now, I think it's best to leave it out.
What about having, say, "servicesd" daemon merging
/etc/defaults/services and /etc/services.conf on startup or on SIGHUP
and feeding all the readers of /etc/services (PIPE | ProcFSNode |
whatever-special-node) with up-to-date data? As an additional goal,
servicesd could even speedup things by caching data.
> Anyway, if someone (let's call him "Matt") says, do it THIS WAY to
> disable entries, I won't regret. :)
--
Dennis Melentyev
http://www.melentyev.kiev.ua/dennis