On 4/7/23, Anssi Saari <a...@sci.fi> wrote: > Greg Wooledge <g...@wooledge.org> writes: > >> On Thu, Apr 06, 2023 at 05:45:08PM -0500, David Wright wrote: >>> Users (including root) write their crontabs anywhere they like, >>> typically in a directory like ~/.cron/. >> >> Is that... normal? I can't say I've ever seen anyone keep a private >> copy of their crontab in their home directory like that. > > I don't know if it's normal but sounds like a good practice, to have a > backup of your crontab. I've been bitten by this sometime when my old > shell provider retired a system and I had no copy of my crontab. My home > dir was not affected by that retirement since those were all NFS mounted > from a different server.
I like mine there. I haven't tried crontab yet, but I've put other things at that location. It's more easily transferable without having to look for or remember any personalizations. I think it was building via npm that made it a comfortable, memorable CHOICE. The .local directory is coming to mind quicker for me these days. /opt, too, thanks to [upstream?] Chrome educating me that it's a nice, empty, less trafficked location to quickly peek at specifically installed packages. There's also /usr/local that makes it easier to more quickly remember packages that are specifically installed favorites for whatever reason. Among /usr/local's potential plusses is that it's about root permissions whereas putting its same contents in .local means mixing root and user. Mixing directories of varying permissions is no biggie for seasoned users but can quickly mangle things for newer ones. I mangled mine a long time ago when I got the bright idea to "chown" my user's entire ~/. We.. try not to do that anymore. What a mess. :) It's all about available cognitive abilities while computing for my usage case.. Cindy :) N.B. because it might catch the eye of a curious newbie: I don't do npm these days. I had fun while the experience lasted. There were some scary security issues a couple years back because it's such a wide open space out there. NPM's security was serious enough that it was a US-CERT advisement. The original is still sitting in my inbox: https://www.cisa.gov/news-events/alerts/2021/10/22/malware-discovered-popular-npm-package-ua-parser-js -- Talking Rock, Pickens County, Georgia, USA * runs with birdseed *
