(OT)
* Michael S. Zick wrote on Sun, May 31, 2009 at 08:05 -0500:
A more general solution would be:
# Am I running as user 0 (root)?
uid=$(/usr/bin/id -u) 2/dev/null
if [ $uid == 0 ] ; then
BTW, shouldn't it be just one = (to be compliant with POSIX and
/usr/bin/test)?
oki,
On Tue, Jun 02, 2009 at 03:49:13PM +0200, Steffen DETTMER wrote:
(OT)
* Michael S. Zick wrote on Sun, May 31, 2009 at 08:05 -0500:
A more general solution would be:
# Am I running as user 0 (root)?
uid=$(/usr/bin/id -u) 2/dev/null
if [ $uid == 0 ] ; then
BTW,
To: openssl-users@openssl.org
Subject: RE: TLS w/LDAP
Thanks for the response, Kyle.
I've pretty much deduced what the error is, but just cannot figure out where it
is coming from. It only happens when I turn on TLS for LDAP. There are really
no 'variables' defined in the LDAP configs
On Sun May 31 2009, John Kane wrote:
After painstakingly commenting everything out of all startup files, then
added them back in, I found the cause of the
-bash: [: =: unary operator expected
error that has been occurring on all Linux servers since turning on LDAP
TLS on INT
...@openssl.org] On Behalf Of Dave Stoddard
Sent: Saturday, May 30, 2009 10:12 AM
To: openssl-users@openssl.org
Subject: RE: TLS w/LDAP
If you add set -x to the top of your script, you can see
the script execute line by line to locate the source of the
error.
Dave
-Original Message
:
On Sun May 31 2009, John Kane wrote:
After painstakingly commenting everything out of all startup files, then
added them back in, I found the cause of the
-bash: [: =: unary operator expected
error that has been occurring on all Linux servers since turning on LDAP
TLS on INT.
In the file
found the cause of the
-bash: [: =: unary operator expected
error that has been occurring on all Linux servers since turning on LDAP
TLS on INT.
In the file:
/etc/profile.d/krb5-workstation.sh
The follow is causing the issue:
if ! echo ${PATH} | /bin/grep -q /usr/kerberos/sbin
On 05/30/2009 12:52 AM, John Kane wrote:
Thanks for the response, Kyle.
I've pretty much deduced what the error is, but just cannot figure out where it is coming
from. It only happens when I turn on TLS for LDAP. There are really no 'variables'
defined in the LDAP configs; nothing using
:
Thanks for the response, Kyle.
I've pretty much deduced what the error is, but just cannot figure
out where it is coming from. It only happens when I turn on TLS for
LDAP. There are really no 'variables' defined in the LDAP configs;
nothing using the '[ $blah = blahblah ] syntax
After painstakingly commenting everything out of all startup files, then
added them back in, I found the cause of the
-bash: [: =: unary operator expected
error that has been occurring on all Linux servers since turning on LDAP
TLS on INT.
In the file:
/etc/profile.d/krb5-workstation.sh
I just turned on TLS on my LDAP (per instructions on
http://www.openldap.org/faq/data/cache/185.html). Now all of my Linux
servers give the following error on login:
-bash: [: =: unary operator expected
The error goes away when I turn TLS back off. I cannot determine what
is causing this error
That's an error in the script you're launching at startup. I don't
know what it is, but I'd bet there's an unquoted '[' character
somewhere that is only evaluated when TLS LDAP is enabled. (see the
'-bash: ' at the beginning of the line? That tells you that bash is
generating the error message
Thanks for the response, Kyle.
I've pretty much deduced what the error is, but just cannot figure out where it
is coming from. It only happens when I turn on TLS for LDAP. There are really
no 'variables' defined in the LDAP configs; nothing using the '[ $blah =
blahblah ] syntax
something about this???
then I hope it's will help :)
Gabrielle
From: SECRET Defense [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
CC: [EMAIL PROTECTED]
Subject: [SSL/TLS and LDAP] : wrong number version
Date: Wed, 05 May 2004 18:10:45 +0200
hello !
First of all, I have an debian
Hi All,
I am writing a API for LDAP , I would like to make it
enabled for TLS. Please let me know the procedure for
invoking TLS in a LDAP Session and the process thereafter.
Thanks
Prashant
_
Get Your
15 matches
Mail list logo
