similar to: Can set ACLs great from Windows, but see only SIDs when i reopen them

Hello, Jeremy and Jerry, I met both of you at LinuxWorld in Boston, where I learned tons and tons of great stuff from your presentations. I'm writing on deadline for publication and would really, really, really like to show off Samba's ability to map NT ACLs to POSIX ACLs. But right now, I can't make them work. I've spent some time on the Samba list trying to make this work, but

When you re-open the properties of an existing file or directory with ACLs set on it from a Windows workstation, do you see the usernames and group names properly? Or do you see SIDs in the dialog box as I do? Just gathering data. If you are seeing usernames and group names properly I'd love to see your smb.conf file. In my case, the Samba server is an AD domain member. -- Thomas Boutell

Hi, I'm working on updates to the WWW FAQ (okay, it's a little much to use the singular in 2006, but it was the first!). Embedded multimedia has been a sore spot for a while. I've been recommending that people embed old-school MPEG, because it works in all players. But it's awful. Terrible bitrates. I'm on the verge of recommending SWF instead, even though it's a hideous

Hi folks, I'm the co-author of "Windows and Linux Integration," a recent Sybex/Wiley title. So I'm very much interested in what's coming next in the Samba world. And I've been watching the Samba 4 'technology releases" with interest. One nifty feature that I like a lot: the old options that specified many confusing types of server behavior have been replaced

OK so I've got samba-3.0.11 compiled with ACL support. I've running 2.4.25 with the ACL/ATTR patch applied. I can read and set ACLS's using the getfacl/setfacl programs. ldd /usr/sbin/smbd shows it's linked to libattr.so.1 and libacl.so.1. I can read ACL with the smbcacls program, but when I try to set them I get: ERROR: Unable to open credentials file! Also from the

Change your security from ads to server security = ADS to server Mark Sarria ----- Original Message ----- From: IslandBwoy <IslandBwoy@ToughGuy.net> Date: Wednesday, March 9, 2005 2:17 pm Subject: [Samba] Domain Control > Hi all, > > I have a simple problem that i cant seem to figure out. Right now > i have > most of my confs in place to join my samba server to my

Samba server: SUN/Solaris 8 Samba version 3.0.10 Domain: Active Directory with a W2K PDC My Samba server is a Domain Member Server, connected to the Active Directory Domain with the "net rpc join" unix command. All the MS-Windows SMB client from the Domain can connect an use, without any problem, the shares of the Samba server. When I use, on an MS-Windows client or the PDC, the

Dear all I have setup separate pop3/imap log "/var/log/dovecot" and lmtp delivery log "/var/log/dovecot-deliver". After rotating logfiles, i run "doveadm log reopen". I see that my pop3/imap log "/var/log/dovecot" is used straight away, but my lmpt log "/var/log/dovecot-deliver" isn't used at first. After some time, usually a few minutes,

I still see the issue below. Is there anyone running separate LMTP logging that could check if they experience the same issue? Best regards Henrik Larsson -------- Original Message -------- Subject: "doveadm log reopen" don't reopen separate lmtp log Date: Sun, 25 Sep 2011 00:23:49 +0200 From: Henrik Larsson <dovecot-user at spambox.dk> To: dovecot at dovecot.org Dear all

Hi, I am running samba 3.0.14a on FreeBSD 6 box. I need this box to join to existing Windows 2003 domain to act as a file server to serve Windows XP clients. In the book "using samba" says to use "smbpasswd -j ..." to join the domain. But the -j option seems didn't existing. Anyone would be able to tell me what is the best way to make samba to join the domain? Thanks,

Processing commands for control at bugs.debian.org: > found 487401 2.6.2-29 Bug#487401: logcheck-database: please include ignore rules for wu-ftpd Bug marked as found in version 2.6.2-29. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)

Hi all, Currently I'm implementing a retrieval system with multiple reader processes and only one writer process updating the database periodically. In a reader process, whenever a Xapian::DatabaseModifiedError exception is caught, I call function reopen() and retry. However, my problem is, when there is only a small set of modification, e.g. only one new document is added, the reader would

On Mon, Apr 27, 2015 at 02:23:25PM +0200, matthias lay wrote: > after upgrading xapian I encountered the same problem as described in > ticket > #645 Read block errors after reopen() > > in our setup its 100% reproducible after each reopen(). I downgraded > again and it seems the problem occurs in Version 1.2.16 and above. > in <=1.2.15 everything works fine without seeing

On Mon, Dec 07, 2015 at 12:52:34PM -0800, Keyur Bhalerao wrote: [. . .] ubuntu@keyurubuntu:~$ virsh blockcommit vm-01 vda --active --verbose --pivot > error: internal error: unable to execute QEMU command 'block-commit': Could > not reopen file: Permission denied Fairly obvious suggestions, ensure permissions are set so that QEMU has permissions to the dir that contains images.

Has re-opening the logfiles broken between 2.2.32 and 2.2.33 releases? Using the same config that I've had for the past 10 or so point releases, /usr/bin/doveadm log reopen works perfectly up until 2.2.32, but with 2.2.33 (and .1 and .2) no new logfiles are created, file descriptors still have the original files open and keep writings to those logs. On an idling test instance, I get: master:

On 06.11.2017 23:31, David Zambonini wrote: > Has re-opening the logfiles broken between 2.2.32 and 2.2.33 releases? > > Using the same config that I've had for the past 10 or so point > releases, /usr/bin/doveadm log reopen works perfectly up until 2.2.32, > but with 2.2.33 (and .1 and .2) no new logfiles are created, file > descriptors still have the original files open and

On 07.11.2017 08:54, Aki Tuomi wrote: > > On 06.11.2017 23:31, David Zambonini wrote: >> Has re-opening the logfiles broken between 2.2.32 and 2.2.33 releases? >> >> Using the same config that I've had for the past 10 or so point >> releases, /usr/bin/doveadm log reopen works perfectly up until 2.2.32, >> but with 2.2.33 (and .1 and .2) no new logfiles are

Hi, after the upgrade from dovecot 2.2.32 to 2.2.33 we notice that the /var/log/director/director.log was empty and the log are write in the logrotate file es. /var/log/director/director.log-20171201. Log path is dovecot is: log_path = /var/log/director/director.log Logrotate configuration is: /var/log/director/director.log { ? daily ? rotate 31 ? missingok ? notifempty ? compress ?

dovecot -n # 2.2.33.2 (d6601f4ec): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.4.21 (92477967) # OS: FreeBSD 11.1-RELEASE-p1 amd64 zfs from logrotate.conf: /var/log/dovecot/dovecot.log { rotate 180 missingok nomail noolddir compress create 0600 nobody nobody postrotate # /usr/local/bin/doveadm log reopen

On 2019-07-08 13:36, Tom Sommer via dovecot wrote: > I rotate logs every night on my Director, running "doveadm log reopen" It happens on "/etc/init.d/dovecot restart", not "doveadm log reopen" - sorry So it happens when you run killproc on dovecot --- Tom