similar to: Logwatch and System uptime

On Mon, June 15, 2015 11:16 am, Pete Geenhuizen wrote: > Enable it in /usr/share/logwatch/default.conf/services/zz-runtime.conf Thanks a lot! Helps you to be aware that you definitely missed something important if you haven't the box rebooted during more than 45-60 days... Valeri > > Pete > > On 06/15/15 09:58, James B. Byrne wrote: >> CentOS-6.6 >> >> Can

Enable it in /usr/share/logwatch/default.conf/services/zz-runtime.conf Pete On 06/15/15 09:58, James B. Byrne wrote: > CentOS-6.6 > > Can logwatch be configured to display the system uptime as part of the > reporting prologue? If not then what would be the recommended way of > including this information in a daily logwatch report? > > -- If money can fix it, it's not

I upgraded from 7.3 to 7.4 over the weekend.? Everything went well except that I can't login because the screen is black with a cursor. If reboot boot the 7.3 kernel 3.10.0-514.26.2.el7.x86_64 kernel everything works just fine, so my guess is that there's a kernel issue with the hardware, specifically the Skylake processor. Has anyone else run into this problem and if so can how I

On 01/18/18 09:01, Johnny Hughes wrote: > On 01/18/2018 07:51 AM, Phelps, Matthew wrote: >> On Thu, Jan 18, 2018 at 5:03 AM, Johnny Hughes <johnny at centos.org> wrote: >> >> So, if we applied the previous microcode update, and all our machines >> rebooted OK, then we don't need to fallback? >> >> Also, do we know if the updated CentOS microcode RPM

On 09/19/17 11:44, m.roth at 5-cent.us wrote: > Pete Geenhuizen wrote: >> I upgraded from 7.3 to 7.4 over the weekend.? Everything went well >> except that I can't login because the screen is black with a cursor. >> >> If reboot boot the 7.3 kernel 3.10.0-514.26.2.el7.x86_64 kernel >> everything works just fine, so my guess is that there's a kernel issue

I just installed the latest kernel 2.6.32-573.8.1.el6.x86_64 and when I rebooted it shorewall (shorewall-4.5.4-1.el6.noarch) failed with the following error ERROR: a non-empty masq file requires NAT in your kernel and iptables /etc/shorewall/masq (line 15) Question is is this a problem in the kernel or is it a problem in Shorewall? Booting the previous kernel allowed shorewall to start

I upgraded to C 7.4 from C 6.9 on my laptop and all was well.? As with C6 and the other C7 hosts that I have, if launch a terminal from the desktop it opens in [ user at host Desktop ]$ which is just fine. I restored parts of my C 6.9 home into C7.4 and now everything shows up on my desktop and when I open a terminal it now opens up in? [ user at host ~ ]$ Obviously I overwrote the setting,

I'm upgrading from CentOS6 to CentOS 7. I run 2 weather stations on C6 and have one of them attached to ttyS0 which is on the motherboard, and the other to ttyS2 which in on an add-on PCI serial card. I'm migrating the weather stations another host running C7 which has a similar hardware configuration.? When I connect the weather station to ttyS0 everything works fine, but when I try

On 08/02/15 12:33, Pete Geenhuizen wrote: > > On 02/08/15 06:12, Ned Slider wrote: >> >> On 08/02/15 05:09, S.Tindall wrote: >> Yes, just to reiterate: >> >> yum erase kmod-nvidia >> yum install kmod-nvidia-340xx >> reboot >> >> You will then be on the correct driver branch and will get the >> appropriate driver updates going

On 01/28/18 20:15, Fred Smith wrote: > On Sun, Jan 28, 2018 at 12:10:29PM -0500, Pete Geenhuizen wrote: >> I'm upgrading from CentOS6 to CentOS 7. >> >> I run 2 weather stations on C6 and have one of them attached to >> ttyS0 which is on the motherboard, and the other to ttyS2 which in >> on an add-on PCI serial card. >> >> I'm migrating the

