-----Original Message----- From: Craig A. Berry [mailto:[EMAIL PROTECTED]] Sent: Sunday, 1 December 2002 5:51 AM To: Keirnan, Paul Cc: '[EMAIL PROTECTED]' Subject: Re: A novice's first VMS build
Craig wrote: >This is something that definitely needs looking into. I think we >frequently see failures here for non-western time zones, or perhaps it's >anywhere SYS$TIMEZONE_DIFFERENTIAL is positive rather than negative. Thanks >for the report. I'm in Sydney, which during daylight saving is on +11:00 hrs. SYS$TIMEZONE_DIFFERENTIAL = 39600 >>Overall, quite successful, and as a Perl novice I learnt a fair bit >>about how the build environment is put together. >Well, you sure got a heck of a lot farther than I did the first time I tried >to build it. The only reason I got anywhere was because I have been following this list for the last six months. Prior to this I have been using the PCSI install. >==================================================================== >I guess we never gave much thought to testing under an account different > from the one that did the build. Was there a particular reason you did >that? As of 5.8.0 the test suite takes considerable care to downgrade privs >to the minimum required, so you're unlikely to run into trouble testing from >a privileged account. However, I can appreciate that a savvy system manager >might prefer not to do so. In that case I'd recommend building and testing >under a non-prived account and then logging in as SYSTEM to do the install; >you shouldn't see any ownership problems if you do that. There are a limited number of us in Systems/Middleware/DBA who have privileged accounts. The installation standard is that everyone works in their own account where possible. It is years since I logged in as SYSTEM, though I do submit batch jobs to run under that account. However infrastructure (directories, scripts, programs, data, etc) should not be owned by individuals. They should be owned either by SYSTEM, or a generic account created for the purpose, such as PERL_MGR. It was (to me) natural therefore, when I created a build directory to make that directory owned by SYSTEM, while working in my own account. The build worked fine. The test however didn't get far. My first action was to give all files and directories W:RWED, but that still gave a couple of errors, so I reset the ownership of everything (to me). What I will do next time, is to leave everything as SYSTEM, and submit the MMS/MMK runs to batch as SYSTEM. >>custom PERL_SETUP.COM snipped. >But this procedure as it exists is really just a shim >that's used for testing and installation and it only serves >production use by providing examples of the symbol and logical >creations. Yes. Thank you for that. I will rename what I have in SYS$STARTUP to be PERL_STARTUP.COM so that it doesn't get in the way of build/test/installs. Regards, Paul Keirnan -- ________________________________________ Craig A. Berry mailto:[EMAIL PROTECTED] "... getting out of a sonnet is much more difficult than getting in." Brad Leithauser
