similar to: provisioning with vagrant-libvirt leaves .img file only readable by root

I am migrating a couple old RH servers running sendmail and UW-IMAP to a new Ubuntu 10.04 servers running Postfix and Dovecot. I have everything working reasonably well except that the permissions of newly created mbox mail folders is always 600. I have reviewed the archives, google, and double checked everything is as suggested in the Dovecot Wiki / SharedMailboxes / Permissions. I am

So, trying to get profiles working. The GPO is there and functioning. However, the user isn't able to create the needed directory for *initial* setup of the profile. [It's possible if I hand-created the profile directory for the user, and granted them rights, it would work properly. But it is vastly easier to have the user create their own directory at first login. I'm sure that's

trying to figure out the best way to accomplish this, running samba 3.x on a debian system in share level mode (workgroup) have a shared folder for all the staff that they have permssions to by membership of being in the "staff" group, this share has about 40-50 subfolders. now they have an intern starting and want to restict that intern to 5 of those folders which they'll

I've got a share that I'm trying to get so I can set permissions through the normal windows way (right click on folder/file->properties->security). The share definition is: [test] comment = Test share on magellan path = /var/test browseable = yes writable = yes hide unreadable = yes admin users = @"Domain Admins" The server is a member server in

OK, so I don't know what's going on. (even with tinyproxy/firehol off the following occurs). Unless wine is run by root, when WoW is first loaded and trying to login, WoW creates a Cache folder and a bunch of folders under cache for login purposes. The Cache folder exists in: <wine profile dir>/drive_c/users/Public/Applicatoin data/Blizzard Entertainment/Battle.net. Now it can

Hello, I tested to transfer all 7 FSMOs from Windows Server 2003 Enterprise to Samba 4.3.0 DC. (I think some users still use Win2K3 and want to migrate.) But unfortunately is failed. To reproduce, (1) Promoto Win2K3R2 Enterprise host to first DC. (2) Join self-built Samba 4.3.0 to the domain. (3) Run 'samba-tool fsmo transfer --role=all' root at jessie64-1:~# samba-tool fsmo

Hello, > On 07/10/15 00:33, TAKAHASHI Motonobu/高橋 基信 wrote: > > Hello, > > > > I tested to transfer all 7 FSMOs from Windows Server 2003 Enterprise > > to Samba 4.3.0 DC. (I think some users still use Win2K3 and want to > > migrate.) But unfortunately is failed. > > > > To reproduce, > > > > (1) Promoto Win2K3R2 Enterprise host to first DC.

Hi guys: I'd like to "scriptify" my virtual machine manager deployment. In particular id like to 1) Configure a 3 node cluster from an ISO 2) Assign static IPs at the vm level, and have those cascade into /etc/hosts 3) Add storage to each machine in the cluster . 4) Set the memory/CPU# for each machine. Is there a way i can automate this task using VMM, or maybe, using VMM in

We are pleased to announce the immediate availability for CentOS Linux 7 x86_64 images for Vagrant. This image represents a minimal install set, that lines up with the user expectation for our Cloud Images, our ISO based Minimal installer and the default minimal install profile from the in-distro install options. Images are released for the VirtualBox and LibVirt providers ( more providers

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Updated Vagrant box's are now available for CentOS Linux 7/x86_64 and for the first time for CentOS Linux 6/x86_64; We are providing box's for Livbirt provider and the Virtual Box provider. ref: https://atlas.hashicorp.com/centos/boxes/6 https://atlas.hashicorp.com/centos/boxes/7 Release Notes for these images are published at :

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Updated Vagrant box's are now available for CentOS Linux 7 and CentOS Linux 6 for x86_64. These are available for the Libvirt and the VirtualBox providers in Vagrant. ref: https://atlas.hashicorp.com/centos/boxes/6 https://atlas.hashicorp.com/centos/boxes/7 Release Notes for these images are published at :

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Updated Vagrant box's are now available for CentOS Linux 7 and CentOS Linux 6 for x86_64. These are available, as in the past, for the Libvirt and the VirtualBox providers in Vagrant. We have also enabled the vmware providers, for anyone using Vmware's products for backing Vagrant on Linux, MacOS or Windows. ref:

Vagrant and packer look like the could be useful to developers, especially when testing, as they make it relatively painless to 'reinstall' a machine to a (mostly) known state. I find that, no matter how hard I try, there always seem to be a few keystrokes that don't make it into the changelog, and recreating from scratch is how I find them. Thanks for pointing them out. I would

Hi, At Vagrant Cloud there are "box" images for stream8 and stream9 [1]. At least they are supposed to be there. The download links on the detail pages, for example for stream9 20230727.1 [2] are redirected to cloud.centos.org, however they give an 404 error. Possibly the centos Vagrant Cloud page is not kept up to date with the actual box images that are now present on

Hi, At Vagrant Cloud there are "box" images for stream8 and stream9 [1]. At least they are supposed to be there. The download links on the detail pages, for example for stream9 20230727.1 [2] are redirected to cloud.centos.org, however they give an 404 error. Possibly the centos Vagrant Cloud page is not kept up to date with the actual box images that are now present on

I am pleased to announce the immediate availability of Vagrant 1.7.4 on CentOS Linux 7 x86_64, delivered via a Software Collection (SCL) built by the SCLo Special Interest Group (https://wiki.centos.org/SpecialInterestGroup/SCLo). QuickStart ---------- You can get started in three easy steps: $ sudo yum install centos-release-scl $ sudo yum install sclo-vagrant1 $ scl enable

I took an hour this morning to document how I use Vagrant and Puppet together to provision development VMs as well as more production-like systems. This may be entirely elementary to folks who are more fluent with Puppet, but this is an example I thought was lacking. https://github.com/blalor/vagrant-puppet-example I welcome feedback and criticism of this setup. I''m looking to

Hi All, I am using Vagrant to provision a box (CentOS 6.x) with puppet provisioner. The box is built by using veewee, with ruby 1.8.7 and puppet 3.2 iinstalled, and the vagrant environment layout is, . ├── Gemfile ├── Gemfile.lock ├── Rakefile ├── Vagrantfile ├── definitions │ └── centos-6.3.minimal ├── hiera │ └── data ├── iso │ ├── CentOS-6.3-x86_64-minimal.iso │ └──

hello all, i have problem in using g729 codec. my asterisk version is 1.8.22. when i run "core show codecs" in asterisk, there is a g729 codec in the list so i assume that i can use it for my channels. but connection can not be set when i use it for my h323 channel. i read somewhere that codec g729 is a commercial codec and i should buy its license in order to use it. is it true? if

Hi, I have an issue whereby when I create a new file it obeys the create mask defined for the share but when I copy a file from within the same directory the file is created without write permssions for the primary group. Ie: directory has permissions 770, existing file has permissions of 770, create mask is 0770. When I copy a file its permissions are 750. However when creating a new file