On Thu, Nov 21, 2024 at 1:02 AM Michael Hennebry < henne...@web.cs.ndsu.nodak.edu> wrote:
> On Thu, 21 Nov 2024, Tim via users wrote: > > > Person comes along with my THIS won't do THAT. You spend some time > > diagnosing, then downloading a few months worth of updates that they > > never did (which is always a slow thing, no matter how fast your > > internet is). Reboot. More downloads... Reboot. It's often all that > > was needed doing. It's regularly 1-2 hours. > > Just out of curiosity, how often did you discover > that the THIS was not supposed to do THAT? > For me, it was usually that THIS claimed to do THAT, but failed due to a resource constraint, violation of a policy (SELINUX), or was given bad input data. Many of the programs I wrote had more code checking arguments than the actual calculations required, but they were used in batch pipelines where it was much easier to sort out an error due to a bad argument than to sort out the resulting mess when incorrect output was fed to the pipeline. -- George N. White III
-- _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
