I really hate to admit it, but there was a type, in the directory
name, had an extra letter on it. (I'm dumb)
Thanks for all the suggestions otherwise, I was really confused where
to begin with the stat error. So thanks for clearing that up.
On Nov 18, 2008, at 10:33 AM, Kevin Keane wrote
Double-check spelling and other details. The error message pretty
clearly includes the notes "no such file or directory" which means that,
as far as Bacula is concerned, the file does not exist. It's also not a
permission problem - else you'd see something about "permission denied"
or a similar
On Tue, Nov 18, 2008 at 11:13 AM, Mike Holden <[EMAIL PROTECTED]> wrote:
> Either the directories or files don't exist, or permissions on the
> directories disallow the current user to look inside them. If the files
> and dirs really do exist, then check the permissions on all the
> directories /,
It DOES exist.
drwxrwsr-x 4 user group 4096 Nov 18 16:02 bin
On Nov 18, 2008, at 10:06 AM, John Drescher wrote:
> On Tue, Nov 18, 2008 at 10:46 AM, Charlie Reddington
> <[EMAIL PROTECTED]> wrote:
>> Okay, that makes sense. So if the file / directory DOES exist, with
>> proper read permissions,
Either the directories or files don't exist, or permissions on the
directories disallow the current user to look inside them. If the files
and dirs really do exist, then check the permissions on all the
directories /, /directory, /directory/directory, /driectory/directory/zips
etc with ls -ld and
On Tue, Nov 18, 2008 at 10:46 AM, Charlie Reddington
<[EMAIL PROTECTED]> wrote:
> Okay, that makes sense. So if the file / directory DOES exist, with
> proper read permissions, what can be causing me this error?
>
What about
/directory/directory/bin
John
-
Okay, that makes sense. So if the file / directory DOES exist, with
proper read permissions, what can be causing me this error?
Thanks,
- charlie -
On Nov 18, 2008, at 9:29 AM, Kevin Keane wrote:
> "Could not stat" is Unix-speak for "file not found". The reason many
> programs call it "could
"Could not stat" is Unix-speak for "file not found". The reason many
programs call it "could not stat" is that the system call to find out
basic information about a file (time stamp, size, etc.) is called stat -
and when stat fails, it usually means that the file or directory doesn't
exist.
Ch
Hi,
Everything looks to be running pretty smooth, but I have one server
which is giving me some problems. It looks like it's backing up
some of the stuff, but it's missing some.
Here's the log after the backup runs. I kind of expected errors with
the *.pl and *.sh files, but the other o
