Re: Bug in cronscript?

[Colin Watson <cjwatson@debian.org>]

On Thu, Jul 18, 2002 at 01:13:04AM +0200, j2 wrote:
> Colin Watson wrote:
> > Oh, you mean that it fails when you run the script by hand too, not just
> > when it's run from cron? Interesting. I wonder if your /bin/sh is
> > something strange.
> 
> Should  be a standard Woody install?

So if you didn't install ash then it will be normal. OK. (ash offers
optionally to install itself as /bin/sh.)

> 6199  stat64("/var/lib/locate/locatedb", 0xbffffc3c) = -1 ENOENT (No such
> file or directory)
> 6199  lstat64("/var/lib/locate/locatedb.n", {st_mode=S_IFREG|0644,
> st_size=10, ...}) = 0
> 6199  lstat64("/var/lib/locate/locatedb", 0xbffffa7c) = -1 ENOENT (No such
> file or directory)
> 6199  rename("/var/lib/locate/locatedb.n", "/var/lib/locate/locatedb") = 0
> 6199  _exit(0)                          = ?

That looks like the very last stage, after updatedb has (or hasn't)
scanned the filesystem, so it's hard to tell what's going on just from
that.

Oh, wait. I've just realized that updatedb is a shell script ... perhaps
you could instead change 'updatedb' in /etc/cron.daily/find to 'sh -x
/usr/bin/updatedb', remove the '2>/dev/null', and send me the output?
You'll probably get some permission denied errors from find, but you can
ignore those.

-- 
Colin Watson                                  [cjwatson@flatline.org.uk]


-- 
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org