similar to: [Bug 3528] New: ls hangs when using ldap groups

Displaying 20 results from an estimated 2000 matches similar to: "[Bug 3528] New: ls hangs when using ldap groups"

2018 Jan 22
1
Samba 4.7 don't start on F27
it's not very helpful when the process exists without any output [root at srv-rhsoft:~]$ /usr/sbin/smbd -D [root at srv-rhsoft:~]$ /usr/sbin/smbd --foreground [root at srv-rhsoft:~]$ ps aux | grep smb root 8877 0.0 0.0 10904 960 pts/1 S<+ 15:04 0:00 /usr/bin/grep --color smb [root at srv-rhsoft:~]$ rpm -qa | grep samba samba-libs-4.7.4-2.fc27.x86_64
2018 Aug 08
0
Reproducible SIGSEGV when Dovecot 2.3 compiled against glibc-2.28
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
2018 Aug 08
3
Reproducible SIGSEGV when Dovecot 2.3 compiled against glibc-2.28
Hi, The link to the release notes seems should have an 'l' on the end: Try: https://www.sourceware.org/ml/libc-alpha/2018-08/msg00003.html This with gdb: thunderstorm /usr/src/dovecot/dovecot-2.3/src/auth # gdb /root/dovecot-auth-crash/auth /root/dovecot-auth-crash/core.auth.29667 GNU gdb (Gentoo 8.1.1 p1) 8.1.1 Copyright (C) 2018 Free Software Foundation, Inc. License GPLv3+: GNU
2018 Aug 08
2
Reproducible SIGSEGV when Dovecot 2.3 compiled against glibc-2.28
Hi, Dovecot 2.3 (release and current -git) versions compile, but fail to run when compiled against glibc-2.28. This is what is logged on startup: Aug 8 08:24:39 thunderstorm.reub.net dovecot[569]: master: Dovecot v2.3.2.1 (0719df592) starting up for imap, lmtp, sieve, submission, sieve Aug 8 08:24:39 thunderstorm.reub.net dovecot[569]: master: Error: service(auth): command startup failed,
2019 Jun 05
0
doveconf complains No matches on !include conf.d/* line but still writes out contents in conf.d
I'm on dovecot 2.3.3 (dcead646b). Output of `dovecot -n`: # 2.3.3 (dcead646b): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.3 (f018bbab) doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf line 98: No matches doveconf: Error: managesieve-login: dump-capability process returned 89 doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf line 98: No
2014 Jan 16
0
Generic UPS driver
One small comment: When the driver has no permission to access the device, it exits with a segmentation fault, it would be nice to have a more informative error. I'm not really sure if the issue is speciffic to this driver or is it general. I attached the output of an strace with the driver crashing. Best regards. -------------- next part --------------
2019 Jun 09
0
doveconf complains No matches on !include conf.d/* line but still writes out contents in conf.d
Further investigation shows that `doveconf` called `/usr/lib/dovecot/managesieve` which in return calls `doveconf` again, but with another uid (possible? I'm not sure) and a few extra arguments, which causes a call to `glob` in `src/config/config-parser.c:settings_include` to fail with `GLOB_NOMATCH`. I'd be appreciate if anyone can provide information on suspicious
2018 Sep 22
1
Printing via SMB-Kerberos no longer works
Robert Schetterer wrote: > Alex Persson wrote: >> Robert Schetterer wrote: >>> Alex Persson wrote: >>>> After upgrading from Ubuntu 16.04 to 18.04 printing via SMB-Kerberos no longer works (printing still works in 18.04 when I print via SMB but I don't want to have the password stored in clear text in /usr/lib/cups/backend/smb). >>>> >>>>
2020 Oct 26
0
Re: RBD volume not made available to Xen virtual guest on openSUSE 15.2 (with libvirt 6.0.0)
On a Friday in 2020, Marcel Juffermans wrote: >Hi there, > >Since upgrading to openSUSE 15.2 (which includes libvirt 6.0.0) the >virtual guests don't get their RBD disks made available to them. On >openSUSE 15.1 (which includes libvirt 5.1.0) that worked fine. The XML >is as follows: > [...] >I tried to strace libvirtd. The results are as follows: > >On
2020 Oct 26
1
Re: RBD volume not made available to Xen virtual guest on openSUSE 15.2 (with libvirt 6.0.0)
It's QEMU 4.2.1-lp152.9.6.1. I've tried updating it from the Open Build Service repos but there's too many version conflicts. Marcel On 26/10/20 9:02 pm, Ján Tomko wrote: > On a Friday in 2020, Marcel Juffermans wrote: >> Hi there, >> >> Since upgrading to openSUSE 15.2 (which includes libvirt 6.0.0) the >> virtual guests don't get their RBD disks
2020 Oct 23
2
RBD volume not made available to Xen virtual guest on openSUSE 15.2 (with libvirt 6.0.0)
Hi there, Since upgrading to openSUSE 15.2 (which includes libvirt 6.0.0) the virtual guests don't get their RBD disks made available to them. On openSUSE 15.1 (which includes libvirt 5.1.0) that worked fine. The XML is as follows: <domain type='xen' id='7'>   <name>mytwotel-a</name>   <uuid>a56daa5d-c095-49d5-ae1b-00b38353614e</uuid>  
2020 Oct 27
0
Re: RBD volume not made available to Xen virtual guest on openSUSE 15.2 (with libvirt 6.0.0)
Thanks Jim, Looking at the logs for the working and non-working setups, the command line for QEMU is identical and the qmp commands almost the same: they both do "query-chardev" and "query-vnc" and the working setup does an additional "qmp_capabilities" which is likely not relevant. So I guess it must be in QEMU - I'll head over to the bug tracker. Thanks
2013 Nov 08
1
[PATCH 2/3] syscalls: Add syscalls needed by arm64
On 11/08/2013 09:12 AM, Steve Capper wrote: > diff --git a/usr/klibc/open64.c b/usr/klibc/open64.c > new file mode 100644 > index 0000000..6ca603e > --- /dev/null > +++ b/usr/klibc/open64.c > @@ -0,0 +1,22 @@ > +/* > + * open64.c > + * > + * For 64 bit systems without the open syscall, pass straight > + * through into openat. > + */ > + > +#define
2015 Aug 01
2
unnecessary /proc requirement in 3.1.1
Hi. Thanks for good program. I'm quite paranoid guy and dont beleave when some program offer me "use chroot = yes". Instead i jail program manually. I was at 3.0.9 and all was fine. Manual chroot only requires files dir, config and personal tmp. 3.1.1 now also want whole /proc only for /proc/self/fd/X instead just fd number. Whole /proc is serious security risk for me. Why? starce
2013 Nov 12
0
[klibc:master] syscalls: Add syscalls needed by arm64
Commit-ID: 8858e8319655ef38398e0833b71d65b0e620a061 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=8858e8319655ef38398e0833b71d65b0e620a061 Author: Steve Capper <steve.capper at linaro.org> AuthorDate: Mon, 11 Nov 2013 17:04:11 +0000 Committer: H. Peter Anvin <hpa at zytor.com> CommitDate: Mon, 11 Nov 2013 19:31:13 -0800 [klibc] syscalls: Add syscalls
2013 Nov 08
0
[PATCH 2/3] syscalls: Add syscalls needed by arm64
arm64 uses generic syscalls, and does not include the "noat", "noflags", and "deprecated" syscalls. i.e. __ARCH_WANT_SYSCALL_{NO_AT|NO_FLAGS|DEPRECATED} This patch adds the syscalls needed for klibc to run on arm64. Signed-off-by: Steve Capper <steve.capper at linaro.org> --- usr/klibc/Kbuild | 3 +++ usr/klibc/SYSCALLS.def | 33
2017 Jan 13
1
Rsync tries to access unnecessary files/dirs after chrooting itself.
Hi. While debugging some encfs errors in the logs, I realized they are being generated because rsync (chrooted inside a encfs file system, --reverse) is trying to access files like: /root/.popt, /etc/localtime etc. This doesn't seem to be related to ID-name mapping as I already have numeric ids enabled in config. Here is the relevant strace output: [pid 25549] chroot("/chroot")
2018 Jun 27
0
dovecot-2.3.36 and flush
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
2020 Jul 07
0
Permission denied for home, even when it's 777
In order to veriify if it is indeed SELINUX, what happens when you use 'setenforce 0' ? Usuallh , you need use_samba_home_dirs boolean to be enabled. Best Regards, Strahil Nikolov ?? 6 ??? 2020 ?. 19:31:46 GMT+03:00, Deft Developer via samba <samba at lists.samba.org> ??????: >I cannot access home samba share from windows. Windows client displays >a >permission denied
2020 Jul 19
0
9p file sharing issue
I've run into an issue with 9p file sharing that I suspect is a bug. I'm running some Debian ARM VMs (armhf Ubuntu guests on an aarch64 Debian stretch host in case that matters). I'm using direct kernel boot, so I'm also using 9p host file sharing so that kernel updates from within the guest would work. However, I've noticed that dpkg (the Debian/Ubuntu package manager) fails