Hi Martin, On Sat, Nov 21, 2020 at 08:48:51PM -0600, Martin McCormick wrote: > find . -name "*" -exec ls -l {} \; \ > |grep -F / \ > | awk ' { total += $5 } END { print total }' > > That usually just adds the sizes of all the files it can > find all the way through the tree. > > If this is not an accurate way to determine how many > bytes there are in a directory then that would be the reason for > the discrepancy.
The same file can be reached by multiple names. So by doing this you end up, in this case, with a ~256x amplification. A simple "du -sh" does a better job here! > cron only works in the time zone for wherever the TZ for the > system is set. Ah, I see. I've never tried it but I believe that systemd timers can have a time spec that includes time zone, so you can set timers that fire on a different time zone to that used by the rest of the system. $ systemd-analyze calendar '11:00 Europe/London' Original form: 11:00 Europe/London Normalized form: *-*-* 11:00:00 Europe/London Next elapse: Sun 2020-11-22 11:00:00 UTC From now: 6h left Cheers, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting