turn off the read data block timeouts. This was inspired by the same fix
in sendmail-8.7, but the code in this area is somewhat different. (8.7
is much more sensible). This will stop the infamous
"timeout waiting for input during message body read" on long running jobs,
eg: /etc/daily | mail root.
`interesting' feature of syslogd turned up. It calls getbootfile() for each
log entry. Since the kernel makefile now changes kern.bootfile when doing
a 'make install', it's quite startling to see the syslog lines change.
This change makes it call getbootfile() once at startup and cache it,
saving a syscall per loop, and keeping something a little more asthetically
pleasing in /var/log/messages...
Here is some patches to IPXrouted. It does the following:
Always use the sap port in the destination address of sap broadcasts.
Clear the host part of network addresses so that routes will really
be deleted in the kernel.
rather out of date.. it even suggested that it was ppp-2.1.1 still :-)
I've selected some bits from the README files and pre-pended it so that
at least reading it tells you _something_ about the recent history.
o Caution against use of `W' options in label/partition screens (dangerous!)
o Make various types of debugging dreck conditionalize on DEBUG flag
o Make a fake /var/db/mountdbtab file so new system doesn't complain
o Apply uniform permissions to entire /usr/X11R6 tree.
o Set erase character to ^H for all interactive commands.
o Don't panic if user exits upgrade shell, reboot.
o Document dangers of `W' options in help screens also.
Since msdosfs is part of the base system, it's not wise to rely on
something like mtools to provide this functionality.
This utility is the agreed fix for PR # misc/804 fdformat did not ...
or "defaultroute"... That's forgivable I guess, but the silly thing
didn't have any way to _enable_ the options either! :-(
This now enables them by default.
Obtained from: ppp-2.3a0
1. Fix the bogon I introduced that made some root filesystems fail to be
made with `unable to make filesystem on sd1s1a' or some such error
message.
2. Latest installment in the never-ending chapter on making FTP do the right
thing on a cruel internet.
3. Make `express install' a truly express install and split off what it used
to do into a `novice install' that's even more geared to the novice
by asking questions in order, rather than forcing them through the menu
interface.
4. Make anonymous FTP setup truly DTRT.
5. Build lndir directly into sysinstall and make the novice install offer
to set up the ports tree. Also make the ports setup truly explanatory
about what it's doing, and always link the ports destination to /usr/ports
if necessary so that bsd.port.mk doesn't need to be tweaked.
This causes:
1: inetd to clear it's getlogin() name at startup (in case the sysadmin
logged in and su'ed to root and restarted inetd)
2: inetd to start each spawned process in it's own session.
3: inetd to call setlogin() on non-root processes (eg: uucp for uucico)
4: log failures more extensively
This means that root spawned processes from inetd remain responsible for
setting their login name if they change their uid. (eg: rshd, login, etc).
If they do not do so, it is safer for them to have no "login name" than a
wrong one (like "root") because the getlogin() system call is documented
as "secure" on 4.4BSD. inetd when started from /etc/rc would have no login
name anyway, so this isn't really a change - it's making it consistant with
the bootup state...
The setsid() change *may* cause something to break that is doing a setsid()
itself and checking the result - it will fail now because it's already been
done. The consensis seems to be that this is unlikely. David G. thinks
this is acceptable as it is cleaner from an architectural point of view.
