Working with different Linux Distributions makes the life harder.
So far I have found out that 'poweroff' & 'reboot' has the same behaviour on
Linux/Unix/BSDs.
Best Regards,
Strahil Nikolov
На 15 юни 2020 г. 5:22:28 GMT+03:00, John Pierce написа:
>On Sun, Jun 14, 2020 at 6:19 PM Pete Biggs
On Sun, Jun 14, 2020 at 6:19 PM Pete Biggs wrote:
>
> > I'm quite sure that in original Berkeley Unix, as on the VAX 11/780, halt
> > was an immediate halt of the CPU without any process cleanup or file
> system
> > umounting or anything. Early SunOS (pre-Solaris) was like this, too.
> >
> The
> On Jun 14, 2020, at 19:55, Jay Hart wrote:
>>
>> I am having some network connectivity issues that manifest itself through
>> ping, wget, dnf,
>> etc.
>> The symptoms are intermittent ability to ping, was wget, or connect to
>> repositories.
>>
>> Where this inquiry is going is: If your
On Jun 14, 2020, at 19:55, Jay Hart wrote:
>
> I am having some network connectivity issues that manifest itself through
> ping, wget, dnf, etc.
> The symptoms are intermittent ability to ping, was wget, or connect to
> repositories.
>
> Where this inquiry is going is: If your internal
This might be of use to somebody. The Readme includes mention of some
handy utilities for checking your database files.
https://github.com/SpareSimian/user-group-migration
___
CentOS mailing list
CentOS@centos.org
> I'm quite sure that in original Berkeley Unix, as on the VAX 11/780, halt
> was an immediate halt of the CPU without any process cleanup or file system
> umounting or anything. Early SunOS (pre-Solaris) was like this, too.
>
The SunOS 4.1.2 man page for halt says
NAME
halt - stop
On 15-06-2020 4:49, Manuel Wolfshant wrote:
[...]
The testing machines are IBM blades, model H21 and H21XM. Initial
tests were performed on the H21 with 16 GB RAM; during the last 6=7
weeks I've been using the H21XM with 64 GB. In all cases the guests
were fully updated CentOS 7 -- initially
On Sun, Jun 14, 2020 at 5:20 PM Pete Biggs wrote:
>
> > fwiw, i've always used 'init 0' to shut down all sorts of unix/linux
> > systems.
>
> In EL7/EL8, init is now a symlink as well because everything is
> controlled by systemd.
>
> > On old school unix, and I think even early Linux, halt
> fwiw, i've always used 'init 0' to shut down all sorts of unix/linux
> systems.
In EL7/EL8, init is now a symlink as well because everything is
controlled by systemd.
> On old school unix, and I think even early Linux, halt was an
> /immediate/ halt, as in catch fire. might as well hit
On Mon, 2020-06-15 at 01:32 +0200, Leon Fauster via CentOS wrote:
> Working with different OSs can be quite challenging (mentally :-)).
>
> I wonder why the command "halt" has not same result between EL6 and EL8.
>
> To shutdown the vm or workstation in EL8 i must use "shutdown now".
>
> Who
I am having some network connectivity issues that manifest itself through ping,
wget, dnf, etc.
The symptoms are intermittent ability to ping, was wget, or connect to
repositories.
Where this inquiry is going is: If your internal network is using 192.168.1 or
10..50.10, what
should be in
On Sun, Jun 14, 2020 at 4:32 PM Leon Fauster via CentOS
wrote:
> Working with different OSs can be quite challenging (mentally :-)).
>
> I wonder why the command "halt" has not same result between EL6 and EL8.
>
> To shutdown the vm or workstation in EL8 i must use "shutdown now".
>
fwiw, i've
Working with different OSs can be quite challenging (mentally :-)).
I wonder why the command "halt" has not same result between EL6 and EL8.
To shutdown the vm or workstation in EL8 i must use "shutdown now".
Who mandates this behavior in terms of configuration file?
--
Leon
On 6/14/20 4:41 PM, Richard wrote:
Date: Sunday, June 14, 2020 17:26:42 -0400
From: Jay Hart
On 6/14/20 1:39 PM, Jay Hart wrote:
You may need to modify /etc/shadow for consistency.
I don't know what to do here. Need some guidance please.
Run "vipw -s" and make the same change to
On Sun, 2020-06-14 at 17:26 -0400, Jay Hart wrote:
> > On 6/14/20 1:39 PM, Jay Hart wrote:
> > > You may need to modify /etc/shadow for consistency.
> > >
> > > I don't know what to do here. Need some guidance please.
> >
> > Run "vipw -s" and make the same change to that file's record for
>
>
>> Date: Sunday, June 14, 2020 17:26:42 -0400
>> From: Jay Hart
>>
>>> On 6/14/20 1:39 PM, Jay Hart wrote:
You may need to modify /etc/shadow for consistency.
I don't know what to do here. Need some guidance please.
>>>
>>>
>>> Run "vipw -s" and make the same change to that
> Date: Sunday, June 14, 2020 17:26:42 -0400
> From: Jay Hart
>
>> On 6/14/20 1:39 PM, Jay Hart wrote:
>>> You may need to modify /etc/shadow for consistency.
>>>
>>> I don't know what to do here. Need some guidance please.
>>
>>
>> Run "vipw -s" and make the same change to that file's
> On 6/14/20 1:39 PM, Jay Hart wrote:
>> You may need to modify /etc/shadow for consistency.
>>
>> I don't know what to do here. Need some guidance please.
>
>
> Run "vipw -s" and make the same change to that file's record for ABCLast.
>
In /etc/passwd the directory was shown in plain text. So
On 6/14/20 1:39 PM, Jay Hart wrote:
You may need to modify /etc/shadow for consistency.
I don't know what to do here. Need some guidance please.
Run "vipw -s" and make the same change to that file's record for ABCLast.
___
CentOS mailing list
I modified a users name on my system. From ABCLast, to ALast (used as an
example).
I modified the username, then the group name of the user (to align with the new
name), and then I
moved the users home directory from /home/ABCLast, to /home/ALast. Then using
vipw, edited the
home directory to
On Sun, 2020-06-14 at 17:39 +0100, Phil Perry wrote:
> yum --enablerepo=\* clean all
Thanks, that worked
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
Hello
For the past months I've been testing upgrading my Xen hosts to
CentOS 7 and I face an issue for which I need your help to solve.
The testing machines are IBM blades, model H21 and H21XM. Initial
tests were performed on the H21 with 16 GB RAM; during the last 6=7
weeks I've
On 14/06/2020 17:09, Robin Lee wrote:
On Fri, 2020-06-12 at 09:20 +0200, Robin Lee wrote:
Today when I ran yum update two packages came up microcode_ctl
and unbound-libs. The updating process went fine until it outputted
Running transaction
Updating : 2:microcode_ctl-2.1-61.6.el7_8.x86_64
On Fri, 2020-06-12 at 09:20 +0200, Robin Lee wrote:
> Today when I ran yum update two packages came up microcode_ctl
> and unbound-libs. The updating process went fine until it outputted
>
> Running transaction
> Updating : 2:microcode_ctl-2.1-61.6.el7_8.x86_64
>
> then it just froze. I
Il 12/06/20 18:59, Gordon Messmer ha scritto:
On 6/12/20 2:16 AM, Thomas Stephen Lee wrote:
Do we need an upgrade ?
Can you restate your question so that it's clear what version you are
running, what hardware you are running it on, what you expect to happen,
and what is happening
25 matches
Mail list logo
