permission denied / var/imap

Robert Scussel rscuss at omniti.com
Wed Nov 19 09:45:07 EST 2003


It looks like cyrus is complaining about writing to /var ...

----------------
...te(1, "creating /var/imap\r...\n", 23creating /var/imap
) = 23
", 0755)               = -1 EACCES (Permission denied)
  ")                     = -1 ENOENT (No such file or directory)
  at (eval 1) line 91.hange to /var/imap\r at"..., 51couldn't change to
/var/imap
----------------

/var/spool/imap seems to be fine, but when it tries to make /var/imap it 
  fails.

double check that /var/imap exists, and if it still fails, try and 
remove /var/imap, allow cryus permissions to create the directory for 
the duration of mkimap, and then change the permissions of /var back.

HTH.

B

frank joseph wrote:
> Hello. I posted yesterday under the subject of  "mkimap failure", but did
> not receive
> any responses. This is my first time posting to any group and if I have done
> something
> wrong, I apologize. Please let me know what it is so that I don't repeat it.
> Below is a
> more concise description of my problem. I would appreciate it if anyone
> would be
> kind enough to respond.
> 
> packages installed:
> 
> db-4.1.25
> openssl-0.9.7c
> cyrus-sasl-2.1.15
> cyrus-imapd-2.1.15
> 
> Everything compiles fine. When I su to cyrus and run "tools/mkimap",
> I can see the return is incorrect:
> 
>  cyrus at ilumina:/usr/local/src/cyrus-imapd-2.1.15/tools$ ./mkimap
> 
> . will configure directory /var/imap
> . saw partition /var/spool/imap
> done
> ...ating /var/imap
>  at (eval 1) line 91.ar/imap
> 
> This is a fresh install of Slackware-9.1. No permissions other than what
> is required in the manual have been changed. Running Strace on mkimap
> shows the following:
> 
> --------------------snip-----------------------------------------------
> reading configure file...open("/etc/imapd.conf", O_RDONLY|O_LARGEFILE) = 4
> ioctl(4, SNDCTL_TMR_TIMEBASE, 0xbffff600) = -1 ENOTTY (Inappropriate ioctl
> for device)
> _llseek(4, 0, [0], SEEK_CUR)            = 0
> fstat64(4, {st_mode=S_IFREG|0644, st_size=155, ...}) = 0
> fcntl64(4, F_SETFD, FD_CLOEXEC)         = 0
> brk(0)                                  = 0x814d000
> brk(0x814e000)                          = 0x814e000
> write(1, "reading configure file...\n", 26reading configure file...
> ) = 26
> brk(0)                                  = 0x814e000
> brk(0x814f000)                          = 0x814f000
> read(4, "configdirectory: /var/imap\r\npart"..., 4096) = 155
> .rite(1, "i will configure directory /var/"..., 39i will configure directory
> /var/imap
> ) = 39
> .rite(1, "i saw partition /var/spool/imap\r"..., 34i saw partition
> /var/spool/imap
> ) = 34
> read(4, "", 4096)                       = 0
> write(1, "done\n", 5done
> )                   = 5
> close(4)                                = 0
> ...te(1, "creating /var/imap\r...\n", 23creating /var/imap
> ) = 23
> ", 0755)               = -1 EACCES (Permission denied)
> ")                     = -1 ENOENT (No such file or directory)
>  at (eval 1) line 91.hange to /var/imap\r at"..., 51couldn't change to
> /var/imap
> ) = 51
> close(3)                                = 0
> exit_group(2)                           = ?
> --------------------------------------------------------------------
> If cyrus owns /var/imap with privileges of 750, and mkimap is being
> run by cyrus, how could write permissions be denied?
> 
> Thanks Again
> 
> -Frank
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 


-- 
Robert Scussel
1024D/BAF70959/0036 B19E 86CE 181D 0912  5FCC 92D8 1EA1 BAF7 0959





More information about the Info-cyrus mailing list