On May 3, 2010, at 11:38 , Steve Simmons wrote:
On May 1, 2010, at 1:35 AM, Brandon S. Allbery KF8NH wrote:
On Apr 30, 2010, at 14:32 , Richard Brittain wrote:
This solves my immediate need, and I'll probably use your mount
point database too, but begs the question of why perl's
File::Find mod
Thanks all,
* Yes, I know kaserver is deprecated, thank you
* To repeat, running IBM AFS anything on Solaris 10 x64 is not possible
* Running kaserver on hosts other than the current two means running
all the database services of AFS on hosts other than the current
two, which leads to all th
On Mon, 3 May 2010 23:04:06 -0400
"Brandon S. Allbery KF8NH" wrote:
> On May 3, 2010, at 09:09 , Frank Burkhardt wrote:
> > is the openafs-fileserver supposed to take advantage of multiple
> > cpu cores?
Yes, however, I think most of the cpu-intensive operations are only in
the RX layer (the net
Derrick Brashear writes:
> On Mon, May 3, 2010 at 11:23 PM, Russ Allbery wrote:
>> Users who create a workgroup named shadow:something and then go to AFS
>> and wonder why fs setacl . shadow:something all doesn't work are
>> unlikely to be easily patched to track by ID instead.
> they should pr
On Mon, May 3, 2010 at 11:23 PM, Russ Allbery wrote:
> Derrick Brashear writes:
>> Russ Allbery wrote:
>>> Derrick Brashear writes:
>
A similar "attack" has been discussed before.
>
pts cg shadow:something
pts chown shadow:something jaltman
>
jaltman now owns jaltman:somethi
"Brandon S. Allbery KF8NH" writes:
> On May 3, 2010, at 09:09 , Frank Burkhardt wrote:
>> is the openafs-fileserver supposed to take advantage of multiple cpu
>> cores?
> Last I heard, only the database servers were capable of true threaded
> operation (and that possibly only in 1.5); the filese
Derrick Brashear writes:
> Russ Allbery wrote:
>> Derrick Brashear writes:
>>> A similar "attack" has been discussed before.
>>> pts cg shadow:something
>>> pts chown shadow:something jaltman
>>> jaltman now owns jaltman:something.
>> This behavior is also really annoying if you have an exte
On Mon, May 3, 2010 at 10:55 PM, Russ Allbery wrote:
> Derrick Brashear writes:
>
>> If it tracked by name.
>
>> A similar "attack" has been discussed before.
>
>> pts cg shadow:something
>> pts chown shadow:something jaltman
>
>> jaltman now owns jaltman:something.
>
> This behavior is also real
On May 3, 2010, at 09:09 , Frank Burkhardt wrote:
is the openafs-fileserver supposed to take advantage of multiple cpu
cores?
Last I heard, only the database servers were capable of true threaded
operation (and that possibly only in 1.5); the fileserver still uses
the old userspace "thread
Derrick Brashear writes:
> If it tracked by name.
> A similar "attack" has been discussed before.
> pts cg shadow:something
> pts chown shadow:something jaltman
> jaltman now owns jaltman:something.
This behavior is also really annoying if you have an external group system
whose names you're
On Mon, May 3, 2010 at 10:19 PM, Jeffrey Altman
wrote:
> On 5/1/2010 6:40 PM, Adam Megacz wrote:
>>
>> Is there any reason why pts won't let system:administrator create groups
>> whose prefix does not match any user?
>>
>> $pts ex blah
>> pts: User or group doesn't exist so couldn't look up id
Jeffrey Altman writes:
> I suspect that the above is a security issue. It means that user 1 can
> be assigned pts id "foo" and if "foo" is deleted (but not foo's groups)
> when user 1 leaves the company, then when user 2 comes along and is
> assigned the unused "foo", s/he will inherit all of th
Jose Calhariz writes:
> On Mon, May 03, 2010 at 07:05:04PM -0700, Russ Allbery wrote:
>> It doesn't work because make libafs_tree only includes the files
>> required for the architecture one runs it on. The OpenAFS Debian
>> packages switched from a full copy of the source tree to using
>> libaf
On 5/1/2010 6:40 PM, Adam Megacz wrote:
>
> Is there any reason why pts won't let system:administrator create groups
> whose prefix does not match any user?
>
> $pts ex blah
> pts: User or group doesn't exist so couldn't look up id for blah
> $pts creategroup blah:booh
> pts: Badly formed
On Mon, May 03, 2010 at 07:05:04PM -0700, Russ Allbery wrote:
> Jose Calhariz writes:
>
> > I used to cross compile openafs modules to amd64/x86_64 linux kernel
> > from a i386 userland. I am using the kernel-package command to produce
> > a debian package with the openafs modules. The last tim
Jose Calhariz writes:
> I used to cross compile openafs modules to amd64/x86_64 linux kernel
> from a i386 userland. I am using the kernel-package command to produce
> a debian package with the openafs modules. The last time I compiled new
> modules was with openafs 1.4.7, for kernel 2.6.26.
>
I used to cross compile openafs modules to amd64/x86_64 linux kernel
from a i386 userland. I am using the kernel-package command to
produce a debian package with the openafs modules. The last time I
compiled new modules was with openafs 1.4.7, for kernel 2.6.26.
Now I try to do the same with op
Mike Pliskin wrote:
I don't feel qualified to write a tutorial on something I have exactly zero
experience with :), but some my comments:
- Andrew's pointers to a typical AFS folder structure are really helpful
- the note about AlwaysAttach file is helpful as well, and the current doc
says yo
On Mon, May 3, 2010 at 6:42 PM, Adam Megacz wrote:
>
> Derrick Brashear writes:
When creating a group foo:bar as admin, I often find that I have to
use the -owner parameter to see the owner to foo(something).
>>>
>>> I see. Is it official AFS policy that this usage is supported?
>>
>>
Derrick Brashear writes:
>>> When creating a group foo:bar as admin, I often find that I have to
>>> use the -owner parameter to see the owner to foo(something).
>>
>> I see. Is it official AFS policy that this usage is supported?
>
> Which usage? I'm not sure what you're asking.
Sorry, let me
Hi Jason,
I don't feel qualified to write a tutorial on something I have exactly zero
experience with :), but some my comments:
- Andrew's pointers to a typical AFS folder structure are really helpful
- the note about AlwaysAttach file is helpful as well, and the current doc
says you need a sp
On Mon, 3 May 2010 15:47:41 -0400 (EDT)
Richard Brittain wrote:
> Bear in mind that I got similarly broken results from Solaris 9 and
> OSX/BSD verion of 'find' when scanning the top levels of the cell, so
> it isn't unique to GNU. The OSX find might include GNU code - it has
> a lot of similar
On Mon, 3 May 2010, Steve Simmons wrote:
File::Find module works fine, while 'find' breaks. Underneath they are
presumably making very similar system calls.
. . . . File::Find has gone through a lot of development aimed at reducing its
impact on the system, whereas in my experience the GNU
"Karl Tißner" writes:
> We use Debian 5/6, which is delivered with helpful scripts afs-newcell
> afs-rootvol. But - do I have to install the "afs-newcell" (I do dot want
> a new cell, I already have one), do I have to call "afs-rootvol" (I dont
> need a new root.afs, I want to replicate the other
My thoughts...
if the 1.6 branch is about to come out, then that version number change
would be a good place to make the integrated login change.
That said, as long as it's well announced, I don't have a problem w. the
change being made in 1.5.whatever ... now that I've learned how to do
transfor
The OpenAFS for Windows distributions come in two different installation
packaging flavors. The .EXE installer based on NSIS defaults integrated
logon to be disabled. The .MSI installer based on WiX defaults
integrated logon to be enabled. The reason for this difference is
historical. The MSI i
On Sun, May 2, 2010 at 5:11 PM, Adam Megacz wrote:
>
> Markus Koeberl writes:
>>> $pts creategroup blah:booh
>>
>> Maybe what you want is to create a group blah.
>
> No -- I actually want it to be called blah:booh.
>
> Making sure group names always have a colon in them is important in
> cells
On Mon, 03 May 2010 11:34:18 +0200
"Karl Tißner" wrote:
> The existing documentation I found explains the replication, if more
> than one server already exists, or the installation of a standalone
> new server. But how do I seamless integrate a new server in my cell?
I'm not sure what the differ
On May 1, 2010, at 1:35 AM, Brandon S. Allbery KF8NH wrote:
> On Apr 30, 2010, at 14:32 , Richard Brittain wrote:
>> This solves my immediate need, and I'll probably use your mount point
>> database too, but begs the question of why perl's
>> File::Find module works fine, while 'find' breaks. U
On Mon, 3 May 2010 15:23:29 +0300 (EEST)
Atro Tossavainen wrote:
> Mon May 3 15:18:31 2010 VL_RegisterAddrs rpc failed; The IP address exists
> on a different server; repair it
> Mon May 3 15:18:31 2010 VL_RegisterAddrs rpc failed; See VLLog for details
My guess is that this would be the resu
On Mon, May 3, 2010 at 8:23 AM, Atro Tossavainen
wrote:
> Hello all,
>
> I am pleased(?) to say that the SPARC Solaris 8 hosts running IBM AFS
> are gone and all @ our place is now on x86_64 Solaris 10 hosts running
> OpenAFS 1.4.12.
>
> I am still experiencing kaserver database issues of the same
Hi AFS-Fans,
is the openafs-fileserver supposed to take advantage of multiple cpu cores?
I got a new big server which I tried to use as a afs-fileserver (just for
fun - the server will be dedicated to something else later). However, 7 of
its 8 cores seems to idle all the time - even when 7 afs-cl
On 5/3/2010 8:23 AM, Atro Tossavainen wrote:
> Hello all,
>
> I am pleased(?) to say that the SPARC Solaris 8 hosts running IBM AFS
> are gone and all @ our place is now on x86_64 Solaris 10 hosts running
> OpenAFS 1.4.12.
>
> I am still experiencing kaserver database issues of the same kind as
>
Hello all,
I am pleased(?) to say that the SPARC Solaris 8 hosts running IBM AFS
are gone and all @ our place is now on x86_64 Solaris 10 hosts running
OpenAFS 1.4.12.
I am still experiencing kaserver database issues of the same kind as
before, with one of the boxes reporting unknown key version
Hello,
I am looking for a tutorial or a step-to-step instruction for adding a
replication server to an existing singe OpenAFS server installation. This is an
heavily used production server, and so I am a bit afraid of doing something
wrong (losing the VLDB, for example).
The existing documenta
35 matches
Mail list logo
