On Mon, Jul 23, 2012 at 10:25:34AM +0100, Malcolm Beattie wrote:
There's a section of the sshd(8) man page beginning:
Regardless of the authentication type, the account is checked
to ensure that it is accessible. An account is not accessible
if it is locked, listed in DenyUsers or
Using the Linux cpuplugd Daemon to manage CPU and memory resources from
z/VM Linux guests
The following paper is available at
developerWorks
www.ibm.com/developerworks/linux/linux390/perf/tuning_cpuhotplug.html#cpuplugd
IBM Information Center
Hi,
This question is for those who are running SMT to service your SLES11 virtual
Linux servers. Do you maintain the repositories on x86 servers, z/Linux
servers, or other? Are there any security, capacity, or usability issues that
determined how your SMT is deployed? Thanks.
Ray Mrohs
Cross-posted to Linux-390, IBVVM, and IBM-MAIN discussion lists.
To: VM Workshop attendees and those who would like to attend,
Background: The VM Workshop is a very inexpensive (registration only $100 each
of the last 2 years), all-volunteer, 2.5 day technical conference held in
mid-June and
Dear Ray,
I host the SMT on a z/LINUX machine which is called installation directory.
In order to get enough disk space for the repositories, the disk is put on
a FBA device (around 150 GB) and setup as LVM in order to make it easily
expandable.
I host on that server s390x and also x86_64
Dear Philip
I tried to look into that deeper but I could not find any information about
how to configure that:
nsswitch.conf states:
shadow: ldap files
A getent delivers:
$ getent shadow bilek1
bilek1:*:::0
There is no difference if the user is locked or not. In case I state a
userid
Hi Malcom,
I will give this work around a try. But the idea was that a simple CMS 'rac
alu userid' revoke would deny access of a user to all systems.
With the workaround I need again a sort of exec that connects/disconnects
the user to a NOLOG group. Or I need to disable the whole feature with