Hi,
On Tue, Mar 08, 2016 at 02:36:09PM +0100, Harald Dunkel wrote:
> Attached is a patch. Hope this helps.
This patch is not helpful. This is only fixing a sympton.
What you really want to do is fix it like RedHat fixed it:
https://bugzilla.redhat.com/show_bug.cgi?id=1067236#c8 (Comment 8).
I c
Hi all,
More than two years after the initial bug report this is still unfixed.
I guess many people who are using LDAP etc. are running into this.
The fix is really trivial, and there is even a patch attached to this
bug report.
I'm wondering: The last upload was made on 2015/06/11, one and a ha
Attached is a patch. Hope this helps.
Harri
diff -ur old/cron-3.0pl1/debian/changelog cron-3.0pl1/debian/changelog
--- old/cron-3.0pl1/debian/changelog 2016-03-08 14:33:16.0 +0100
+++ cron-3.0pl1/debian/changelog 2016-03-08 14:32:51.976319657 +0100
@@ -1,3 +1,10 @@
+cron (3.0pl1-128.1) uns
Hi,
On 2014-10-27 17:50, Rath,Georg wrote:
> when using cron with sssd for ldap user accounts the cronjobs fail with the
> error message:
> crond[1234]: (tmp.cronjob) ORPHAN (no passwd entry)
>
> A similar bug (winbind instead of sssd) is #732203.
> There the bug was fixed by adding winbind to S
Package: cron
Version: 3.0pl1-124
Severity: important
Dear Maintainer,
when using cron with sssd for ldap user accounts the cronjobs fail with the
error message:
crond[1234]: (tmp.cronjob) ORPHAN (no passwd entry)
A similar bug (winbind instead of sssd) is #732203.
There the bug was fixed by ad
5 matches
Mail list logo