Define Files on FreeBSD...
Chad McWilliams
chad at computiprint.com
Thu Apr 28 06:11:15 PDT 2005
> #####
> When trying to define a file on FreeBSD filePro I get the
> following error:
>
>
> *** A System Error Has Occurred ***
>
> Cannot open file.
> /usr/appl/filepro/<file>/map: No such file or directory
> #####
>
> So, this tells us it's hitting ENOENT, or possibly one of
> several other errors. There are a limited amount of
> conditions that could cause this:
>
> 1) /usr/appl/filepro/<file>/map should exist already and an attempt at
> opening it without O_CREAT is failing.
>
> 2) /usr/appl/filepro/<file> is not being created itself prior to the
> creation of the map. I quote from the open(2) manpage:
>
> ENOENT A directory component in pathname does not exist or
> is a dangling symbolic link.
>
> Of course, all of this assumes that filePro is actually
> reporting the error correctly. I've gotten wholly unrelated
> errors out of it before that point in entirely the wrong
> direction. However, the verbiage for ENOENT would indicate
> that even if the error reporting is in the wrong place, that
> was the last error condition encountered. So I would hold at
> least the system error to be accurate, even if the context
> isn't. Something that should exist, doesn't.
>
> Does the file/table directory exist after you encounter this
> (with or without a map or subsidiary files)?
>
> mark->
> --
No, it never creates the directory. I have tried various things to get it
to work, to no avail. The only time it will work properly is if I have
previously created the directory /usr/appl/filepro/<file>. Then everything
is peachy.
-Chad McWilliams
More information about the Filepro-list
mailing list