This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-API] Just signed up + first question.

To: xen-api@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-API] Just signed up + first question.
From: "frenchyp@xxxxxxxxx" <frenchyp@xxxxxxxxx>
Date: Tue, 17 Jul 2007 09:51:21 -0700
Delivery-date: Tue, 17 Jul 2007 09:50:01 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-api-request@lists.xensource.com?subject=help>
List-id: Discussion of API issues surrounding Xen <xen-api.lists.xensource.com>
List-post: <mailto:xen-api@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-api-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird (X11/20070604)
Hello everyone.

I just joined this list, so I thought I would introduce myself quickly. My name is Pierre, I am from Seattle. I have a professional and personal interest in virtualization solutions. I have a little experience with openvz, and I am currently interested in Xen (3.1.0) and xen-api.

My question concerns PAM authentication for xen-api.
I use this line in my xend-config.sxp to turn on xen-api and PAM authentication:
   (xen-api-server ((9363 pam )))
and I created a /etc/pam.d/xend file to handle login attempts.
However, it seems that xen-api insists on using the /etc/pam.d/login file instead on mine. Is that hardcoded in the code, or is there something I overlooked in my configuration?

Thank you for your help.


xen-api mailing list

<Prev in Thread] Current Thread [Next in Thread>