Hi,
I'm working on the SGE / AFS integration under SL5. With the latest
OpenAFS (1.4.3) the way PAGs are handled has changed (kernel keyring).
Unfortunately this keyring won't get inherited from SGE's shepherd in an
interactive qrsh session.
I can have full access to the PAG environment SGE
Derrick J Brashear <[EMAIL PROTECTED]> writes:
>> Hey neat, the output of 'ls' shows pts names.
> i actually did this years ago, before there was nss, and let it
> drop. but, the issue when you have not coordinated local uids and pts
> ids is when do you do an afs lookup and when do you do a loca
> I also think (thanks, kula) that setting up the new machine as a
> fileserver, moving the disks over to the new machine, then doing the vos
> syncserv/vos syncvldb dance on all the fileservers will also work. I'm
> going to try it myself in a couple days.
> --david
this worked fine, too, if a
On Mon, 19 Mar 2007, Adam Megacz wrote:
Derrick J Brashear <[EMAIL PROTECTED]> writes:
someone had nss_pts. that's the right idea.
http://tarna.oit.unc.edu/~utoddl/nss_pts_0.2.tgz
Hey neat, the output of 'ls' shows pts names.
i actually did this years ago, before there was nss, and let it
On Mon, 19 Mar 2007, Adam Megacz wrote:
If I were to add support for this, where would be the best place to
put the configuration option (afsd command line flag, perhaps)?
yet another afsd flag? ick.
the generic pioctl (which takes a parameter and a value) and a parameter
for this, is the "
Derrick J Brashear <[EMAIL PROTECTED]> writes:
> someone had nss_pts. that's the right idea.
http://tarna.oit.unc.edu/~utoddl/nss_pts_0.2.tgz
Hey neat, the output of 'ls' shows pts names.
- a
--
PGP/GPG: 5C9F F366 C9CF 2145 E770 B1B8 EFB1 462D A146 C380
___
If I were to add support for this, where would be the best place to
put the configuration option (afsd command line flag, perhaps)?
- a
Derrick J Brashear <[EMAIL PROTECTED]> writes:
> Not currently
>
> On Fri, 16 Mar 2007, Adam Megacz wrote:
>
>>
>> Is there any option for the OpenAFS client
On Mon, 19 Mar 2007, Adam Megacz wrote:
Just wondering... is the Administrator guide's documentation of how
AFS uses the mode bits complete and up-to-date?
http://www.openafs.org/pages/doc/AdminGuide/auagd020.htm#HDRWQ580
It doesn't seem to cover:
1. sticky bit
- AFS stores this, but
Just wondering... is the Administrator guide's documentation of how
AFS uses the mode bits complete and up-to-date?
http://www.openafs.org/pages/doc/AdminGuide/auagd020.htm#HDRWQ580
It doesn't seem to cover:
1. sticky bit
- AFS stores this, but does it have any effect?
2. setuid/s
> Um,
>
> I must be missing something, but why doesn't "vos move" fill the bill.
>
you must be missing something, indeed.
> [...] We want to change the server (hardware), but no[t] the disk library
> (vicepxx). [...]
I also think (thanks, kula) that setting up the new machine as a
fileserver, m
I'm afraid you're going to be disappointed, unless you have only one
OpenAFS server. The OpenAFS clients communicate with whichever server(s)
house the volumes they are trying to use. Volumes contain what looks
like a directory of subtrees with files, directories, and symbolic
links, but they c
On Wed, 14 Mar 2007, Robinson, Eric wrote:
Network connectivity differs significantly between NFS and Samba. With
CIFS/Samba, shares may participate in a DFS tree and appear to the
client as a single unified tree. However, when the client actually
connects to a resource, he is redirected to the
On Wed, 14 Mar 2007, Nicolas DEFFAYET wrote:
HOn Fri, 2007-03-09 at 00:26 -0500, Jeffrey Altman wrote:
The OpenAFS Gatekeepers announce the availability of OpenAFS
version 1.5.16. Source files and available binaries can be
accessed via the web at:
http://www.openafs.org/release/openafs-1
Network connectivity differs significantly between NFS and Samba. With
CIFS/Samba, shares may participate in a DFS tree and appear to the
client as a single unified tree. However, when the client actually
connects to a resource, he is redirected to the IP address of the server
that holds the resour
HI Sir
I started the bos server successfully but while executing " bos setcellname
-server -name ".
It shows "bos:can't open cell database (/usr/local/etc/openafs) .
Although /usr/local/etc/openafs file exists and symlinks required are also
there in the file.
Please help me.
Server not found in database: afs/[EMAIL PROTECTED]: No such
entry in the database
Just ignore this error, its kinit/pam modules trying to do afslog and
tries diffrent names
for the service. You might have a [EMAIL PROTECTED] if cellname and
realmname
only differ in case-ing.
and at
Um,
I must be missing something, but why doesn't "vos move" fill the bill.
Set up the new server, vos move the volumes from the old server and
decommision it. The only catch is that AFS server's can't share vicepxx
partitions at the same time.
Jose Angel Herrero wrote:
Hello everybody,
We
HOn Fri, 2007-03-09 at 00:26 -0500, Jeffrey Altman wrote:
> The OpenAFS Gatekeepers announce the availability of OpenAFS
> version 1.5.16. Source files and available binaries can be
> accessed via the web at:
>
> http://www.openafs.org/release/openafs-1.5.16.html
When did you plan to releas
Derek Atkins <[EMAIL PROTECTED]> writes:
> Adam Megacz <[EMAIL PROTECTED]> writes:
>> So, is there any way to make a backup volume less accessible than its
>> rw? If not, then it means that reducing access to any backed-up file
>> always has to wait until the next backup...
> Nope, there's not.
On Tue, 13 Mar 2007, Marcus Watts wrote:
I think for openafs, it would make sense to have a "enable-pic" configure
flag - that could turn on pic mode globally. That could be used to
The CCOBJ rule is designed for just that; you just need the configure
glue.
On Tue, 13 Mar 2007, Kim Kimball wrote:
Uh oh ... what happens with vos zap for pre-1.4.2?
There was a "rock" missing in one of the calls and so it left some crap
behind; This is actually only true of -force.
___
OpenAFS-info mailing list
OpenAF
Adam Megacz <[EMAIL PROTECTED]> writes:
> If a user removes a file (or restricts access to it by changing an
> ACL), and the file existed prior to the most recent "vos backup", that
> file will still be accessible via the backup volume.
Correct.
> The backup volume can be mounted beneath a direc
22 matches
Mail list logo
