Hi
I have been scratching my head most of today over a problem with exicyclog ( it
also looks like the same problem is afflicting eximon). The version of Exim is
4.30
When I run exicyclog it pumps a load of info to stdio then just stops. The line
it stops at is
exim_path=`grep "^[$st]*exim_path" $config | sed "s/.*=[$st]*//"`
It looks like $config is not being defined. However if I run the script by
giving it the path to the configure file it goes on a little further ( eximon
responds the same way)
ie
./exicyclog /usr/local/exim/configure
lots of screen stuff snipped
./exicyclog: /usr/local/exim: cannot execute
./exicyclog: /usr/local/exim: cannot execute
/log: No such file or directory
So it looks the script isnt determining the location of my EXIM log file ( they
live in /var/adm/exim )
eximon is also doing the same thing. So I am guessing that resolving the problem
with exicyclog will solve the problem with eximon
I havent investigated any further as yet. Are any other Tru64 people seeing the
same problem?
#############################################
This week I be mainly fixing computers by not switching them on.
Gwen Pettigrew
Senior Computer Officer
School of Earth Ocean and Planetary Sciences
Cardiff University
DEPT WEB
www.earth.cf.ac.uk
Home page
www.ocean.cf.ac.uk/people/gwen
