is there any diference in using your integrated ldap auth than tipical pam+ldap setup?
I can't see the advantage of using pam here.
is there any diference in using your integrated ldap auth than tipical pam+ldap setup?
i've installed RC1 and when configuring ldap in auth settings i can't see any way to filter ldap query. on most servers we usually only allow to appear on system (getent passwd) a subset of our whole user tree.
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of proxmox-ve-2.6.32:
proxmox-ve-2.6.32 depends on pve-manager; however:
Package pve-manager is not configured yet.
dpkg: error processing proxmox-ve-2.6.32 (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libpve-access-control:
libpve-access-control depends on pve-cluster; however:
Package pve-cluster is not configured yet.
dpkg: error processing libpve-access-control (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of qemu-server:
qemu-server depends on pve-cluster; however:
Package pve-cluster is not configured yet.
dpkg: error processing qemu-server (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of redhat-cluster-pve:
redhat-cluster-pve depends on pve-cluster; however:
Package pve-cluster is not configured yet.
dpkg: error processing redhat-cluster-pve (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of vzctl:
vzctl depends on pve-cluster; however:
Package pve-cluster is not configured yet.
dpkg: error processing vzctl (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of resource-agents-pve:
resource-agents-pve depends on redhat-cluster-pve; however:
Package redhat-cluster-pve is not configured yet.
dpkg: error processing resource-agents-pve (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of fence-agents-pve:
fence-agents-pve depends on redhat-cluster-pve; however:
Package redhat-cluster-pve is not configured yet.
dpkg: error processing fence-agents-pve (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of clvm:
clvm depends on redhat-cluster-pve; however:
Package redhat-cluster-pve is not configured yet.
dpkg: error processing clvm (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libpve-storage-perl:
libpve-storage-perl depends on clvm; however:
Package clvm is not configured yet.
dpkg: error processing libpve-storage-perl (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
pve-cluster
pve-manager
proxmox-ve-2.6.32
libpve-access-control
qemu-server
redhat-cluster-pve
vzctl
resource-agents-pve
fence-agents-pve
clvm
libpve-storage-perl
Install these packages without verification [y/N]? y
Err http://debian.mirror.iweb.ca lenny/main netselect 0.3.ds1-12.1
404 Not Found [IP: 70.38.0.135 80]
Err http://debian.mirror.iweb.ca lenny/main netselect-apt 0.3.ds1-12.1
404 Not Found [IP: 70.38.0.135 80]
Failed to fetch http://debian.mirror.iweb.ca/debian/pool/main/n/netselect/netselect_0.3.ds1-12.1_amd64.deb 404 Not Found [IP: 70.38.0.135 80]
Failed to fetch http://debian.mirror.iweb.ca/debian/pool/main/n/netselect/netselect-apt_0.3.ds1-12.1_all.deb 404 Not Found [IP: 70.38.0.135 80]
E: Some files failed to download
Hi!, i have a little question for proxmox forum guys
We're testing the new release candidate to use it in the future in our production servers.
We've installed proxmox 2.0 -8d4f53a0-20 (downloaded from the proxmox website).
But... we faced a problem when we need to install iscsi-scst package and have it as a module too, to export a iscsi target (tape device in this case).
Anyone could help us? please we're really interested in using proxmox 2.0
Thanks in advance!
Maximiliano (from Argentina).
P/D: any estimated date for the release of version 2.0??
We was also unable to compile SCST for newer kernels, so we never included that in newer kernel releases. Instead we include the iscsi_trgt module. ButBut... we faced a problem when we need to install iscsi-scst package and have it as a module too, to export a iscsi target (tape device in this case).