Hi,
This morning my day began quite badly, since my main production server wasn't
responsive anymore. For public hosting I'm using a "Dedibox Pro" server at the
french provider Online that's recently been acquired by Scaleway. I'm currently
managing half a dozen public servers at that provider,
I'll answer that myself, since I just got to the root of the problem. I just
got contacted by the hosting company, and they made a mistake. So tl;dr I just
have to wait until things get back to normal.
In the meantime, I would be curious though : how *do* you read system logs in
chroot ?
Cheer
> Yes, let me validate Mr. Kovacs comment. I am aware of the shortcomings
> of NIS in the area of security. Let me provide some information on the
> topography of my network and my reasoning for choosing NIS/NFS. Perhaps
> an alternative may be suggested to meet my needs without totally
>
On Apr 12, 2020, at 05:47, Pete Biggs wrote:
> There are other options than LDAP, and servers other than OpenLDAP, but
> LDAP is the de facto standard.
Unfortunately, OpenLDAP as a server is deprecated in C8, and isn’t packaged
anymore. Upstream they point customers to their directory service,
On Sun, 2020-04-12 at 08:13 -0400, Jonathan Billings wrote:
> On Apr 12, 2020, at 05:47, Pete Biggs wrote:
> > There are other options than LDAP, and servers other than OpenLDAP, but
> > LDAP is the de facto standard.
>
> Unfortunately, OpenLDAP as a server is deprecated in C8, and isn’t
> packa
Dear P.,
NIS is out. Don’t ask me why. Ask the developer.
On our cluster it is still in use, but for the next instance
I must use LDAP or compile the packages by my self.
Best wishes
Andy
> Am 12.04.2020 um 14:28 schrieb Pete Biggs :
>
> On Sun, 2020-04-12 at 08:13 -0400, Jonathan Billings
On 4/12/20 1:16 AM, kikinovak via CentOS wrote:
In the meantime, I would be curious though : how*do* you read system logs in
chroot ?
As far as I know: the same way you do when you're not in a chroot.
*Reading* logs doesn't seem to involve connecting to journald, so:
less /var/log/messag
On 4/9/20 6:31 AM, Andreas Haumer wrote:
...
I'm neither a fail2ban nor a SELinux expert, but it seems the
standard fail2ban SELinux policy as provided by CentOS 7 is not
sufficient anymore and the recent updates did not correctly
update the required SELinux policies.
I could report this as bug,
On 2020-04-12 08:13, Jonathan Billings wrote:
On Apr 12, 2020, at 05:47, Pete Biggs wrote:
There are other options than LDAP, and servers other than OpenLDAP, but
LDAP is the de facto standard.
Unfortunately, OpenLDAP as a server is deprecated in C8, and isn’t packaged
anymore. Upstream th
On Sun, Apr 12, 2020 at 6:43 PM Mark LaPierre wrote:
> On 2020-04-12 08:13, Jonathan Billings wrote:
> > On Apr 12, 2020, at 05:47, Pete Biggs wrote:
> >> There are other options than LDAP, and servers other than OpenLDAP, but
> >> LDAP is the de facto standard.
> >
> > Unfortunately, OpenLDAP
On 2020-04-12 21:49, John Pierce wrote:
It appears that they just pasted a new name on an old horse. It's still
LDAP.
yes, its the standardized LDAP protocol...
it is, however, a completely different implementation, so no, its not
OpenLDAP, which is a specific implementation.
Oh insert D
11 matches
Mail list logo
