/usr/lib/x86_64-linux-gnu/metview/metview_local.common is in metview 5.0.0~beta.1-1build1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 | # **************************** LICENSE START ***********************************
#
# Copyright 2012 ECMWF and INPE. This software is distributed under the terms
# of the Apache License version 2.0. In applying this license, ECMWF does not
# waive the privileges and immunities granted to it by virtue of its status as
# an Intergovernmental Organization or submit itself to any jurisdiction.
#
# ***************************** LICENSE END ************************************
# ================================================================
# 19980507/vk, rev 20030718/vk
#
# original file 'scripts/metview_local.example'
# - copied into 'scripts/metview_local.common' by 'mvbuild' script
# - copied into 'bin/metview_local.common' by 'make'
#----------------------------------------------------------------+
#-- If you have installed Metview with MARS_remote - to access -
#-- MARS database at ECMWF - then un-comment and customise the -
#-- following three lines according to the configuration of -
#-- your 'ECaccess Tools' installation (the values assigned here -
#-- are given only as examples): -
#----------------------------------------------------------------+
#
#ECACCESS_HOME=/usr/local/ecaccess-v2.0.3
#ECHOST=GatewayHost
#ECCERT_PORT=9443
#------------------------------------------------------+
#-- If you have problems with shared libraries then -
#-- uncomment and customise one of the following lines -
#-- (pick the one used in your Unix system) -
#------------------------------------------------------+
#
#LD_LIBRARY_PATH=/your/custom/libdir:$LD_LIBRARY_PATH
#LIBPATH=/your/custom/libdir:$LIBPATH
#LPATH=/your/custom/libdir:$LPATH
#LD_LIBRARYN32_PATH=/your/custom/libdir:$LD_LIBRARYN32_PATH
#-- If you have more problems with shared libraries then note that
#-- on some Linux systems 'xterm' does not inherit environment
#-- variable LD_LIBRARY_PATH (for some security reasons), but
#-- 'konsole' does. If this is the case in your environment then
#-- uncomment the line below to use 'konsole'.
#-- If this does not help then you need to change 's' bit in
#-- 'xterm' or 'konsole' executable file protections bits!
#--
#-- For more info, see:
#--
#-- http://dickey.his.com/xterm/xterm.faq.html#no_libpath
#--
#[ $METVIEW_VERSION = dev ] && METVIEW_CMD="konsole -nowelcome -e"
#-- editor help button browser config - used in src/WebAccess/WebAccess.cc
#MV_BROWSER_NAME=${MV_BROWSER_NAME:=firefox}
#MV_BROWSER_VERS=${MV_BROWSER_VERS:=5.1}
#--------------------------------------------------------+
#-- This one is for log files (the 7 lines in the end) -
#-- (note that you can also use the new flag -slog which -
#-- is available by default) -
#--------------------------------------------------------+
#
# BACKGROUND
# ----------
# Metview startup script has a flag called '-log'. By default
# this flag is dummy i.e. setting it has no effect.
#
# Sometimes you may need to know what is going on when Metview
# is running (e.g. you have a macro that fails in batch mode).
# In such cases you can configure Metview to be able to produce
# log files i.e. you can activate '-log' flag.
# (Or - starting from Metview 3.6-export - you can also try flag
# -slog which is a standard flag, available by default).
#
# WARNING
# -------
# Note that activating '-log' flag does not come free: reconfigured
# Metview requires twice the number of processes compared to default
# Metview because activating '-log' flag is done by executing each
# Metview module indirectly via a small script 'logrun' that handles
# log file operations.
#
# HOW
# ---
# Activating '-log' flag is simple: just uncomment the seven (7) last
# lines in this file. Remember to run 'make all' after editing!.
#
# EXAMPLE
# -------
# In an imaginary member state Memland they have a meteorological service
# called Memlandian Weather Institute (MWI). While building some operational
# macroes they run into strange problems and they decide to activate '-log'
# option. In directory ./scripts they do:
#
# vi metview_local.common #-- edit and uncomment the required lines
# make #-- update the modified file into bin dir
#
# and to activate their production version they install this change i.e.
# in directory ./src/MAKE they once more do:
#
# make install
#
# Then they run their problematic macro with '-log' flag...
#
# NOTE:
# ----
# When flag '-log' is used it must be given before flag '-b' because
# all parameters after '-b' are passed to the macro itself e.g.:
#
# metview -log mymacro -b /path/to/my/macro/mymacro
#
# Log files are created into $SCRATCH. In case your environment has not
# defined $SCRATCH Metview script sets $SCRATCH to point to $TMPDIR (or
# /tmp if $TMPDIR has not been set).
#
#-- uncomment the following seven lines to activate log files --
#if [ $METV_DEV = no ]
#then
# #-- enable flag '-log' i.e. execute modules through a script
# METVIEW_CMD="$METVIEW_BIN/logrun "
#fi
|