On Sun, Jul 31, 2022 at 02:16:30PM -0500, David Wright wrote: > On Sun 31 Jul 2022 at 06:28:18 (-0700), Paul Scott wrote: > > On 7/31/22 04:50, Curt wrote: > > > On 2022-07-31, <tomas@tuxteam.de> <tomas@tuxteam.de> wrote: > > > > > Doesn't it seem from the OP that the daemon doesn't > > > > > start? > > > > I interpret the process list in the original post as showing a > > > > running dyn_updater: > > > > > > > > > ps ax |grep dyn > > > > > 5237 ? Sl 170:43 dyn_updater > > > > > 5269 ? Sl 5:38 /usr/bin/dyn_updater --daemon start > > > > > 719685 pts/2 R+ 0:00 grep dyn > > > > You're right. I misread all that somehow. Documentation is > > > infuriatingly sparse, but mentions that the app's ( a *GUI* app) actvity > > > is logged to a file. Maybe the OP (who's disappeared anyway, as they > > > often do) should look there. > > > > I haven't disappeared. We're probably in different time zones and > > have different sleep schedules. > > > > I don't know about the GUI part of dyn_updater. It just site in my > > task bar and doesn't do anything when I click it. > > I'm just intrigued by how expensive dyn_updater is to run. Admittedly, > the machine has been up long enough to churn through 719685 processes, > but almost three hours CPU time to tell a daemon to spend five seconds > doing something; is everything OK? It seems to be from Oracle [1]. Possibly a Java abomination. Cheers [1] https://help.dyn.com/updater/ (Search for copyright and look at the small print at the page's bottom) -- t
Attachment:
signature.asc
Description: PGP signature