On Mon, Aug 13, 2012 at 02:18:11PM +0200, Tiziano Zito wrote:
What about this in condor.postinst::
SH=$(getent passwd | egrep '^condor:'| cut -d : -f 7)
if [ $SH = /bin/false -o $SH = /usr/sbin/nologin ]; then
# condor user exists and it is a locked user
else
adduser --system ...
Hi!
On Sat 11 Aug, 20:59, Michael Hanke wrote:
Regarding the actual bug. This issue came up in the early days of this
packaging. It essentially happens mostly for people upgrading from
existing Condor deployments. While I can't say much about the necessity
to have a Condor user in LDAP. I'm
severity 684463 normal
tag 684463 - wontfix
thanks
On Mon, Aug 13, 2012 at 12:28:17PM +0200, Tiziano Zito wrote:
If you see a way that is both secure and satisfies your needs, please
let me know. Otherwise, I think Evgeni is right: move 'condor' out of
LDAP and solve email issues with
severity 684463 normal
thank you!
However, it would be much nicer if we could find a way to deal with this
scenario without having to use debconf. Maybe we could try to check the
validity of the requirements: there is a 'condor' user and it can't be
used to log in. If there is a reliable
On Aug 13, 2012, at 7:02 AM, Michael Hanke wrote:
On Mon, Aug 13, 2012 at 12:28:17PM +0200, Tiziano Zito wrote:
If you see a way that is both secure and satisfies your needs, please
let me know. Otherwise, I think Evgeni is right: move 'condor' out of
LDAP and solve email issues with
severity 684463 wishlist
tag 684463 wontfix
thanks
Hi Tiziano,
[Debian bug is in CC]
On Fri, Aug 10, 2012 at 08:42:17PM +0200, Tiziano Zito wrote:
I mistakenly posted a bug report about condor on debian BTS
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684463 which
should have been
6 matches
Mail list logo
