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

[IDD #BJE-199821]: radar data

Hi Elmer,

> Any reboots, upgrades etc. would have to be done by our sysadmin group,
> and I have no idewa when they would be able to get to it.  We will keep
> trying.

OK, sounds good.

By the way, the one thing that I have never said because I assumed it was
obvious is that your 'ldm' user must have permission to write the output
file.  So, in:

FNEXRAD ^rad/NEXRCOMP/(...)/(...)_(........)_(....)
    FILE -close /data/radar/\1/\2/\2_\3_\4

'ldm' must be able to do a 'touch /data/radar/xxx'.  If 'ldm' can't write
to /data/radar, the action will fail.

Is it possible that you meant your action to be:

FNEXRAD ^rad/NEXRCOMP/(...)/(...)_(........)_(....)
    FILE -close data/radar/\1/\2/\2_\3_\4

Here you would be writing to ~ldm/data/radar/..., not /data/radar/...

Just an thought...

Unidata User Support                                    UCAR Unidata Program
(303) 497-8642                                                 P.O. Box 3000
address@hidden                                   Boulder, CO 80307
Unidata HomePage                       http://www.unidata.ucar.edu

Ticket Details
Ticket ID: BJE-199821
Department: Support IDD
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.