- To: cfm@maine.com
- Subject: Re: [Barry@bstent.com: [mv] MV 4.04 catalog error.log]
- From: Barry Treahy <Barry@BSTent.com>
- Date: Sat, 13 May 2000 20:56:43 -0700
- References: <20000513203127.A30205@maine.com> <391DF6B3.D028F537@BSTent.com> <20000513214227.A30431@maine.com>
I see it but only for the global reporting, not for the individual catalogs.
hinj:/ibin/minivend4/bin# grep error.log minivend
$Global::InitialErrorFile = $Global::ErrorFile = "$Global::VendRoot/error.log";
-d dir, --dir=dir directory for VendRoot (minivend.cfg, error.log, etc.)
$Global::ErrorFile = "$Global::VendRoot/error.log"
Barry
cfm@maine.com wrote:
> I'm looking at 4.03. In that case:
>
> grep error.log bin/minivend
>
> Worst case you can just hard code it in there.
>
> On Sat, May 13, 2000 at 05:43:31PM -0700, Barry Treahy wrote:
> > cfm@maine.com wrote:
> >
> > > Did you check /var/log?
> > >
> > > I'm thinking I saw something about that in CHANGES.
> >
> > Thanks for idea, but I just looked and nothing new there... If did a quick find across
> > my home system and didn't find much int he way of error.log. Its almost as if it is
> > being supressed, perhaps incorrect permissions, I do not know.
> >
> > hinj:/ibin/minivend4# find / -name 'error.log' -print
> > /mv_catalogs/kss/error.log
> > /mv_catalogs/awards/error.log
> > /ibin/minivend4/error.log
> > /ibin/minivend/error.log
> >
> > The first is a MV3 catalog and the second in awards was a file that I created and set
> > permissions on in a vain attempt to kick start is it were like syslog files. The
> > remaining two are just the standard server logs that have no helpful info.
> >
> > Barry
> >
> >
>
> --
>
> Christopher F. Miller, Publisher cfm@maine.com
> MaineStreet Communications, Inc 208 Portland Road, Gray, ME 04039
> 1.207.657.5078 http://www.maine.com/
> Database publishing, e-commerce, office/internet integration, Debian linux.