I am trying to get a logwatch summary emailed to a central address from a cron job. The tasd was copied verbatim from a system which does this already. Both are shown below. host1 crontab -l as root 45 7 * * * /usr/sbin/logwatch --service http --service imapd --service pop3 --service sshd --service vsftpd --service zz-disk_space --service zz-network --service zz-sys --mailto support at

On 06/03/2019 19:30, Pete Geenhuizen wrote: > > > On 03/06/2019 09:59 AM, Fred Smith wrote: >> >>> I tried to install this and ran into a conflict >>> >>> --> Processing Conflict: >>> nvidia-x11-drv-340xx-340.107-2.el7_6.elrepo.x86_64 conflicts ocl-icd >>> --> Finished Dependency Resolution >>> Error: nvidia-x11-drv-340xx

On 08/02/15 14:24, Pete Geenhuizen wrote: > > On 02/08/15 07:45, Ned Slider wrote: >> >> On 08/02/15 12:33, Pete Geenhuizen wrote: >> No, you don't have the package kmod-nvidia-340xx installed. You have >> kmod-nvidia VERSION 340.65. In the first example, the package NAME is >> kmod-nvidia-340xx (the -340xx is part of the package name, NOT the >>

On 09/07/2016 14:15, Walter H. wrote: > On 09.07.2016 14:39, Pete Geenhuizen wrote: >> I don't see it either. >> >> On 07/09/16 08:36, Walter H. wrote: >>> On 07.07.2016 22:19, Helmut Drodofsky wrote: >>>> Helo, >>>> >>>> update is in EPEL repository. >>>> >>> strange, here it isn't ... > the reason:

On 11/03/2019 12:41, Pete Geenhuizen wrote: > Hi Pete, > On 03/07/2019 01:56 AM, Phil Perry wrote: >> On 06/03/2019 23:03, Stephen John Smoogen wrote: >> >> Thank you Stephen. I assumed because they were pulling a dependency >> from epel that they were also from epel. >> > > Been out of town, yes I goofed vlc, smplayer, mplayer, and ffmpeg aren't

After some experimenting I have observed that overriding settings from /usr/share/logwatch/default.conf/logwatch.conf in /etc/logwatch/conf/logwatch.conf does not produce consistent results. For example, if I replace the default detail configuration in etc/logwatch/conf/logwatch.conf with: Detail = High It does indeed change the level of detail from the default Low set in

It was the mid/late-90s, but I seem to recall Bourne being the default shell, although sh/ksh/csh were all available with a typical install. On Fri, Apr 24, 2015 at 8:32 AM, Scott Robbins <scottro at nyc.rr.com> wrote: > On Fri, Apr 24, 2015 at 08:02:56AM -0400, mark wrote: > > On 04/24/15 06:57, Pete Geenhuizen wrote: > > > > > >On 04/24/15 06:07, E.B. wrote:

On 06/03/2019 23:03, Stephen John Smoogen wrote: > On Wed, 6 Mar 2019 at 17:50, Phil Perry <pperry at elrepo.org> wrote: >> >> On 06/03/2019 21:53, Pete Geenhuizen wrote: >>> >>> >>> On 03/06/2019 04:21 PM, Phil Perry wrote: >>>> On 06/03/2019 19:30, Pete Geenhuizen wrote: >>>>> >>>>> That is all good and

On 09/19/17 11:01, Pete Geenhuizen wrote: > I upgraded from 7.3 to 7.4 over the weekend.? Everything went well? > except that I can't login because the screen is black with a cursor. > > If reboot boot the 7.3 kernel 3.10.0-514.26.2.el7.x86_64 kernel? > everything works just fine, so my guess is that there's a kernel > issue? > with the hardware, specifically the

On Wed, Mar 06, 2019 at 07:26:42AM -0500, Pete Geenhuizen wrote: > > On 03/02/2019 05:41 AM, Phil Perry wrote: > > > >Hi Gerry, > > > >I've updated the nvidia 340xx legacy package set for el7.6, and > >released the packages to the elrepo testing repository. > > > >Please could you test them and let me know if they work as > >expected. To