search for: wyoham

One can also do the 'yum-cron' dance to automate updates. Good writeup and description here: https://www.howtoforge.com/tutorial/how-to-setup-automatic-security-updates-on-centos-7/ On Fri, Feb 15, 2019 at 11:37 PM Rob Kampen <rkampen at kampensonline.com> wrote: > On 16/02/19 6:59 PM, Ralf Prengel wrote: > > Hallo, > > as a beginner using centos I?ve a question

On Feb 16, 2019, at 15:14, Tate Belden <wyoham at gmail.com> wrote: > > One can also do the 'yum-cron' dance to automate updates. > Good writeup and description here: > > https://www.howtoforge.com/tutorial/how-to-setup-automatic-security-updates-on-centos-7/ 1.) yum-cron with ?update_cmd = security? wont do anythin...

> Am 17.02.2019 um 14:28 schrieb Jonathan Billings <billings at negate.org>: > >> On Feb 16, 2019, at 15:14, Tate Belden <wyoham at gmail.com> wrote: >> >> One can also do the 'yum-cron' dance to automate updates. >> Good writeup and description here: >> >> https://www.howtoforge.com/tutorial/how-to-setup-automatic-security-updates-on-centos-7/ > > 1.) yum-cron with ?update_c...

Warren, one slight correction on an other wise nicely written bit of info: The time transmitted from WWV is not Mountain Time. Even though the WWV transmitter farm is located in the Mountain time zone, the signals are transmitted as "Coordinated Universal time", UTC, or 'Zulu' time. Here, you can listen to a recording made at the transmitter site for the 5Mhz signal:

Might I suggest using "systemctl restart sshd", instead of reload? At the least - see if it behaves differently for you. - *restart* = stop + start - *reload* = remain running + re-read configuration files. On Thu, Mar 2, 2017 at 9:29 AM, <me at tdiehl.org> wrote: > Hi, > > Since upgrading to 7.3 I am having a problem getting sshd to reload after >

I have to assume it's something unique to your install, then. I run about a dozen sshd instances on as many CentOS 7 boxes around here. To a one, systemctl restart sshd is all it takes to implement config changes. Only time it's given me fits is if I forget to actually write the config file in VIM. That pesky w gets me on rare occasion. On Thu, Mar 2, 2017 at 11:50 AM, <me at

Use the 'downgrade' option. https://access.redhat.com/solutions/29617 On Thu, Jun 1, 2017 at 1:46 PM, Anand Buddhdev <anandb at ripe.net> wrote: > We're using ansible to configure our CentOS 6 servers, and we have a > task to install a specific version of a package: > > - name: install thrift2 > yum: name=ripencc-thrift2-{{ version }} > > In this ansible

I can log in and view the forums just fine. But yea, using your search link, I get that same 'server busy' Informational. Man, looks like it's been awhile since I've visited there..... On Mon, Feb 11, 2019 at 11:20 AM J Martin Rushton via CentOS < centos at centos.org> wrote: > All day I've been getting "Sorry but you cannot use search at this time. > The

And the answer is same as the last X times this has been asked. When it's ready. However, they do have a page up so you can track said 'readiness'. It may lends some info. https://wiki.centos.org/About/Building_8 On Fri, Jun 7, 2019 at 3:57 PM Eugene Poole <etpoole60 at comcast.net> wrote: > The subject says it all. > > -- > Eugene Poole > Woodstock, Georgia

https://www.freedesktop.org/software/systemd/man/systemd-sleep.conf.html On Mon, Jun 17, 2019 at 9:44 AM mark <m.roth at 5-cent.us> wrote: > I found that one of my users' workstation is, for some reason, running > systemd-sleep. I cannot find, anywhere on the system. system-sleep.conf > (or systemd-sleep.conf), nor do I find systemctl status system[d]-sleep. > > How can

FWIW, on Fedora 29, I'm running Geany 1.34.1 and didn't have to enable anything other than the default repositories. So, it'd appear to at least be in the stream. geany-1.34.1-2.fc29.x86_64 On Thu, Feb 14, 2019 at 8:53 AM H <agents at meddatainc.com> wrote: > On 01/04/2019 04:17 AM, H wrote: > > Does anyone know if Geany 1.34 is headed to one of the repositories? I

I've several USB <-> RS-232 dongles around. As well as a few embedded devices. They all "Just Work (tm)" on Redhat, CentOS, Fedora, Debian, Raspian and Kali. Knock on wood - never had a problem using any of them. As the drivers are part of the kernel, I'd expect any distro using a recent kernel to do well. On Wed, Jul 8, 2020 at 9:24 AM Leroy Tennison <leroy at