For quite some time I’ve been using FreeNAS to provide services as a NAS over
ethernet and SAN over Fibre Channel to CentOS 7 servers each using their own
export, not sharing the same one.
It’s time for me to replace my hardware and I have a new R720XD that I’d like
to use in the same capacity
Le 10/01/2019 à 22:17, Stephen John Smoogen a écrit :
> I updated to CentOS 7.6 and something must have changed in the base
> OS setup that prevents vsftpd from allowing logins for accounts
> with /sbin/nologin as their shell.
Maybe this could be your solution. Here's the relevant lines from my
v
I think the pam_shells test is really a lazy test for daemons. There's
already a blacklist in /etc/vsftpd/user_list but it's incomplete. (It lacks
a LOT of common system services such as named, sshd, and dbus.) I suggest
replacing pam_shells with a test for UID < 1000:
authrequired
More digging (now that I have a better handle on how to ask the question)
reveals this bug against documentation and release notes for 7.6 to alert
updaters about this breaking change for vsftpd:
https://bugzilla.redhat.com/show_bug.cgi?id=1647485
The last comment there, #15 by "Roy":
For a
--On Thursday, January 10, 2019 4:17 PM -0500 Stephen John Smoogen
wrote:
So I think this is a side effect of a long term argument of the security
nature of /sbin/nologin
https://serverfault.com/questions/328395/nologin-in-etc-shells-is-dangero
us-why
https://lists.fedoraproject.org/archives/
On 1/10/19 10:20 AM, Simon Matter via CentOS wrote:
RAID1 is going to have type FD00 (Linux RAID) whereas EFI firmware
expects type EF00 (EFI System Partition) to boot from.
I think you're referring to MBR partition types. I'm not certain, but I
don't see those values in a GPT.
No, it's GPT. W
On Thu, 10 Jan 2019 at 16:09, Kenneth Porter wrote:
> I updated to CentOS 7.6 and something must have changed in the base OS
> setup that prevents vsftpd from allowing logins for accounts with
> /sbin/nologin as their shell. I had to add that to /etc/shells so that
> such
> accounts could FTP ag
I updated to CentOS 7.6 and something must have changed in the base OS
setup that prevents vsftpd from allowing logins for accounts with
/sbin/nologin as their shell. I had to add that to /etc/shells so that such
accounts could FTP again. That file is in the setup package. Did it include
/sbin
> It doesn't specifically. Anaconda will create two EFI boot entries,
> each referring to one of the mirror components:
>
> # efibootmgr -v
> BootCurrent: 0001
> Timeout: 1 seconds
> BootOrder: 0001,
> Boot* CentOS Linux
> HD(1,GPT,534debcc-f3d6-417a-b5d4-10b4ba5c1f7d,0x800,0x5f000)/File(\
On 1/10/19 8:35 AM, Simon Matter via CentOS wrote:
Are you sure?
Yes.
How is the EFI firmware going to know about the RAID1?
It doesn't specifically. Anaconda will create two EFI boot entries,
each referring to one of the mirror components:
# efibootmgr -v
BootCurrent: 0001
Timeout:
On Thu, 10 Jan 2019 at 11:35, Simon Matter via CentOS
wrote:
> > On 1/9/19 2:30 AM, Gary Stainburn wrote:
> >> 1) The big problem with this is that it is dependant on sda for booting.
> >> I
> >> did find an aritcle on how to set up boot loading on multiple HDD's,
> >> including cloning /boot/ef
ok
a good hint.
I will test it monday.
Ralf
Von meinem iPhone gesendet
> Am 10.01.2019 um 18:23 schrieb Mogens Kjaer :
>
>> On 1/10/19 11:32 AM, Ralf Prengel wrote:
>> yum install doesn't work running the script via cron allthough yum remove
>> works.
>
> Is the network up when the script ex
On 1/10/19 11:32 AM, Ralf Prengel wrote:
yum install doesn't work running the script via cron allthough yum
remove works.
Is the network up when the script executes?
Mogens
--
Mogens Kjaer, m...@lemo.dk
http://www.lemo.dk
___
CentOS mailing list
C
> On 1/9/19 2:30 AM, Gary Stainburn wrote:
>> 1) The big problem with this is that it is dependant on sda for booting.
>> I
>> did find an aritcle on how to set up boot loading on multiple HDD's,
>> including cloning /boot/efi but I now can't find it. Does anyone know
>> of a
>> similar article?
Hallo,
I m using a script to install docker after a reboot.
The script is starting and working.
The problem:
yum install doesn't work running the script via cron allthough yum
remove works.
Starting the script manual works fine .
Has anyone a hint for me?
Thanks
Ralf
xxx
SHELL=/bin/bash
P
Zitat von Pete Biggs :
which switch is the right one for Centos 7.6 to finish the
installation.
Every Installation needs an acknowledgement at the end when the
network configuration is shown while installing with grafics.
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linu
16 matches
Mail list logo
