Displaying 5 results from an estimated 5 matches for "vadmin".
Did you mean:
admin
2008 Mar 25
0
domU doesn''t start | Error
Hi Guys,
my domUs won''t start and i do not know why.
i use the acutal version of xen (3.2) from mercurial on a debian etch
64 system. Thanks for any help
here the config of a domU:
==================================
name = "vadmin89"
kernel = "/boot/vmlinuz-2.6-xen"
root = "/dev/hda1"
memory = 75
disk = [ ''phy:/dev/vadmin/vadmin84_hdd,hda1,w'' ]
cpu_weight = 1
# network
vif = [ ''mac=00:17:31:A5:CB:D2,bridge=xenbr0'' ]
==================================
xend-config...
2017 Aug 23
3
maildir boxes directory mode upon creation
Hello, list !
Dovecot version is 2.2.27, running on Centos 6.7.
Postfix is receiving mail and putting it into mailboxes. Dovecot just
serves IMAP/POP3 connections to mailboxes.
Virtual users are stored in DB.
The problem is in directory mode (and thus file mode) for new mailboxes
upon it's creation.
If I create new record for new mailbox in DB and send mail to it,
Postfix will create
2008 Mar 25
1
Xen3.1 Etch-backports | VE already running
...ateDevice: vbd :
{''uuid'': ''dc7aeab1-5342-af00-6541-57ca33bb0218'', ''bootable'': 1,
''driver'': ''paravirtualised'', ''dev'': ''hda1'', ''uname'':
''phy:/dev/vadmin/vadmin90_hdd'', ''mode'': ''w''}
[2008-03-25 18:43:26 2695] DEBUG (__init__:1072) DevController:
writing {''virtual-device'': ''769'', ''device-type'': ''disk'', ''protocol'':
&...
2017 Aug 24
0
maildir boxes directory mode upon creation
* vadim <vadim at ideco.ru> 2017.08.23 16:04:
> I am unable to enforce dovecot to create mailboxes with 660 permissions.
> Output of dovecot -n is in the attachment.
>
> Please tell me what's the right way to control mailbox permissions ?
Hi Vadmin,
inject the mails per LMTP rather than having Postfix save them directly and let Dovecot worry about the permissions:
https://wiki2.dovecot.org/HowTo/PostfixDovecotLMTP
Regards
Thomas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: applicat...
2008 Aug 31
0
NFSv4 ACLs.
...long as VOP_ACCESS implementation simply
passes the "a_mode" parameter to the proper vaccess(9) routine, there
should be no difference in behaviour.
Adding granularity required adding some VWHATEVER defines to sys/vnode.h,
adding several VOP_ACCESS checks in the syscall layer, replacing VADMIN
with more specific permission in UFS and adding a unixify_vaccess()
routine that "strips the granularity" from the mode. This routine is
used in vaccess(9) and vaccess_acl_posix1e(9).
Filesystem-independent functionality was implemented in kern/subr_acl_nfs4.c.
This includes vaccess_acl...