Carsten Schulz-Key wrote:
Gerald Macinenti wrote:
When trying to restore a volume for which I have incremental dumps on
tape (not a tape but a file on an external disk), I can sucessfully
restore the last full dump but increments are not appended, I have the
following error in butc output:
Hi ,
Is write-on-close something i can count on ?
More precisely i need to get from an afs client a file created
from another client and i wonder how can i be sure that the file
is not truncated.
Greetings,
Imad Zaza
This
Hi ,
Is write-on-close something i can count on ?
More precisely i need to get from an afs client a file created
from another client and i wonder how can i be sure that the file
is not truncated.
A fairly standard technique is to use a temp-name while
writing the file then rename the file
On Wed, Jul 11, 2007 at 08:57:02PM -0400, Dale Ghent wrote:
To expound on Rob's first point, the spindle count of a RAIDZ (or Z2)
set is important. It's generally urged to keep the disks that
comprise a raidz(2) set in the single digits and no more than 10 or
generally urged where? I
I'm using OpenAFS 1.4.3, pam_afs_session, and pam_krb5 from
Russ Alberry. Can anyone shed light on why my tickets and
tokens have only a 24hr lifetime?
kadmin.local: getprinc jblaine
Principal: [EMAIL PROTECTED]
Expiration date: [never]
Last password change: Mon Apr 23 14:50:16 EDT 2007
The box I'm using has 8GB of RAM. I ran the command to find the size of
the ARC, and it looks like (at least right now), it's only using about 4.2GB
of memory. There are no other major processes running on the box besides
our monitoring program, so it shouldn't be affecting it that much.
#
Jeff Blaine [EMAIL PROTECTED] writes:
I'm using OpenAFS 1.4.3, pam_afs_session, and pam_krb5 from Russ
Alberry. Can anyone shed light on why my tickets and tokens have only a
24hr lifetime?
Because the Kerberos libraries hard-code a 24 hour lifetime unless you
configure something else. You
Jeff Blaine wrote:
I'm using OpenAFS 1.4.3, pam_afs_session, and pam_krb5 from
Russ Alberry. Can anyone shed light on why my tickets and
tokens have only a 24hr lifetime?
kadmin.local: getprinc jblaine
Principal: [EMAIL PROTECTED]
Expiration date: [never]
Last password change: Mon Apr
What, what about front ending the NetApp with a box that provides the
AFS functionality? In other words, the NetApp exports to Server X only
which serves AFS. How viable would this approach be?
Marcus Watts wrote:
Date:Wed, 11 Jul 2007 14:07:34 EDT
To: openafs-info@openafs.org
Ah, that explains it. Thanks.
Jeffrey Altman wrote:
Jeff Blaine wrote:
I'm using OpenAFS 1.4.3, pam_afs_session, and pam_krb5 from
Russ Alberry. Can anyone shed light on why my tickets and
tokens have only a 24hr lifetime?
kadmin.local: getprinc jblaine
Principal: [EMAIL PROTECTED]
I spoke way too soon.
One of them was off.
They're all three set to 2 days now as a test and I still only
get tickets and tokens for 24hrs.
Jeffrey Altman wrote:
Jeff Blaine wrote:
I'm using OpenAFS 1.4.3, pam_afs_session, and pam_krb5 from
Russ Alberry. Can anyone shed light on why my
kinit -l7d ?
On Thu, 12 Jul 2007, Jeff Blaine wrote:
I spoke way too soon.
One of them was off.
They're all three set to 2 days now as a test
and I still only
get tickets and tokens for 24hrs.
Jeffrey Altman wrote:
Jeff Blaine wrote:
I'm using OpenAFS 1.4.3, pam_afs_session, and
On Thu, 12 Jul 2007, Russ Allbery wrote:
Jeff Blaine [EMAIL PROTECTED] writes:
I'm using OpenAFS 1.4.3, pam_afs_session, and pam_krb5 from Russ
Alberry. Can anyone shed light on why my tickets and tokens have only a
24hr lifetime?
Because the Kerberos libraries hard-code a 24 hour lifetime
Seeing Russ's response now that I got the digest email,
but FWIW:
~:rcf-kerbtest-linux /usr/kerberos/bin/kinit -l7d
Password for [EMAIL PROTECTED]:
...
Valid starting ExpiresService principal
07/12/07 17:04:54 07/13/07 17:04:54 krbtgt/[EMAIL PROTECTED]
renew until
This is MIT Kerberos as shipped with RHELv4.
ticket_lifetime = 2d in [libdefaults] of krb5.conf buys
me nothing. ticket_lifetime is not a documented option
for [libdefaults] according to the official MIT docs.
ticket_lifetime=2d as an option to pam_krb5RA.so buys
me nothing.
Jul 12 17:24:06
On 7/12/07, Jeff Blaine [EMAIL PROTECTED] wrote:
I spoke way too soon.
One of them was off.
They're all three set to 2 days now as a test and I still only
get tickets and tokens for 24hrs.
There is also the max_life parameter that can be set in kdc.conf.
(Maximum ticket lifetime for the
Jesse W. Asher [EMAIL PROTECTED] wrote:
What, what about front ending the NetApp with a box that provides the
AFS functionality? In other words, the NetApp exports to Server X
only which serves AFS. How viable would this approach be?
The above definately works using iSCSI. Seems to me like
It's set to 7d in kdc.conf
But thanks for the try! :(
Kevin Coffman wrote:
On 7/12/07, Jeff Blaine [EMAIL PROTECTED] wrote:
I spoke way too soon.
One of them was off.
They're all three set to 2 days now as a test and I still only
get tickets and tokens for 24hrs.
There is also the
The backup dump command has -append as an option.
Do you know if this was used when the dumps were created?
Gerald Macinenti wrote:
Carsten Schulz-Key wrote:
Gerald Macinenti wrote:
When trying to restore a volume for which I have incremental dumps
on tape (not a tape but a file on an
Jeff Blaine [EMAIL PROTECTED] writes:
ticket_lifetime = 2d in [libdefaults] of krb5.conf buys me nothing.
ticket_lifetime is not a documented option for [libdefaults] according
to the official MIT docs.
It's not a documented option, but the code uses it.
ticket_lifetime=2d as an option to
Jeff Blaine wrote:
This is MIT Kerberos as shipped with RHELv4.
ticket_lifetime = 2d in [libdefaults] of krb5.conf buys
me nothing. ticket_lifetime is not a documented option
for [libdefaults] according to the official MIT docs.
ticket_lifetime=2d as an option to pam_krb5RA.so buys
me
sure, but ignore the config files and give kinit a lifetime switch
On Thu, 12 Jul 2007, Jeff Blaine wrote:
This is MIT Kerberos as shipped with RHELv4.
ticket_lifetime = 2d in [libdefaults] of krb5.conf
buys
me nothing. ticket_lifetime is not a documented
option
for [libdefaults] according
I don't know if you missed it, but I did and replied
already. kinit -l7d did nothing worthwhile.
Derrick J Brashear wrote:
sure, but ignore the config files and give kinit a lifetime switch
On Thu, 12 Jul 2007, Jeff Blaine wrote:
This is MIT Kerberos as shipped with RHELv4.
ticket_lifetime
Okay, maxrenewlife changes are in effect and solved the
creds problem, but the fresh token still only has a
lifetime of 24hrs.
[ Thanks for all the replies, BTW ]
Jeffrey Altman wrote:
Jeff Blaine wrote:
This is MIT Kerberos as shipped with RHELv4.
ticket_lifetime = 2d in [libdefaults] of
24 matches
Mail list logo
