freebsd stable - Aug 2015 - (once again) freebsd-update cron and man whatis

Hi,

I wrote about this some time ago here on the list:
http://marc.info/?l=freebsd-stable&m=143556175104543&w=3

I am on 10.1-RELEASE-p17 amd64 now, and the problem still remains:

- freebsd-update cron fetches new updates and notifies me by email. (ok)
- I run freebsd-update install and reboot. freebsd-version shows the
  correct version. (ok)
- Next morning I get notification from freebsd-cron for the same update
  I installed yesterday, but only for /usr/share/man/whatis. (not ok)

Not 100% sure, but I think that running both freebsd-fetch and
freebsd-install from an interactive ssh session corrects this until
the next update.

Are there any differences between freebsd-update cron and
freebsd-update fetch, apart from random time offset?

Regards,
-- 
Marko Cupa?
https://www.mimar.rs/

On 08/11/15 08:21, Marko Cupa? wrote:
> - Next morning I get notification from freebsd-cron for the same update
>   I installed yesterday, but only for /usr/share/man/whatis. (not ok)
Did you by any chance happend to run the weekly/320.makewhatis periodic
script that night?   It is enabled by default.  However, you shouldn't
need it if you maintain your system entirely through freebsd-update.
> Are there any differences between freebsd-update cron and
> freebsd-update fetch, apart from random time offset?
freebsd-update is a shell script, so it's fairly easy to see the
difference between 'fetch' and 'cron' -- look for the functions
'cmd_fetch()' and 'cmd_cron()' in the code (they're right
next to each
other.)

The differences are:

   'fetch' tests that is is connected to a tty and complains about not
           being run interactively if not

   'cron'  sleeps for a random number of seconds up to 1 hour, and it
           logs everything it does to a temporary file in order to mail
           back a report to the user if needed.

Otherwise, they both call exactly the same 'fetch_check_params()' and
'fetch_run()' functions.

	Cheers,

	Matthew


# Fetch command.  Make sure that we're being called
# interactively, then run fetch_check_params and fetch_run
cmd_fetch () {
        if [ ! -t 0 -a $NOTTYOK -eq 0 ]; then
                echo -n "`basename $0` fetch should not "
                echo "be run non-interactively."
                echo "Run `basename $0` cron instead."
                exit 1
        fi
        fetch_check_params
        fetch_run || exit 1
}

# Cron command.  Make sure the parameters are sensible; wait
# rand(3600) seconds; then fetch updates.  While fetching updates,
# send output to a temporary file; only print that file if the
# fetching failed.
cmd_cron () {
        fetch_check_params
        sleep `jot -r 1 0 3600`

        TMPFILE=`mktemp /tmp/freebsd-update.XXXXXX` || exit 1
        if ! fetch_run >> ${TMPFILE} ||
            ! grep -q "No updates needed" ${TMPFILE} ||
            [ ${VERBOSELEVEL} = "debug" ]; then
                mail -s "`hostname` security updates" ${MAILTO} <
${TMPFILE}
        fi

        rm ${TMPFILE}
}


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: OpenPGP digital signature
URL:
<http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20150811/a6ae1e18/attachment.bin>