Hey, Gavin, Ypnose and the list, Gavin wrote: |Finally to sign off, I'd just like to say that I don't technically require |user/host-specific settings at all. I simply like being able to source |passwords for multiple accounts from a separate file, so that \
|Gavin Ypnose wrote: |And BTW, I second Gavin for the separate password file. :) |Y. on the [next] branch you'll find the possibility to set the *netrc-load* option, which will expand the path of its value if any is set, otherwise that of $NETRC if that is set, otherwise ~/.netc. The `netrc' command acts like a cache -- when called (without args or with `show') it lists the cache, calling `netrc clear' will reset it, so that updates on the .netrc file can be incorporated. The parser supports anything that is mentioned by the NetBSD ftp(1) .netrc file section (including 'macdef'), but all we really care about is 'machine HOST', 'login USER', 'password PASS' (or 'passwd PASS'), the rest is thrown away, just as is anything after 'default'; and comments are not allowed (what a shitty syntax!). Because we are so dumb we *require* that only the user can access the file. >From a bit of testing it works quite well (not so much testing since i've seen a crash in credential lookup, which took almost an hour), i.e., this message will be backed by credentials from ~/.netrc; of course, any (negative) test would be appreciated. I plan to release v14.7.1 on Tuesday. Ciao, and have a nice rest-weekend! --steffen ------------------------------------------------------------------------------ HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in Your Big Data with HPCC Systems Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. Leverages Graph Analysis for Fast Processing & Easy Data Exploration http://p.sf.net/sfu/hpccsystems _______________________________________________ S-nail-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/s-nail-users
