Not just rpcbind, but man db update as well

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



OK, I just updated my system and got the same
ridiculous delays I saw someone else complain about
recently. Not once, but twice. First when
it installed the new rpcbind, then second
when it ran the rpcbind scriptlet.

Worse than that, when I rebooted to make sure
everything was loaded from scratch and up to
date, the reboot hung for about 3 minutes
saying a start job was running for man-db-cache-update
(or something like that).

What kind of moronic decision is it to postpone
a reboot while updating the man db? If there is
anything less critical I have a hard time thinking
what it is.

For gosh sakes, keep a flag somewhere that says if
the man db is up to date and update it on a timer
when the system is back up again if required.
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux