On 2019-07-27 09:20, Ian Zimmerman wrote:
> On 2019-07-27 07:42, Aidan Harris wrote:
>
>> I run openrc with rc_parallel enabled and I end up booting so fast
>> that by the time ntp-client starts DNS resolution is not properly
>> available yet (I use a local DNS resolver so even though networking
On 2019-07-27 07:42, Aidan Harris wrote:
> I run openrc with rc_parallel enabled and I end up booting so fast
> that by the time ntp-client starts DNS resolution is not properly
> available yet (I use a local DNS resolver so even though networking is
> up my local resolver takes a while - a small
On 2019-07-27 01:27, Grant Edwards wrote:
> > By the way does "rc_parallel" really makes a difference?
>
>
> Yes. It guarantees that when you do have boot problems, you'll never
> be able to figure out the real problem.
>
>
> Having more parallel boot operations used to be one of the
>
On 2019-07-26, YUE Daian wrote:
> By the way does "rc_parallel" really makes a difference?
Yes. It guarantees that when you do have boot problems, you'll never
be able to figure out the real problem.
Having more parallel boot operations used to be one of the
"advantages" touted by some
On 06/18/2017 08:34 PM, Tom H wrote:
> On Sat, Jun 17, 2017 at 1:46 PM, Walter Dnes wrote:
>> On Fri, Jun 16, 2017 at 09:44:27PM +1000, Michael Palimaka wrote
>>>
>>> Someone raised the issue that the "time server" option in the date
>>> and time applet was greyed out on
On Sat, Jun 17, 2017 at 1:46 PM, Walter Dnes wrote:
> On Fri, Jun 16, 2017 at 09:44:27PM +1000, Michael Palimaka wrote
>>
>> Someone raised the issue that the "time server" option in the date
>> and time applet was greyed out on their system. It turns out that
>> this
On Fri, Jun 16, 2017 at 09:44:27PM +1000, Michael Palimaka wrote
> Someone raised the issue that the "time server" option in the date
> and time applet was greyed out on their system. It turns out that
> this occurs if neither ntpdate nor rdate binaries are present, so I
> added the dep. There's
On Friday 16 Jun 2017 21:44:27 Michael Palimaka wrote:
> Someone raised the issue that the "time server" option in the date and
> time applet was greyed out on their system. It turns out that this
> occurs if neither ntpdate nor rdate binaries are present, so I added the
> dep. There's been some
On Fri, Jun 16, 2017 at 10:34 AM, R0b0t1 wrote:
>
> Is it not possible to add it via a USE flag? Even if there are no real
> compile time options, could the flag pull in ntp?
Could a USE flag do this? Sure. Should it? No.
"The usage of a USE flag should not control runtime
On Fri, Jun 16, 2017 at 6:44 AM, Michael Palimaka wrote:
> Hi,
>
> On 06/16/2017 04:19 PM, Andrew Lowe wrote:
>> Good afternoon all,
>> Does anyone have any inside knowledge as to why 5.9.5 of KDE plasma
>> desktop did not require ntp whereas 5.10.5 does? I use
On 2017-06-16, Michael Palimaka wrote:
>
> Someone raised the issue that the "time server" option in the date and
> time applet was greyed out on their system. It turns out that this
> occurs if neither ntpdate nor rdate binaries are present,
That seems like perfectly
Hi,
On 06/16/2017 04:19 PM, Andrew Lowe wrote:
> Good afternoon all,
> Does anyone have any inside knowledge as to why 5.9.5 of KDE plasma
> desktop did not require ntp whereas 5.10.5 does? I use Openntp and been
> using KDE 5 for ages with the time being correct so was wondering why
> now
John Blinka [EMAIL PROTECTED] writes:
I have a very old Dell P150ST laptop that I try to maintain Gentoo on.
Every time I boot it,
it complains ERROR: cannot start ntp-client as net.eth0 could not be
started.
One way that will probably work is to start ntp-client from
[EMAIL PROTECTED] wrote:
One way that will probably work is to start ntp-client from
/etc/conf.d/local-start
local-start is the very last thing called during a bootup so if timing
is the problem this would be a way to skirt around it.
Just put whatever commands start ntp-client in
On Monday 06 November 2006 19:52, [EMAIL PROTECTED] wrote:
John Blinka [EMAIL PROTECTED] writes:
I have a very old Dell P150ST laptop that I try to maintain Gentoo on.
Every time I boot it,
it complains ERROR: cannot start ntp-client as net.eth0 could not be
started.
One way that will
Devon Miller devon.c.miller at gmail.com writes:
Make sure you have told you firewall to allow port 123 for both TCP
UDP.I had the same behavior until I did that.dcm
Well my firewall should allow outgoing initiated sessions from the
ntpd (internal) server. From what I read, the remote ntpd
On Feb 1, 2006, at 1:25 PM, James wrote:
Devon Miller devon.c.miller at gmail.com writes:
Make sure you have told you firewall to allow port 123 for both TCP
UDP.I had the same behavior until I did that.dcm
Well my firewall should allow outgoing initiated sessions from the
ntpd (internal)
John Jolet john at jolet.net writes:
But now when I run 'ntpq -p' I get:
ntpq: read: Connection refused
is ntpd dying? ps -elf|grep ntp should show you something besides
the grep.
Yep. Attempt stop it and start it again: /etc/init.d/ntpd start
fails.
Ideas?
James
--
James wireless at tampabay.rr.com writes:
John Jolet john at jolet.net writes:
But now when I run 'ntpq -p' I get:
ntpq: read: Connection refused
is ntpd dying? ps -elf|grep ntp should show you something besides
the grep.
Yep. Attempt stop it and start it again:
James wrote:
is ntpd dying? ps -elf|grep ntp should show you something besides
the grep.
Yep. Attempt stop it and start it again: /etc/init.d/ntpd start
fails.
/etc/init.d/ntpd zap to clear out the invalid status, then do the
'start' again.
--
gentoo-user@gentoo.org mailing
On 2/1/06, James [EMAIL PROTECTED] wrote:
It corrected the minutes but it's off by exactly one hour. It needs to be
EST (eastern standard time) NY (Tampa Florida).
so what file do I edit to correct utc to est ?
Try timezone US/Eastern instead of EST.
ln -sf /usr/share/zoneinfo/US/Eastern
On Feb 1, 2006, at 2:18 PM, James wrote:
James wireless at tampabay.rr.com writes:
John Jolet john at jolet.net writes:
But now when I run 'ntpq -p' I get:
ntpq: read: Connection refused
is ntpd dying? ps -elf|grep ntp should show you something besides
the grep.
Yep. Attempt stop it
Default behaviour is that if the time zone is off by more than a preset
amount (I think 128ms) it will refuse to sync, and silently fails.
Read the docs for the config file command tinker panic 0 (and its
implications) which will remove the limitation and allow stepping to the
new time.
Also
On 04/20/05 07:27, Nuno Alexandre wrote:
On Wed, 2005-04-20 at 03:21 -0400, Peng wrote:
I'm sorry to ask something so basic, but is there an Idiot's Guide to
Time Syncronization on Gentoo Linux anywhere? I just can't figure the
dumb thing out. :-(
--
Hi,
try this one:
24 matches
Mail list logo