On 5/17/2011 5:53 AM, Onkesh Bansal wrote:
> Hello,
>
>
>
> Configuration>>
>
Windows 2008 R2 (Service Pack 1) workstation.
>
>
>
> I am having this problem on my machine and am not able to figure out
> what is the root cause.
>
> The scenario seems with Terminal Services installed on the sys
Application specific configuration files do not belong in \WINDOWS.
The correct place for krb5.ini is \ProgramData\Kerberos\krb5.ini which
requires that the environment variable KRB5_CONFIG be set to refer to
that file.
I do not know whether or not Java will pay attention to the environment
variab
Hello,
Configuration>>
>>>Windows 2008 R2 (Service Pack 1) workstation.
I am having this problem on my machine and am not able to figure out
what is the root cause.
The scenario seems with Terminal Services installed on the system and
when the authentication has to be done via the LDAP ov
Quoting Jason L Tibbitts III :
> You need to send -HUP to the daemons to get them to close and reopen
> their logs.
Doh! The fact is, it isn't always necessary to do that (e.g. for Exim)
and I just happened to use one of those logrotate files as an example
without checking any others.
Thanks
> "JW" == Jaap Winius writes:
JW> Hi folks, On all of the Debian squeeze servers with Kerberos
JW> (v1.8.3) that I manage, I've noticed that the Kerberos daemons start
JW> out writing to their designated log files, e.g. kdc.log, but once
JW> those log files are rotated they ignore the new emp
Hi folks,
On all of the Debian squeeze servers with Kerberos (v1.8.3) that I
manage, I've noticed that the Kerberos daemons start out writing to
their designated log files, e.g. kdc.log, but once those log files are
rotated they ignore the new empty ones and instead prefer to write
only to
