This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
Mike, > Here you go: > bash-2.03$ who am i > ldm pts/2 Apr 28 18:19 (metsupport) > bash-2.03$ pwd > /export/caymus2r/ldm > bash-2.03$ fgrep LOG_LDM $HOME/src/config.status > s,@LOG_LDM@,|#_!!_#|local1,g > s,^\([ #]*\)[^ ]*\([ ]*LOG_LDM\)[ (].*,\1define\2 LOG_locAl1 , > bash-2.03$ echo local1 | tr "[a-z]" "[A-Z]" > LOCAL1 > bash-2.03$ The sed(1) command s,^\([ #]*\)[^ ]*\([ ]*LOG_LDM\)[ (].*,\1define\2 LOG_locAl1 , in the file "config.status" is responsible for your problem. It should, instead, be s,^\([ #]*\)[^ ]*\([ ]*LOG_LDM\)[ (].*,\1define\2 LOG_LOCAL1 , I have no idea why it isn't. To expedite the process, may I log onto your system as the LDM user? I would be coming from gilda.unidata.ucar.edu (128.117.156.30) and would need the hostname, username (ldm?) and the password. Alternatively, if you allow ssh(1) access, then adding the following line to the file ~ldm/.ssh/authorized_keys should work: ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAIEA5v3LwC2R6kdWnCVPVQf5e7I8F2qAgrFytbk7NYdkdhG+ViSfg050KtCaeH7BFI/T+ceL3a39ZW0Z/5mz+w3C2bvRH8NkyodEd3WNCCl1a72L+FDOczld3Pi0PU5Hp+UPY8NEA6H0PspEKCYCFfDVhOG3pkquB2zjhBlW9XzC39k= steve@*.unidata.ucar.edu It's all one line with two spaces: one between "rsa" and "AAAAB..." and another between "9k=" and "steve@...". Regards, Steve Emmerson Ticket Details =================== Ticket ID: RDQ-217349 Department: Support LDM Priority: Normal Status: On Hold