I'm trying to get OpenAFS 1.6.1 running on a new (additional)
Linux server. I've got the keyfiles etc copied over and can start
the bosserver, but it ignores all bos commands sent remotely.
I'm guessing that is because BosLog says:
Listening on 127.0.0.1:7007
I tried adding the real
On Thu, 30 Aug 2012 09:43:51 -0500
John Tang Boyland boyl...@pabst.cs.uwm.edu wrote:
I'm trying to get OpenAFS 1.6.1 running on a new (additional)
Linux server. I've got the keyfiles etc copied over and can start
the bosserver, but it ignores all bos commands sent remotely.
I'm guessing that
Michael Meffie mmef...@sinenomine.net wrote:
] On Thu, 30 Aug 2012 09:43:51 -0500
] John Tang Boyland boyl...@pabst.cs.uwm.edu wrote:
]
] I'm trying to get OpenAFS 1.6.1 running on a new (additional)
] Linux server. I've got the keyfiles etc copied over and can start
] the bosserver, but it
On Thu, 30 Aug 2012 13:45:47 -0500
John Tang Boyland boyl...@pabst.cs.uwm.edu wrote:
] What does netstat say about which interfaces are bound to port 7007
] for udp?
Sorry, I don't know how to use netstat:
As root:
netstat -lpn | grep bosserver
(or 'grep pid')
--
Andrew Deason
On Thu, 30 Aug 2012 13:45:47 -0500
John Tang Boyland boyl...@pabst.cs.uwm.edu wrote:
] What does netstat say about which interfaces are bound to port 7007
] for udp?
Sorry, I don't know how to use netstat:
# netstat | grep 7007
# netstat --udp
Hello John,
By default bosserver will listen
Michael Meffie mmef...@sinenomine.net wrote:
] On Thu, 30 Aug 2012 13:45:47 -0500
] John Tang Boyland boyl...@pabst.cs.uwm.edu wrote:
] ] What does netstat say about which interfaces are bound to port 7007
] ] for udp?
]
] Sorry, I don't know how to use netstat:
]
] # netstat | grep 7007
]
[Adding openafs-info because this discussion is relevant to a broader
audience than simply the afs3-standardization group. The full thread
can be found at
https://lists.openafs.org/pipermail/afs3-standardization/2012-August/000898.html
for those not subscribed to
We're moving from OpenLDAP to ActiveDirectory (let's not get into the
ethics here...), so we need all of our non-Windows servers to
authenticate against decentralized domain controllers. I've successfully
implemented winbind as an authentication mechanism, but lost the
niceness of having a
Ben Howell howel...@gmail.com writes:
Is it possible to reproduce the combination of pam_krb5 and
pam_afs_session to create a PAG and generate a ticket and AFS token on
login using winbind's KRB5 mechanism? I think at this point the only
thing I haven't done is write my own module from
While this is true, people who get paid a lot more than I do decided we
shouldn't be pointing authentication to individual machines and instead
use domain lookups, which winbind does nicely. I was able to replicate
the old functionality by pointing the pam stack directly to
dc01.domain.com,
On Thu, Aug 30, 2012 at 7:54 PM, Ben Howell howel...@gmail.com wrote:
While this is true, people who get paid a lot more than I do decided we
shouldn't be pointing authentication to individual machines and instead use
domain lookups, which winbind does nicely. I was able to replicate the old
That's part of the default krb5.conf, specifying kdc = hostname, as well
as master_kdc, etc. for ever host that serves as KDC. I do have SRV
records in place, and I know that from our old implementation that SRV
lookups DO work the way they're supposed to, but I'm not paid enough to
argue with
Ben Howell howel...@gmail.com writes:
That's part of the default krb5.conf, specifying kdc = hostname, as well
as master_kdc, etc. for ever host that serves as KDC. I do have SRV
records in place, and I know that from our old implementation that SRV
lookups DO work the way they're supposed
Jeffrey Altman jalt...@your-file-system.com writes:
For any given protocol standardization proposal, substantial expertise
and time is required to perform proper analysis and review let alone
write a document in the first place. On top of that it is very
difficult to anticipate all of the
Maintaining OpenAFS involves, among other things:
* Kernel code as well as userspace code for various UNIXes.
* Mac OS X development (with quite a bit of OS internals involvement).
* Windows kernel file system development.
* High-performance threaded code with a complex lock model.
* A
15 matches
Mail list logo
