similar to: File handles

https://bugzilla.netfilter.org/show_bug.cgi?id=1104 Bug ID: 1104 Summary: Use close on exec flags instead of fcntl Product: iptables Version: CVS (please indicate timestamp) Hardware: x86_64 OS: All Status: NEW Severity: enhancement Priority: P5 Component: iptables Assignee:

Hi I have a problem with doveadm and flush # 2.2.36 (1f10bfa63): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.24.rc1 (debaa297) # OS: Linux 3.16.0-5-amd64 x86_64 Debian 8.10 example: #doveadm director status mail server ip tag vhosts state state changed users 10.0.100.24??????? 1????? up??? -???????????? 65 10.0.100.25??????? 100??? up??? -???????????? 989 #doveadm director flush

On Sat, Aug 06, 2016 at 03:43:48AM +0000, Eric Wong wrote: > Eric Wong <e at 80x24.org> wrote: > > I'm trying to test a trivial patch to set FD_CLOEXEC on the > > flintlock lockfd when using F_OFD_SETLK > > Fwiw, this is the patch I was originally going to test. > (but now I see maybe my F_SETFD might only need to be > called on F_OFD_SETLK success)

Hi! How to get usermod working with SSSD/389DS ? We have SSSD set up on our server and it uses 389DS. SSSD was enabled with the following command: authconfig --enablesssd --enablesssdauth --ldapbasedn=dc=example,dc=com --enableshadow --enablemkhomedir --enablelocauthorize --update Running for example "usermod -L username" returns: usermod: user 'username' does not exist in

Commit-ID: 26e26f48cf9255c44514b8d36e351ecf3c6260b2 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=26e26f48cf9255c44514b8d36e351ecf3c6260b2 Author: H. Peter Anvin <hpa at linux.intel.com> AuthorDate: Fri, 15 Jan 2016 11:30:01 -0800 Committer: H. Peter Anvin <hpa at linux.intel.com> CommitDate: Fri, 15 Jan 2016 11:30:01 -0800 [klibc] Remove open_cloexec()

Anyone? My next concern is codepages. The latest source (I've moved to 4.5.5 now) doesn't have any >> codepages. The RPM spec file I'm customising lists and wants to install them here: >> >> /usr/share/samba/codepages >> /usr/share/samba/codepages/lowcase.dat >> /usr/share/samba/codepages/upcase.dat >> /usr/share/samba/codepages/valid.dat >>

What is the intended behavior of the internal-sftp server when looking to resolve identity information for user via the nsswitch configured mechanisms? I am seeing different behavior between two packaged versions and am looking to understand what should be expected. Scenario: Utilizing a developed directory services plugin (dsplug), "ls" access on the sftp session fails with the

Locking of Quartz databases is currently done with a lockfile. This works well from the actual locking side, but the downside is that the lock isn't released if a process doesn't destroy the Xapian::WritableDatabase object. This is made worse because some of the bindings don't call destructors (or don't do it reliably). The obvious alternative is to use actual locking APIs. On

I'm trying to test a trivial patch to set FD_CLOEXEC on the flintlock lockfd when using F_OFD_SETLK and am running into a build failure even in an unpatched state. This is on a Debian jessie amd64 system building the jessie-backports version. The stable version (1.2.19-1+deb8u1) works and builds fine using the same commands, however I also encountered a similar build problem in a sid chroot

Hi! Thank you for the report, few points though: ?- The link you provided is broken ?- getting glibc-2.28 prebuilt seems to be bit problematic, and what I read from their changelog, the crypt function should work as normal. That said, it would be somewhat helpful if you could use gdb to find out what was passed to crypt p sample[i].key p sample[i].salt the return value is, for some reason, an

Hi Dovecot peeps, I'm enjoying running /usr/lib/dovecot/imap directly as a PREAUTH IMAP pipe. I find that it outputs log messages whose severity is INFO to stdout. I'm running it as follows: /usr/lib/dovecot/imap -c /tmp/dovecot.conf and I see the following messages output to stdout: * PREAUTH [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY

On 15/02/17 14:40, Tom Robinson via samba wrote: > On 13/02/17 10:18, Andrew Bartlett via samba wrote: >> On Mon, 2017-02-13 at 10:00 +1100, Tom Robinson via samba wrote: >>> On 12/02/17 03:13, Rowland Penny via samba wrote: >>>> On Fri, 10 Feb 2017 12:34:23 +1100 >>>> Tom Robinson via samba <samba at lists.samba.org> wrote: >>>>

As shown in the previous patch, plugins may choose to use stdin or stdout during .config. But from .get_ready onwards, well-written plugins shouldn't be needing any further use of stdin/out. We already swapped stdin/out to /dev/null while daemonizing, but did not do do during -f or --run, which leads to some surprising inconsistency when trying to debug a plugin that works in the foreground

Hi, ? Kotresh workaround works for me. But before I tried it, I created some strace-logs for Florian. setup: 2 VMs?(192.168.222.120 master, 192.168.222.121 slave), both with a volume named vol with Ubuntu?16.04.3,?glusterfs 3.13.2, rsync 3.1.1 . ? Best regards, Tino ? root at master:~# cat /usr/bin/rsync #!/bin/bash strace -o /tmp/rsync.trace -ff /usr/bin/rsynco "$@" ? One of the traces

On 2017-05-18T13:13, mh at ow2.org <mh at ow2.org> wrote: > Le 18/05/2017 ? 12:17, mh at ow2.org a ?crit : > > However, I get uid/gid numbers instead of names within sftp session (ls > > -l) ? I don't know if it's new but I would definitively prefer names... > > It seems the reason is : > > open("/etc/passwd", O_RDONLY|O_CLOEXEC) = -1 EACCES

On Sat, 27 Feb 2016 19:39:11 +0100 (CET), Eric J <eric at deptj.eu> wrote: > On Thu, 25 Feb 2016 23:37:52 +0000, Olly Betts <olly at survex.com> wrote: 8>< -------- >> I'm testing with Tcl 8.6 (Debian package 8.6.4+dfsg-3), and it works for >> me. >> >> So it does seem it must be due to something your Tcl interpreter is >> doing, but I'm

On 02/11/2019 03:05, Delian Krustev via dovecot wrote: > Hi, > > I got this simple test Sieve config: > > ############################################# > # Sieve Filter > # Generated by Ingo (http://www.horde.org/apps/ingo/) (11/01/2019, 10:46:06 PM) > > # Forwards > if true { > redirect "krustev at krustev.net"; > } > # Forward Keep Action

Hello, I have several systems which I recently updated with yum -y update to all the latest packages. These systems use yum-priorities and use the CentOS (priority 1) EPEL (priority 5) and rpmforge (priority 10) repositories. After the updates, dhcpd stopped working with a SIGPIPE error which occurs shortly after it attempts to fork into the background. I worked around that problem by building

As shown in the previous patch, plugins may choose to use stdin or stdout during .config. But from .get_ready onwards, well-written plugins shouldn't be needing any further use of stdin/out. We already swapped stdin/out to /dev/null while daemonizing, but did not do do during -f or --run, which leads to some surprising inconsistency when trying to debug a plugin that works in the foreground

F_SETFD takes an "int", so it stands to reason that FD_CLOEXEC expands to an "int". In turn, it's bad hygiene to manipulate the sign bit of (signed) integers with bit operations: ~FD_CLOEXEC Convert FD_CLOEXEC to "unsigned int" for the bitwise complement operator: ~(unsigned)FD_CLOEXEC The bitwise complement then results in an "unsigned int".