[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[LDM #ARA-679268]: Scour in LDM 6.13.6 not cleaning directories that 6.11.6 would

Anne,

> Thanks for the swift response. But at this point literally everything in
> our scour.conf file is coming up as not existing, even if navigating to it
> by hand on command line works fine.
> 
> More examples:
> ~ldm/data/decoders                      10
> ~ldm/data/decoders/nssl                 2
> 
> scour: directory ~ldm/data/decoders does not exist, skipping
> scour: directory ~ldm/data/decoders/nssl does not exist, skipping
> ldm@system: cd ~ldm/data/decoders
> /usr1/ldm/data/decoders
> ldm@system: ls
> acft/  csig/   ffa/  gfsmos/   hrcn/  isig/  ncon/  rdf/    scd/
> ship6hr/         ship_nomask/  taf/   warn/   wou/
> airm/  drops/  ffg/  gfsxmos/  hrly/  ltng/  nssl/  recon/  ship/
> ship6hr_nomask/  syn/          uair/  watch/  wstm/
> ldm@system: pwd
> /home/ftp/mntfil1v1/data/ldm2/decoders
> ldm@system: cd nssl
> /usr1/ldm/data/decoders/nssl
> ldm@system: pwd
> /home/ftp/mntfil1v1/data/ldm2/decoders/nssl
> ldm@system: ls
> ptype/  qpe/  qpe_01H/  qpe_q2rad_gc/  qpe_q2rd_gc/  rainrate/

Good lord! That means that this compound command in the scour(1) script:

        if edir=`cd "$dir" && /bin/pwd`; then
            : true
        else
            $LOGGER "directory $dir does not exist, skipping"
            continue
        fi

is taking the false path -- something that's arguably impossible.

We'd better check our assumptions. Please send me the output of the following 
commands, executed by the LDM user:

    id
    uname -a
    echo $SHELL
    /bin/pwd
    ls -ld ~ldm/data/decoders ~ldm/data/decoders/nssl

Also, and if you can, would you please replace the blank line at the top of the 
installed scour(1) script, "~ldm/bin/scour", with the line "#!/bin/bash" to see 
if that gets it to work.

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: ARA-679268
Department: Support LDM
Priority: Normal
Status: Closed
===================
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata 
inquiry tracking system and then made publicly available through the web.  If 
you do not want to have your interactions made available in this way, you must 
let us know in each email you send to us.