Just for reference, let me add SLES12 in this discussion too. I recently
installed a SLES12 machine and there it should be configured in systemd.
In systemd you don’t have the inittab. The user is to be logged on on ttyS0, so
you need to ensure serial-getty@ttyS0.service is started during boot.
On 16 August 2017 at 00:47, Rick Troth wrote:
>
> It's arguable that having to enter a password at a "login:" prompt would
> actually be /less/ secure.
>
Indeed. It can be argued, and I did that a lot :-) A lot of the security
rituals we follow were created for problems that
Greetings Donald,
The model that many debian packages has preferred over the years is that
of a "rootless" security model. In this configuration you must log in as
a user and then "sudo" to root. In order to do this you must be in the
sudoers group or be explicitly mentioned in
> How/what do I have to configure so logging onto the 3270 console gets me
> logged into root in a bash shell automatically? Similar question for
> sometimes the system has problems coming up and it's prompting for
"Enter
> root password or CTL-D to continue". How can that be bypassed so it just
Thanks Paul,
Our security model does not allow sudo. Instead we use something called
pmrun which requires authentication across a network. (Don't get me started
on the pitfalls of that)
sudo nor pmrun address the issue of the "*Enter root password for
maintenance, or CTL-D to continue*" prompt
On 08/16/2017 12:04 PM, Donald Russell wrote:
> Our security model does not allow sudo. Instead we use something called
> pmrun which requires authentication across a network. (Don't get me started
> on the pitfalls of that)
PBRUN at least fits the model of "don't sign on as root - sign on as
Dear Rick,
One slight embellishment...
On Wed, 16 Aug 2017, Rick Troth wrote:
Conflicting requirements between your security people and your
business continuity people. Lock them in a room together and let them
fight it out.
Either sell tickets or televise (pay-per-view :^)
Kindest
I think that would be a problem. Indeed these solutions will not work when the
boot phase is stuck in INITRD.
We have had boot problems in the past, either because of an error in /etc/fstab
or because of boot disk errors. In those cases we logoff the linux machine and
mount the boot disk(s) in
Greetings Berry,
That is the better way to go!
Regards,
Flint
On Wed, 16 Aug 2017, van Sleeuwen, Berry wrote:
Date: Wed, 16 Aug 2017 19:43:32 +
From: "van Sleeuwen, Berry"
Reply-To: "linux-390@vm.marist.edu"
To:
Greetings all,
We use Tivoli Workload Scheduler (TWS/d) on our Linux on z servers. Alas, the
batchman process wakes up every 10-15 seconds and uses ~10% CPU on each and
every server, day in and day out.
Does anyone else use batchman, and do you see the same CPU use?
Very best regards,
Mark
10 matches
Mail list logo