From: Lon Hohberger <lhh@redhat.com>
To: cluster-devel.redhat.com
Subject: [Linux-cluster] Re: [Cluster-devel] PAM and NSS for clusters
Date: Mon, 17 Nov 2008 13:05:03 -0500 [thread overview]
Message-ID: <1226945103.25751.106.camel@ayanami> (raw)
In-Reply-To: <Pine.LNX.4.64.0811171541320.7841@trider-g7>
On Mon, 2008-11-17 at 15:43 +0100, Fabio M. Di Nitto wrote:
> Hi,
>
> On Mon, 17 Nov 2008, Kadlecsik Jozsef wrote:
> > http://www.kfki.hu/~kadlec/sw/cluster/
>
> This looks very interesting. Did you consider submitting those patches
> upstream?
I agree - it's very cool. It can't be used for bringing up GFS
(chicken/egg), but for permissions on the file system and such, it looks
pretty good.
What's neat is that you don't need centralized management server(s) :)
> I am pretty sure some of them (like PAtch 1) should be accepted right
> away given they fix what could be a bug and reduce your delta in time.
0005 looks like it statically defines /etc/cluster_rootdir, but I am
probably reading the patch incorrectly. I don't know PAM well enough to
answer this question, so I need to ask it anyway:
* Is there a way to make the root directory configurable, or are admins
expected to link /etc/cluster_rootdir to /gfs/system (or whatever they
choose)?
Side note:
I wonder if it would get accepted in a distribution ... that would be
neat. Since it doesn't actually require cluster software itself (just a
shared file system), then it shouldn't be that hard... in theory :/
-- Lon
next prev parent reply other threads:[~2008-11-17 18:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-17 14:33 [Cluster-devel] PAM and NSS for clusters Kadlecsik Jozsef
2008-11-17 14:43 ` Fabio M. Di Nitto
2008-11-17 14:53 ` [Linux-cluster] " Kadlecsik Jozsef
2008-11-17 18:05 ` Lon Hohberger [this message]
2008-11-17 19:26 ` Kadlecsik Jozsef
2008-11-17 22:58 ` Mark Hlawatschek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1226945103.25751.106.camel@ayanami \
--to=lhh@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.