search for: thegeekdiari

Displaying 9 results from an estimated 9 matches for "thegeekdiari".

Did you mean: thegeekdiary
2017 Feb 05
2
Chrony vd NTP
I have read: http://thegeekdiary.com/centos-rhel-7-chrony-vs-ntp-differences-between-ntpd-and-chronyd/ My server is up all the time and will serve time to internal systems (via DHCP options). Caveat is that my server is an armv7 (Cubieboard2) which does not have an RTC (no battery). So whenever the system boots, the time is ZERO (Dec 31, 1969 or some such). Chrony fixes this really fast;
2017 Feb 05
2
Chrony vd NTP
On 05/02/17 16:15, Richard wrote: > >> Date: Sunday, February 05, 2017 10:26:05 -0500 >> From: Robert Moskowitz <rgm at htt-consult.com> >> >> I have read: >> http://thegeekdiary.com/centos-rhel-7-chrony-vs-ntp-differences-bet >> ween-ntpd-and-chronyd/ >> >> My server is up all the time and will serve time to internal >> systems (via
2016 Dec 30
1
chronyd configuration as a local ntp server
Robert, If your NTP server will be on 7/24, I would uninstall chrony and install ntpd which is still included in CentOS 7. Configure as usual. For the differences between chrony and ntpd reference: http://thegeekdiary.com/centos-rhel-7-chrony-vs-ntp-differences-between-ntpd-and-chronyd/ Essentially, chrony is more for laptops with intermittant network connections, and ntpd is better suited to
2017 Feb 05
1
Chrony vd NTP
> Date: Sunday, February 05, 2017 10:26:05 -0500 > From: Robert Moskowitz <rgm at htt-consult.com> > > I have read: > http://thegeekdiary.com/centos-rhel-7-chrony-vs-ntp-differences-bet > ween-ntpd-and-chronyd/ > > My server is up all the time and will serve time to internal > systems (via DHCP options). > > Caveat is that my server is an armv7
2019 Aug 07
2
another bizarre thing...
On Tue, Aug 06, 2019 at 03:18:06PM -0600, Warren Young wrote: > On Aug 6, 2019, at 7:59 AM, Fred Smith <fredex at fcshome.stoneham.ma.us> wrote: > > > > On Tue, Aug 06, 2019 at 05:27:54AM -0600, Warren Young wrote: > >> On Aug 5, 2019, at 6:57 PM, Fred Smith <fredex at fcshome.stoneham.ma.us> wrote: > >>> > >>> no core file (yes, ulimit
2020 Jan 15
2
[semi-OT] C7 Possible bug but I can't determine what tool has the problem
Il 15/01/20 17:51, Jon Pruente ha scritto: > On Wed, Jan 15, 2020 at 10:18 AM Alessandro Baggi < > alessandro.baggi at gmail.com> wrote: > >> I made several test to see what happens and noticed that removing -S >> (--sparse) from rsync command problem does not occour. >> In another test, thinking about a problem on 0ed file, I tried file >> generation using
2017 Feb 05
0
Chrony vd NTP
On 02/05/2017 11:58 AM, J Martin Rushton wrote: > On 05/02/17 16:15, Richard wrote: >>> Date: Sunday, February 05, 2017 10:26:05 -0500 >>> From: Robert Moskowitz <rgm at htt-consult.com> >>> >>> I have read: >>> http://thegeekdiary.com/centos-rhel-7-chrony-vs-ntp-differences-bet >>> ween-ntpd-and-chronyd/ >>> >>> My
2019 Aug 07
0
another bizarre thing...
On Aug 6, 2019, at 8:48 PM, Fred Smith <fredex at fcshome.stoneham.ma.us> wrote: > > Setting up as you described earlier, is there a way to allow only > a single program to drop core? Of course. The * in the limits.d file is a ?domain? value you can adjust to suit: https://www.thegeekdiary.com/understanding-etc-security-limits-conf-file-to-set-ulimit/ You?d have to read the
2020 Jan 15
0
[semi-OT] C7 Possible bug but I can't determine what tool has the problem
On Wed, Jan 15, 2020 at 11:38 AM Alessandro Baggi < alessandro.baggi at gmail.com> wrote: > Hi Jon, > I wrote in the first mail the script with the current order of command > that I used. Try to run in a bash script and you will see the result. > > If not my sequence is: > > dd if=/dev/zero of=src/testfile bs=1M count=100 > rsync -avS src/ dest/ > du -h