>SQLite opens the directory so that it can fsync() it. It
>wants to fsync() the directory after creating the journal file
>to make sure that the inode for the journal file gets created
>and updated properly.
>
>Some unix filesystems guarantee that inodes always get updated
>correctly. Others do
>As I'm not familiar with
>daemon, I can't comment further. What is this daemon?
>
I'm not usre about the name of it, but you can configure it with the Madriva
Linux Control Center.
Respectfully,
Christopher
chtaylo3 uttered:
Christian,
Or you could just fix the permissions on your temp directories. If the
files in */tmp are sensitive, they should be protected. The file name
themselves should not be sensitive.
I'm not aware of many installations using the permissions you use for temp
chtaylo3 <[EMAIL PROTECTED]> wrote:
> Jay,
>
> >It's important that the journal file be preserved between reboots.
> >If the power fails you can then recover the database using the journal.
> >If your code has to go on one of the linuxes(linuxii??)
> >that follow posix/LSG standards you'll want
On 7/24/06, chtaylo3 <[EMAIL PROTECTED]> wrote:
Jay,
>It's important that the journal file be preserved between reboots.
>If the power fails you can then recover the database using the journal.
>If your code has to go on one of the linuxes(linuxii??)
>that follow posix/LSG standards you'll want
Jay,
>It's important that the journal file be preserved between reboots.
>If the power fails you can then recover the database using the journal.
>If your code has to go on one of the linuxes(linuxii??)
>that follow posix/LSG standards you'll want to know how to make
>it work correctly on those
Christian,
>
>Or you could just fix the permissions on your temp directories. If the
>files in */tmp are sensitive, they should be protected. The file name
>themselves should not be sensitive.
>
>I'm not aware of many installations using the permissions you use for temp
>directories.
Yes that
On 7/24/06, chtaylo3 <[EMAIL PROTECTED]> wrote:
>/tmp : Temporary files
>/var/tmp : Temporary files preserved between system reboots
What does this have to do with having the tmp dir's as global read?
It's important that the journal file be preserved between reboots.
If the power fails you
>/tmp : Temporary files
>/var/tmp : Temporary files preserved between system reboots
What does this have to do with having the tmp dir's as global read?
Mandriva 2006 has a daemon (not sure what the name is) that checks the
permissions of certain folders, in this case /var/tmp, usr/tmp, and
On 7/21/06, chtaylo3 <[EMAIL PROTECTED]> wrote:
>Set the global variable sqlite3_temp_directory to any
>directory you want and it tries that directory first.
Ok, fair enough. But why do you try and open the directory? Why can you
just try and create the tmp file there and deal with it if
chtaylo3 uttered:
Set the global variable sqlite3_temp_directory to any
directory you want and it tries that directory first.
Ok, fair enough. But why do you try and open the directory? Why can you
just try and create the tmp file there and deal with it if it's not allowed?
I'm asking
>Set the global variable sqlite3_temp_directory to any
>directory you want and it tries that directory first.
Ok, fair enough. But why do you try and open the directory? Why can you
just try and create the tmp file there and deal with it if it's not allowed?
I'm asking becuase I have
chtaylo3 <[EMAIL PROTECTED]> wrote:
> I have a question about os_unix.c
>
> On line 854 inside function sqlite3UnixTempFileName, you declare:
> static const char *azDirs[] = {
> 0,
> "/var/tmp",
> "/usr/tmp",
> "/tmp",
> ".",
> };
>
> I'm guessing this is where sqlite
I have a question about os_unix.c
On line 854 inside function sqlite3UnixTempFileName, you declare:
static const char *azDirs[] = {
0,
"/var/tmp",
"/usr/tmp",
"/tmp",
".",
};
I'm guessing this is where sqlite attempts to create a temp copy of the
database it's
14 matches
Mail list logo
