Re: Adding makemandb as build tool for man.db

[Robert Swindells <rjs%fdy2.co.uk@localhost>]

userm57%yahoo.com@localhost wrote:
>On 10/9/18 3:02 AM, Martin Husemann wrote:
>> On Tue, Oct 09, 2018 at 09:46:48AM +0100, David Brownlee wrote:
>>> On lower powered (and particularly lower memory boxes), the makemandb
>>> on first boot after install can run for some time and significantly
>>> affect the performance of the system (in extreme cases for several
>>> hours).
>> It is not so much memory, but slow disk access that makes it painfull.
>> Most sparc machines do pretty well, mac68k is a disaster.
>>
>> Even if you distribute the database, it will take some serious time on
>> each boot to check it is up to date.
>>
>> Maybe we should add an rc.conf option to delay it after boot (i.e. sleep
>> three hours and only then start the man page check), defaulting to 0 (i.e.
>> no delay) on most architectures but make sysinst configure it to a few
>> hours on slow architectures.
>
>Maybe add a rc.conf option to disable man page processing
>altogether?

We already have one:

makemandb=NO

You also need a line in /etc/daily.conf though to keep it turned off:

run_makemandb=NO

>> We should also offer usefull (and documented) slow-systems ssh{d}
>> default configurations, even if they are "unsafe" from a modern world's
>> PoV.
>
>ok, but if it's "unsafe", why use it?  On an internal network,
>with slow systems all on the same switch and protected from the
>public Internet, there's really no advantage to using ssh/scp
>instead of telnet/ftp on slow systems.  I agree that telnet and
>authenticated ftp shouldn't be used on systems that are exposed
>to the public Internet.  I see some sites (such as ftp.gnu.org)
>talking now about eliminating all clear-text protocols, even
>anonymous ftp, and that doesn't make any sense, especially for
>slow clients.  Besides, properly configured anonymous ftp isn't
>any worse than http.

I still use ftp & rlogin within my home network.