Oh yes, I forgot to mention:
I tried this also with sssd and with that everything works ok with
pam_unix being first in stack. (Configured sssd running and then
replaced all pam_ldap.so with pam_sss.so in the original configuration).
--
You received this bug notification because you are a member
I've been having this problem also for some time now. I did some more
testing with pam configuration and found out that there is something
broken(?) in using combination of pam_unix and pam_ldap with auth and
account management group types.
So this does NOT work (in file /etc/pam.d/vsftpd):
--
removing /etc/pam.d/vsftpd worked for me also, but that makes the whole
"supports pam authentication" totally meaningless, since you can't
actually configure anything for vsftpd :-)
Could this be regression or something similar to this old bug from redhat?
(Comment 24 mentioning some kind of "pam
** Description changed:
Final output generated after read from stdin is lost by empty if command
exits quickly after the read.
All output comes through fine if:
-there is a lot of output after the read
-command waits for a small time after the read (no matter if waiting before
or aft
Package: empty-expect 0.6.18b-3ubuntu1 (precise)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1012027
Title:
final output lost when command exits quickly after reading from stdin
To manage notific
** Attachment added: "Perl example"
https://bugs.launchpad.net/ubuntu/+source/empty-expect/+bug/1012027/+attachment/3186093/+files/script.pl
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1012027
T
** Attachment added: "Bash example"
https://bugs.launchpad.net/ubuntu/+source/empty-expect/+bug/1012027/+attachment/3186092/+files/script.sh
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1012027
T
Public bug reported:
Final output generated after read from stdin is lost by empty if command
exits quickly after the read.
All output comes through fine if:
-there is a lot of output after the read
-command waits for a small time after the read (no matter if waiting before or
after the final ou
This has been fixed in upstream since version 3.2.0
https://github.com/ganglia/monitor-
core/commit/883f169353bdd58df10f21fb4e78541f53bc0f17
(I'm a bit sad that Precise being an LTS version did not get a newer
version of ganglia-monitor since current version 3.1.7 is already over
two years old.)
