It would be better to make the create permission 0666. Then umask can
restrict that permission and the user can get whatever permission
required by the application.
Joe Wilson wrote:
--- "Shan, Zhe (Jay)" <[EMAIL PROTECTED]> wrote:
I've tried umask, but it does not work for SQLite.
Here
Joe Wilson wrote:
I can never remember the umask number's effect without
experimentation
DESCRIPTION
umask sets the umask to mask & 0777.
The umask is used by open(2) to set initial file permissions on a
newly-created file. Specifically, permissions in the umask are turned
off from
--- "Shan, Zhe (Jay)" <[EMAIL PROTECTED]> wrote:
> I've tried umask, but it does not work for SQLite.
Here are the default permissions used with open()'s O_CREAT flag:
src/os_os2.h:# define SQLITE_DEFAULT_FILE_PERMISSIONS 0600
src/os_unix.c:# define SQLITE_DEFAULT_FILE_PERMISSIONS 0644
But
I've tried umask, but it does not work for SQLite.
I search this emaillist, and find the following message in 2003 which is
related to this topic. I want to check if it is still true in the current
version. Thanks.
Jay
From: Dong Xuezhang-A19583
<[EMAIL
This is not actually about SQLite. man umask
M. Manese
On 2/22/07, Shan, Zhe (Jay) <[EMAIL PROTECTED]> wrote:
Hi,
If to use SQLite to create a database in Linux, the database file will
be granted permission 644 as default.
Is this value hardcoded in the current version? Is it possible to
Hi,
If to use SQLite to create a database in Linux, the database file will
be granted permission 644 as default.
Is this value hardcoded in the current version? Is it possible to
change this default vaule, say to 664 or something else?
Thanks.
Jay
6 matches
Mail list logo
