similar to: Stealing ownership: chown user->qemu->root

Hi everyone (oh yeah, and I am new to the list but have a little Samba experience). I have a Samba 3.0.1 install on a Fedora Core 1 (.2138 kernel non-smp - not that it should matter for this). I have created a group called "osla" for the users in my domain and I have Samba working properly as a PDC, or at least properly in so far as I can join clients to the server, run scripts and

Hi, I've just upgraded our dovecot installation from 1.0.15 to 1.1.13. This went smoothly and just worked -- thank you very much for writing such a high performance and robust piece of software. However, we have a shared mailbox that people can subscribe to. After upgrading to 1.1.13 ... dovecot tries to create a dovecot-acl-list file in the top level of this ... but it creates it

On Fri, Feb 1, 2019 at 11:37 PM Aki Tuomi <aki.tuomi at open-xchange.com> wrote: > > On 01 February 2019 at 23:16 Mark Moseley < moseleymark at gmail.com> wrote: > > > Running: Ubuntu xenial, dovecot 2.2.36 > > I've been working on moving our user base from maildir to mdbox and trying > to come up with solutions for things like moving emails around. In the

Hi, I'm trying to run a DOS program within a cron job. After much trial-and-error I settled on the following approach: - rm -r ~/.wine - call wine without any arguments, this lets wine generate a default configuration in ~/.wine - change ~/.wine/config: set GraphicsDriver to ttydrv instead of x11drv - the cron job consists of a shell script that runs the DOS program with "wcmd

Basically, what I typed was: chown -R user2:user2 * chown -R user2:user2 .* chown -R user2:user2 *.* ...all in /home. Duh. I forgot which way recursive went. So, I then did: chown -R root:root * chown -R root:root .* chown -R root:root *.* ...this time in / to try and f things. Duh again. Other items need to have other owners & groups. So, how can I fix this? In MacOSX, there is a utility

Hello, I've been trying to figure this out for some time and can't quite nail it down, despite searching the internet, and a couple of samba books. Here goes: I'm running "Version 3.4.3-3.3.1-2341-SUSE-SL11.2" of Samba on OpenSUSE 11.2. Here are some relevant excerpts from my smb.conf file: [global] ... security = ADS ... winbind separator = + ... log level = 2 ...

Hello list, I have a apache documentroot with ownership root.www-data and mode 755 Now I have a /var/www/index.html and chown'd that file to user "foo". Sincen "foo" has no write permission under /var/www, he cannot rsync from remote server to the local filesystem because rsync will try to make temp file and unlink the original file before writing over it. Is there any

Running: Ubuntu xenial, dovecot 2.2.36 I've been working on moving our user base from maildir to mdbox and trying to come up with solutions for things like moving emails around. In the past, with maildir, our support guys could just mv the files around and done. For mdbox, I've been working on getting things set up to use doveadm. One weirdness I've seen is that in imports (i.e.

Hi all, After setting permissions on a file. If anyone authorised to open the file writes to it, the ACL gets deleted and that person becomes the owner of the file and the group is reset to the default. For example, whenever a certain user opens and changes a file in the problem folder he becomes the owner and another gets kicked of the list: More clearly, lee was the last one to write to this

Hi there... Foolish me.... all was going sooooooo well and then I got a wild hair and updated to the latest clamav .92 today. It is possible I should have just done an rpm update install yet there were some changes in ClamAV lately and I didn't know how well that would go. up till now I spec'd and rolled my own Clamav RPMs without milter somewhat recently ClamAV changed from having a

Hi All, I've pored over the wiki, read through the archive, and have what I believe should be a working set-up, but I can't seem to get my shared namespace to work correctly. Any guidance would be much appreciated. I started off using a flat file for acl_shared_dict and ran into the same problem recently reported with the shared-database file getting chown'd to the first user to

Hi people I'm running Xapian (1.0.9) and more specifically omega to index a few different databases. After the databases are first indexed (by user A), the dirs get chmod'ed to 0777 to allow user B full access to them. Even after the indexing is done, the file "flintlock" still exists in all database dirs. It's owned by user A (perm: -rw-------). When user B wants

Hi, I discovered yesterday that the instructions given at http://www.openssh.org/faq.html#3.14 regarding the correct permissions for the authorized_keys file mistakenly recommend chmod'ing the file to 600 when it should be 644. The requirement for public key authentication to work is in fact that ~/.ssh/authorized_keys is readable (but not writable) by group and other, not just owner. Someone

For many months now we have been trying to create a file-backed qcow image with the qcow-create code. Each time we try to back a file with a qcow, it screams: *** buffer overflow detected ***: qcow-create terminated Below is the output from two different attempts and information about qcow-create. Any ideas/thoughts/help you can offer? Thank you for your help! -Eric [root@trogdor ~]#

After snapshot-delete, the qcow2 image file size doesn't decrease, isn't that a waste of disk space? Would someone please tell me how to decrease the file size when snapshot-delete, if that's possible? The image file name of my virtual machine is d0.qcow As follows: [root at test1 ]# virsh list Id Name State

Hi, Trying to understand the current state of affairs with QCOW support in Xen with the blktap driver. It''s been made clear that a deviation from QEMU''s implementation of QCOW has occurred and that the QCOW files used in Xen must be created with the associated Xen tools only (e.g. qcow-create) and that images between QEMU and Xen are not interchangeable. My first question is

"Michal Prívozník" <mprivozn@redhat.com> wrote on 03/23/2020 12:26:14 PM: > From: "Michal Prívozník" <mprivozn@redhat.com> > To: Martin Kletzander <mkletzan@redhat.com>, Joe Muro <joemuro@us.ibm.com> > Cc: libvirt-users@redhat.com > Date: 03/23/2020 12:26 PM > Subject: [EXTERNAL] Re: libvirt dynamic file ownership > > On 20. 3. 2020

excuse the newbie nature of the post, we recently inherited a linux server which has ext3 on it and we have encountered problems before being afforded the opportunity to properly educate ourselves... We had a situation where the server froze and required a hard restart. On reboot we get the following notices which were captured in the dmesg log EXT3-fs: INFO: recovery required on readonly

Hi! Changeset 17913 breaks build on *BSD: block-qcow.c:36:20: error: gcrypt.h: No such file or directory cc1: warnings being treated as errors block-qcow.c: In function ''gen_cksum'': block-qcow.c:160: warning: implicit declaration of function ''gcry_md_hash_buffer'' block-qcow.c:160: error: ''GCRY_MD_MD5'' undeclared (first use in this function)

On 10/08/2012 21:58, nut-upsuser-request at lists.alioth.debian.org wrote: >>> Arnaud Quette<aquette.dev<at> gmail.com> writes: >>>> 2012/6/3 Chris Rees<crees<at> freebsd.org>: >>>>> Hi all, >>>> Hi Chris, >>>> >>>>> After some research I've found that this device should run with the