svn commit: r288291 - head/etc

[Niclas Zeising]

On 2016-06-19 16:08, Cy Schubert wrote:
> In message <4e985ab9-0d98-a160-bdad-fa4924ddc5b3 at freebsd.org>, Niclas 
> Zeising writes:
>>
>> This is wrong, and how I discovered it.  ddb (/etc/rc.d/ddb) starts
>> before disks, and currently refuses to start on my systems with this
>> issue.  This means no crash dumps, unless I remember to manually start
>> it later in the boot process, so this is an issue.
> 
> ddb isn't a daemon. It's an interface into the kernel that configures DDB 
> properties. It runs and completes. And, yes, it is affected by limits not 
> being found in the path.

I think I misunderstood what you mean, I thought you meant nothing is
affected by this.  Apologies for that.

> 
> My point is, since there are no daemons, as per the definition of a daemon 
> (processes that become daemons and run in the background) prior to the 
> filesystems being run, to say that there would be differing systems 
> behavior before and after filesystems are started is presently false 
> (though technically true because one day we might have daemons started 
> before critical filesystems are mounted).

Agreed.  I understand if we are too late in the release cycle for 11 to
move limits to /bin, which seems like the best solutions.  Are there any
other reasons not to move /usr/bin/limits?

I wanted to bring this to attention, since it seems noone else has
noticed it, or cared enough about it.  It is nothing that stops me from
using FreeBSD, I will just have to remember to start ddb manually, or
run the commands in case of a panic.
Regards!
-- 
Niclas