is open, but
this is not enough (intact may be unnecessary). Chrony uses a unprivileged port
( > 1024) to connect to port 123 on the ntp pool server. What needs to happen
is the firewall needs to track this connection and allow a udp packet back form
the source port 123 to your server, to th
Hello,
Following the previous email exchange, what is the next step?
Is the issue clearly identified?
Do I need to run more tests?
Thank.
===
Patrick DUPRÉ | | email: pdu...@gmx.com
Laborato
time:
23:01:55.706587 IP HP_Box.home.ntp > vpn.webersheim.de.ntp: NTPv3, Client,
length 48
23:01:55.741872 IP vpn.webersheim.de.ntp > HP_Box.home.ntp: NTPv3, Server,
length 48
23:09:18.187249 IP HP_Box.home.ntp > 213.145.129.29.ntp: NTPv3, Client, length
48
23:09:18.323093 IP 213.145.1
transit
>>> time:
>>>
>>> 23:01:55.706587 IP HP_Box.home.ntp > vpn.webersheim.de.ntp: NTPv3, Client,
>>> length 48
>>> 23:01:55.741872 IP vpn.webersheim.de.ntp > HP_Box.home.ntp: NTPv3, Server,
>>> length 48
>>> 23:09:1
On 09/09/2015 03:43 PM, Ed Greshko wrote:
Nice to know Yet you really should consider trimming. Otherwise you'll
start to prove top-posters right. :-) :-)
Indeed. One of my pet peeves is people who respond to something in the
middle of a message and then quote the remainder, including
:01:55.741872 IP vpn.webersheim.de.ntp > HP_Box.home.ntp: NTPv3, Server,
length 48
23:09:18.187249 IP HP_Box.home.ntp > 213.145.129.29.ntp: NTPv3, Client, length
48
23:09:18.323093 IP 213.145.129.29.ntp > HP_Box.home.ntp: NTPv3, Server, length
48
23:12:00.892883 IP HP_Box.home
> 23:01:55.741872 IP vpn.webersheim.de.ntp > HP_Box.home.ntp: NTPv3, Server,
> length 48
> 23:09:18.187249 IP HP_Box.home.ntp > 213.145.129.29.ntp: NTPv3, Client,
> length 48
> 23:09:18.323093 IP 213.145.129.29.ntp > HP_Box.home.ntp: NTPv3, Server,
> length 48
> 23:12:00.892883 I
enabled
chronyd.service - NTP client/server
Loaded: loaded (/usr/lib/systemd/system/chronyd.service; enabled)
Active: active (running) since Wed 2015-09-09 19:31:53 CEST; 4min
23s ago
Process: 6933 ExecStartPost=/usr/libexec/chrony-helper
add-dhclient-servers (code=exited, status=0/SUCCESS)
P
files | grep chrony
>>> chrony-wait.service disabled
>>> chronyd.service enabled
>>>
>>>
>>> chronyd.service - NTP client/server
>>>Loaded: loaded (/usr/lib/systemd/system/chronyd.service; enabled)
>
.841 +/- 0.025 ppm read
> from /
> Sep 08 12:08:01 Homere systemd[1]: Stopping NTP client/server...
> Sep 08 12:08:01 Homere systemd[1]: Starting NTP client/server...
> Sep 08 12:08:01 Homere systemd[1]: Started NTP client/server.
> Sep 08 12:08:01 Homere chronyd[5528]: chronyd versi
On 9 September 2015 at 21:40, Patrick Dupre wrote:
> > On 09/09/2015 10:37 AM, Patrick Dupre wrote:
> I do not see any ntpd running, ntp is not installed!
>
>
"NTP client/server" _is_ chronyd; this is just systemd's weird habit of
showing a service "descriptio
rt chronyd
> >
> > systemctl list-unit-files | grep chrony
> > chrony-wait.service disabled
> > chronyd.service enabled
> >
> >
> > chronyd.service - NTP client/server
> > Loaded: loaded (/usr/li
]: Stopping NTP client/server...
Sep 08 12:08:01 Homere systemd[1]: Starting NTP client/server...
Sep 08 12:08:01 Homere systemd[1]: Started NTP client/server.
Sep 08 12:08:01 Homere chronyd[5528]: chronyd version 1.31.1 starting
Sep 08 12:08:01 Homere chronyd[5528]: Frequency -15.841 +/- 0.025 ppm read from
On 09/10/15 01:00, Rick Stevens wrote:
>
> journalctl -u chrony -b
You want
journalctl -u chronyd -b
--
It seems most people that say they are "done talking about it" never really are
until given the last word.
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or c
53 CEST. --
>>
>>
>> after systemctl restart chronyd
>>
>> systemctl list-unit-files | grep chrony
>> chrony-wait.service disabled
>> chronyd.service enabled
>>
>>
>> chronyd.service - NTP
disabled
chronyd.service enabled
chronyd.service - NTP client/server
Loaded: loaded (/usr/lib/systemd/system/chronyd.service; enabled)
Active: active (running) since Wed 2015-09-09 19:31:53 CEST; 4min 23s ago
Process: 6933 ExecStartPost=/usr
enabled
chronyd.service - NTP client/server
Loaded: loaded (/usr/lib/systemd/system/chronyd.service; enabled)
Active: active (running) since Wed 2015-09-09 19:31:53 CEST; 4min 23s ago
Process: 6933 ExecStartPost=/usr/libexec/chrony-helper add-dhclient-servers
(code
ctstate NEW
ACCEPT udp -- anywhere anywhere udp dpt:ipp
ctstate NEW
ACCEPT udp -- anywhere anywhere udp dpt:ipp
ctstate NEW
ntp is on the port 123
In zone internal I checked ntp
It is all I need?
I don't think that's nece
.0.251 udp dpt:mdns
> > ctstate NEW
> > ACCEPT udp -- anywhere anywhere udp dpt:ipp
> > ctstate NEW
> > ACCEPT udp -- anywhere anywhere udp dpt:ipp
> > ctstate NEW
> >
> > ntp is on the port
anywhere udp dpt:ipp
ctstate NEW
ACCEPT udp -- anywhere anywhere udp dpt:ipp
ctstate NEW
ntp is on the port 123
In zone internal I checked ntp
It is all I need?
I don't think that's necessary. The firewall rules affect incoming
connect
NEW
ACCEPT udp -- anywhere anywhere udp dpt:ipp
ctstate NEW
ntp is on the port 123
In zone internal I checked ntp
It is all I need?
Thank.
> >
> >
> > ===
&
ot;Rick Stevens"
To: "Community support for Fedora users"
Subject: Re: NTP synchronized: no
On 09/08/2015 10:52 AM, Patrick Dupre wrote:
Hello,
I am not sure to understand.
The previous conclusion was that the firewall did not
Community support for Fedora users"
> Subject: Re: NTP synchronized: no
>
> On 09/08/2015 10:52 AM, Patrick Dupre wrote:
> > Hello,
> >
> > I am not sure to understand.
> > The previous conclusion was that the firewall did not let me go through.
> > Now,
time: Tue 2015-09-08 17:46:24 UTC
RTC time: Tue 2015-09-08 17:46:24
Timezone: Europe/Paris (CEST, +0200)
NTP enabled: yes
NTP synchronized: yes
RTC in local TZ: no
DST active: yes
Last DST change: DST began at
Sun 2015-03-29 01:59:59 CET
:
timedatectl set-ntp yes
Here, the results of some commands:
netstat -a |grep ntp
udp0 0 localhost.localdo:51314 ns346276.ip-94-23-3:ntp
ESTABLISHED
udp0 0 localhost.localdo:39994 tomia.ordimatic.net:ntp
ESTABLISHED
udp0 0 localhost.localdo:45035
-09-08 19:46:24 CEST
Universal time: Tue 2015-09-08 17:46:24 UTC
RTC time: Tue 2015-09-08 17:46:24
Timezone: Europe/Paris (CEST, +0200)
NTP enabled: yes
NTP synchronized: yes
RTC in local TZ: no
DST active: yes
Last DST change: DST began at
Sun 2015-03
On 08/09/15 18:02, Rick Stevens wrote:
On 09/08/2015 03:27 AM, John Pilkington wrote:
On 08/09/15 10:52, Ed Greshko wrote:
On 09/08/15 17:29, Patrick Dupre wrote:
I cannot synchronize the date:
My undestanding is that it should be set by:
timedatectl set-ntp yes
Here, the results of some
On 09/08/2015 03:27 AM, John Pilkington wrote:
On 08/09/15 10:52, Ed Greshko wrote:
On 09/08/15 17:29, Patrick Dupre wrote:
I cannot synchronize the date:
My undestanding is that it should be set by:
timedatectl set-ntp yes
Here, the results of some commands:
netstat -a |grep ntp
udp
On 09/08/15 19:11, Patrick Dupre wrote:
> Should I ask to have the port ntp open ?
> Is it 123?
Yes, UDP port 123
--
It seems most people that say they are "done talking about it" never really are
until given the last word.
--
users mailing list
users@lists.fedoraproject.org
T
Thank.
Should I ask to have the port ntp open ?
Is it 123?
===
Patrick DUPRÉ | | email: pdu...@gmx.com
Laboratoire de Physico-Chimie de l'Atmosphère | |
Université du Littoral-Côte d&
4 * * *
> 5 * * *
> 6 * * *
> 7 * * *
> 27 * * *
> 28 * * *
> 29 * * *
> 30 * * *
Yep A firewall
You should talk to your network administrator. They probably have a local ntp
server you should be using.
--
It seems most people that say they are "done
traceroute to 123.204.45.116 (123.204.45.116), 30 hops max, 60 byte packets
1 cisco-dk.univ-littoral.fr (193.49.194.1) 2.168 ms 2.332 ms 2.598 ms
2 192.168.168.203 (192.168.168.203) 0.441 ms 0.458 ms 0.506 ms
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
27 * * *
28 * * *
29 * * *
On 09/08/15 18:26, Patrick Dupre wrote:
> This is at the Unversity. Maybe it is a firewall issue.
> Is there a test that I can do to double check?
What do you get with this.
traceroute -p 123 -U 123.204.45.116
--
It seems most people that say they are "done talking about it" never really ar
On 08/09/15 10:52, Ed Greshko wrote:
On 09/08/15 17:29, Patrick Dupre wrote:
I cannot synchronize the date:
My undestanding is that it should be set by:
timedatectl set-ntp yes
Here, the results of some commands:
netstat -a |grep ntp
udp0 0 localhost.localdo:51314 ns346276.ip-94
>
> On 09/08/15 17:29, Patrick Dupre wrote:
> > I cannot synchronize the date:
> > My undestanding is that it should be set by:
> > timedatectl set-ntp yes
> >
> > Here, the results of some commands:
> >
> > netstat -a |grep ntp
> > udp
On 09/08/15 17:29, Patrick Dupre wrote:
> I cannot synchronize the date:
> My undestanding is that it should be set by:
> timedatectl set-ntp yes
>
> Here, the results of some commands:
>
> netstat -a |grep ntp
> udp0 0 localhost.localdo:51314 ns346276.ip-94
I cannot synchronize the date:
My undestanding is that it should be set by:
timedatectl set-ntp yes
Here, the results of some commands:
netstat -a |grep ntp
udp0 0 localhost.localdo:51314 ns346276.ip-94-23-3:ntp ESTABLISHED
udp0 0 localhost.localdo:39994
On 09/08/15 01:48, Patrick Dupre wrote:
> Now, I have:
>
> Local time: Mon 2015-09-07 17:46:49 CEST
> Universal time: Mon 2015-09-07 15:46:49 UTC
> RTC time: Mon 2015-09-07 17:46:49
>Time zone: Europe/Paris (CEST, +0200)
> NTP enabled: yes
> NTP
On 07/09/15 22:32, Patrick Dupre wrote:
On 07/09/15 18:48, Patrick Dupre wrote:
Now, I have:
Local time: Mon 2015-09-07 17:46:49 CEST
Universal time: Mon 2015-09-07 15:46:49 UTC
RTC time: Mon 2015-09-07 17:46:49
Time zone: Europe/Paris (CEST, +0200)
NTP
>
> On 07/09/15 18:48, Patrick Dupre wrote:
> > Now, I have:
> >
> > Local time: Mon 2015-09-07 17:46:49 CEST
> >Universal time: Mon 2015-09-07 15:46:49 UTC
> > RTC time: Mon 2015-09-07 17:46:49
> > Time zone: Europe/Pari
On 07/09/15 18:48, Patrick Dupre wrote:
Now, I have:
Local time: Mon 2015-09-07 17:46:49 CEST
Universal time: Mon 2015-09-07 15:46:49 UTC
RTC time: Mon 2015-09-07 17:46:49
Time zone: Europe/Paris (CEST, +0200)
NTP enabled: yes
NTP synchronized: yes
RTC in local
Now, I have:
Local time: Mon 2015-09-07 17:46:49 CEST
Universal time: Mon 2015-09-07 15:46:49 UTC
RTC time: Mon 2015-09-07 17:46:49
Time zone: Europe/Paris (CEST, +0200)
NTP enabled: yes
NTP synchronized: yes
RTC in local TZ: yes
DST active: yes
Last DST change
Hello,
In fedora 22, how do I synchronize the ntp:
timedatectl
Local time: Mon 2015-09-07 17:04:58 CEST
Universal time: Mon 2015-09-07 15:04:58 UTC
RTC time: Mon 2015-09-07 17:04:58
Time zone: Europe/Paris (CEST, +0200)
NTP enabled: yes
NTP synchronized: no
RTC in
On 07/26/2015 09:46 AM, Paul Cartwright wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 07/26/2015 11:04 AM, Bill Shirley wrote:
Put this at the bottom of /etc/chrony.conf:
# comment out allow and noclientlog above
# my stuff
allow 10.0.0.0/8
allow 192.168.0.0/16
allow 172.16.0.0/12
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 07/26/2015 11:04 AM, Bill Shirley wrote:
> Put this at the bottom of /etc/chrony.conf:
> # comment out allow and noclientlog above
> # my stuff
> allow 10.0.0.0/8
> allow 192.168.0.0/16
> allow 172.16.0.0/12
> broadcast 60 192.168.4.255
> broadca
You don't need ntpd.
HTH,
Bill
On 7/26/2015 10:48 AM, François Patte wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bonjour,
I want to have ntp service running on my machine, so I enabled this
service:
systemctl enable ntpd.service
systemctl start ntpd.service
But, every time I r
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/26/15 22:48, François Patte wrote:
> Bonjour,
>
> I want to have ntp service running on my machine, so I enabled this
> service:
>
> systemctl enable ntpd.service
>
> systemctl start ntpd.service
>
> But, every ti
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bonjour,
I want to have ntp service running on my machine, so I enabled this
service:
systemctl enable ntpd.service
systemctl start ntpd.service
But, every time I reboot my machine, ntp is dead
systemctl status ntpd.service
● ntpd.service
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/25/15 07:14, Sam Varshavchik wrote:
> Ed Greshko writes:
>
>> I see I've not worked with masquerading in a firewalld environment.
>> I've only done it with shoreview as the IP Tables manipulator
>>
>> With that in mind, since you have
Ed Greshko writes:
I see I've not worked with masquerading in a firewalld environment.
I've only done it with shoreview as the IP Tables manipulator
With that in mind, since you have 2 LAN interfaces are they assigned to
different zones? One with masquerading turned on, the other
hat countless of
> consumer-grade Internet routers do. They own the public IP address, configure
> 192.168.0.1 as the IP address of their LAN interface, and run a DHCP server
> on the LAN interface to configure the clients on 192.168.0.0/24, and
> masquerade them on the public IP addres
consumer-grade Internet routers do. They own the public IP address,
configure 192.168.0.1 as the IP address of their LAN interface, and run a
DHCP server on the LAN interface to configure the clients on 192.168.0.0/24,
and masquerade them on the public IP address.
And where are the ntp client
ace system with the Fedora firewalld system
acting as a "router" with masquerading for a set of clients "behind" it?
And where are the ntp clients in relation to the server?
- --
If you can't laugh at yourself, others will gladly oblige.
-BEGIN PGP SIGNATURE
As far as I can determine, the way that firewalld sets up masquerading
completely breaks both ntpd and chrony.
Both servers appears to start, but their corresponding client-side tools,
ntpdc or chronyc, cannot talk to them. strace shows that UDP packets to
127.0.0.1 have their source IP add
On 01/06/15 09:54, Bob Goodwin wrote:
[root@box48 bobg]# chronyc sources
210 Number of sources = 2
MS Name/IP address Stratum Poll Reach LastRx Last sample
===
^? box10 3 6 346
On 01/06/15 09:37, poma wrote:
http://chrony.tuxfamily.org/FAQ.html#question_8.3
Besides we gave you a direct and simple instructions, proven to work.
Repeat the same title again n again for the umpteenth time, man ...
Reminds me of a scene with Don Ameche and Selleck in Folks!
Haha
"Perhaps y
On 01/06/15 09:07, Ed Greshko wrote:
I would check to make sure that the network interface being used is in the correct
"Firewall Zone".
It may be the case that you've checked NTP in the public zone in the GUI, but
for some reason the interface is not in that zone.
Yes that on
On 06.01.2015 14:58, Bob Goodwin wrote:
> I have two Fedora-21 computers set as time servers for chrony, this one
> [box10] Which began as a new install and box7 which evolved from the
> alpha version. In both the firewalld GUI Service > Workstation > NTP
> show "chec
On 01/06/15 21:58, Bob Goodwin wrote:
> I have two Fedora-21 computers set as time servers for chrony, this one
> [box10] Which began as a new install and box7 which evolved from the alpha
> version. In both the firewalld GUI Service > Workstation > NTP show
> "chec
I have two Fedora-21 computers set as time servers for chrony, this one
[box10] Which began as a new install and box7 which evolved from the
alpha version. In both the firewalld GUI Service > Workstation > NTP
show "checked." However I have to disable the firewall in box7 to al
On Tue, 2014-12-23 at 03:54 +0100, Ralf Corsepius wrote:
> On 12/22/2014 01:50 PM, Patrick O'Callaghan wrote:
> > On Mon, 2014-12-22 at 04:48 +0800, Ed Greshko wrote:
> >> On 12/22/14 02:46, Aaron Gray wrote:
> >>> There are no ntp or ntpd or systemd-timesy
On 12/22/2014 01:50 PM, Patrick O'Callaghan wrote:
On Mon, 2014-12-22 at 04:48 +0800, Ed Greshko wrote:
On 12/22/14 02:46, Aaron Gray wrote:
There are no ntp or ntpd or systemd-timesyncd packages on F20 !
The default time sync package is now chrony.
ntp is available in the F20
On Mon, 2014-12-22 at 21:32 +0800, Ed Greshko wrote:
> On 12/22/14 20:50, Patrick O'Callaghan wrote:
> > On Mon, 2014-12-22 at 04:48 +0800, Ed Greshko wrote:
> >> On 12/22/14 02:46, Aaron Gray wrote:
> >>> There are no ntp or ntpd or systemd-timesyncd packages
On 12/21/14 19:43, Aaron Gray wrote:
It should be 4.2.8 now as there are new vulnerabilities !
The following updates was submitted for testing at 2014-12-19.
For F19 in updates-testing
ntp-4.2.6p5-13.fc19
For F20 in updates-testing
ntp-4.2.6p5-19.fc20
For F21 in updates testing
ntp-4.2.6p5
On Mon, 22 Dec 2014 11:19:11 -0500
sean darcy wrote:
> How do you move to chrony?
Disable ntp and enable chrony.
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: h
On 12/22/2014 08:32 AM, Ed Greshko wrote:
On 12/22/14 20:50, Patrick O'Callaghan wrote:
On Mon, 2014-12-22 at 04:48 +0800, Ed Greshko wrote:
On 12/22/14 02:46, Aaron Gray wrote:
There are no ntp or ntpd or systemd-timesyncd packages on F20 !
The default time sync package is now chrony.
On 12/22/14 20:50, Patrick O'Callaghan wrote:
> On Mon, 2014-12-22 at 04:48 +0800, Ed Greshko wrote:
>> On 12/22/14 02:46, Aaron Gray wrote:
>>> There are no ntp or ntpd or systemd-timesyncd packages on F20 !
>> The default time sync package is now chrony.
>>
&
On Mon, 2014-12-22 at 04:48 +0800, Ed Greshko wrote:
> On 12/22/14 02:46, Aaron Gray wrote:
> > There are no ntp or ntpd or systemd-timesyncd packages on F20 !
>
> The default time sync package is now chrony.
>
> ntp is available in the F20 repos.
>
AFAIK chrony still
Cheers !
On 21 December 2014 at 20:48, Ed Greshko wrote:
> On 12/22/14 02:46, Aaron Gray wrote:
>> There are no ntp or ntpd or systemd-timesyncd packages on F20 !
>
> The default time sync package is now chrony.
>
> ntp is available in the F20 repos.
>
> --
>
On 12/22/14 02:46, Aaron Gray wrote:
> There are no ntp or ntpd or systemd-timesyncd packages on F20 !
The default time sync package is now chrony.
ntp is available in the F20 repos.
--
If you can't laugh at yourself, others will gladly oblige.
--
users mailing li
There are no ntp or ntpd or systemd-timesyncd packages on F20 !
On 21 December 2014 at 18:43, Aaron Gray wrote:
> It should be 4.2.8 now as there are new vulnerabilities !
>
> On 21 December 2014 at 18:33, Ralf Corsepius wrote:
>> On 12/21/2014 07:24 PM, Aaron Gray wr
It should be 4.2.8 now as there are new vulnerabilities !
On 21 December 2014 at 18:33, Ralf Corsepius wrote:
> On 12/21/2014 07:24 PM, Aaron Gray wrote:
>>
>> Hi,
>>
>> Whats going on with Fedora and the NTP vulnerability ?
>>
>> Both of my F20 ma
On 12/21/2014 07:24 PM, Aaron Gray wrote:
Hi,
Whats going on with Fedora and the NTP vulnerability ?
Both of my F20 machines don't seem to have ntp installed.
What surprises me more, is seeing a bugfix update addressing this issue
(ntp-4.2.6p5-25) pending in testing for f20, but not fo
Hi,
Whats going on with Fedora and the NTP vulnerability ?
Both of my F20 machines don't seem to have ntp installed.
Many thanks in advance,
Aaron
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/ma
On 10 April 2014 23:32, patrick korsnick wrote:
> Hi all,
>
> Does anyone know if Gnome3 did away with the ability to set your NTP servers
> in the Date and Time control panel? I remember you used to be able to do
> this, but can't remember if it was on Gnome2xx o
Hi all,
Does anyone know if Gnome3 did away with the ability to set your NTP
servers in the Date and Time control panel? I remember you used to be able
to do this, but can't remember if it was on Gnome2xx or was a feature that
originally existed in Gnome3 on fedora.
Thanks!
--
users ma
On Tue, 11 Feb 2014 14:10:00 -0500
Matthew Miller wrote:
> One of the first things to learn is that "disable" doesn't mean "disable".
> "mask" means "disable". (Something that's merely the former can be started
> by other things.) So, you could try 'systemctl mask ntpd.service".
Or you could use
On Tue, 11 Feb 2014 12:01:20 -0700
Eric Smith wrote:
> I'm using a Dell T3500 running Fedora 20 x86_64. It's on a private
> network not connected to the Internet, and with no NTP server. When I
> shut down the machine, it pauses for more than a minute at
>
> A st
On Tue, Feb 11, 2014 at 12:01:20PM -0700, Eric Smith wrote:
> I'm using a Dell T3500 running Fedora 20 x86_64. It's on a private network
> not connected to the Internet, and with no NTP server. When I shut down the
> machine, it pauses for more than a minute at
> A stop
I'm using a Dell T3500 running Fedora 20 x86_64. It's on a private network
not connected to the Internet, and with no NTP server. When I shut down the
machine, it pauses for more than a minute at
A stop job is running for NTP client/server.
I don't think I enabled NTP when
On 01/24/2013 06:49 PM, Jan Litwiński issued this missive:
Dnia czwartek, 24 stycznia 2013 21:36:50 Sam Varshavchik pisze:
Jan Litwiński writes:
Dnia czwartek, 24 stycznia 2013 21:06:26 Sam Varshavchik pisze:
Jan Litwiński writes:
Dnia piÄ…tek, 25 stycznia 2013 09:28:24 Ed Greshko pisze:
s
On 2013/01/24 15:46, Jan Litwiński wrote:
I have proglem with ntp service, I did:
systemctl enable ntpd.service
systemctl start ntpd.service
but ntp don't start at boot, starting by hand works. As a solution I
created rc.local and add to it systemctl start ntpd.service and it works. I
Dnia piątek, 25 stycznia 2013 10:54:26 Ed Greshko pisze:
> On 01/25/2013 10:49 AM, Jan Litwiński wrote:
> > but when I run ls in var tmp is green, I think it is a symlink
>
> In /var this is an example of a regular directory
>
> drwxrwxrwt. 61 root root 4096 Jan 25 10:51 tmp
>
> this is an examp
On 01/25/2013 10:49 AM, Jan Litwiński wrote:
> but when I run ls in var tmp is green, I think it is a symlink
In /var this is an example of a regular directory
drwxrwxrwt. 61 root root 4096 Jan 25 10:51 tmp
this is an example of a symlink
lrwxrwxrwx. 1 root root6 Dec 26 14:44 run -> ../run
Dnia czwartek, 24 stycznia 2013 21:36:50 Sam Varshavchik pisze:
> Jan Litwiński writes:
> > Dnia czwartek, 24 stycznia 2013 21:06:26 Sam Varshavchik pisze:
> > > Jan Litwiński writes:
> > > > Dnia piątek, 25 stycznia 2013 09:28:24 Ed Greshko pisze:
> > > >
> > > > subject is closed, I now use chro
Jan Litwiński writes:
Dnia czwartek, 24 stycznia 2013 21:06:26 Sam Varshavchik pisze:
> Jan Litwiński writes:
> > Dnia piątek, 25 stycznia 2013 09:28:24 Ed Greshko pisze:
> >
> > subject is closed, I now use chrony :)
> > thank you again
>
> Well, it doesn't matter any more, I suppose, but let m
Dnia czwartek, 24 stycznia 2013 21:06:26 Sam Varshavchik pisze:
> Jan Litwiński writes:
> > Dnia piątek, 25 stycznia 2013 09:28:24 Ed Greshko pisze:
> >
> > subject is closed, I now use chrony :)
> > thank you again
>
> Well, it doesn't matter any more, I suppose, but let me make a wild
guess:
>
On 01/25/2013 10:12 AM, Mark LaPierre wrote:
> I don't know if F18 has changed the way services start
Yes Since F17 the majority of services are controlled using systemd
instead of SysV scripts.
http://fedoraproject.org/wiki/Systemd
Your suggestions are out of date and not relevant to
On 01/24/2013 06:46 PM, Jan Litwiński wrote:
I have proglem with ntp service, I did:
systemctl enable ntpd.service
systemctl start ntpd.service
but ntp don't start at boot, starting by hand works. As a solution I
created rc.local and add to it systemctl start ntpd.service and it works. I
Jan Litwiński writes:
Dnia piątek, 25 stycznia 2013 09:28:24 Ed Greshko pisze:
subject is closed, I now use chrony :)
thank you again
Well, it doesn't matter any more, I suppose, but let me make a wild guess:
Your /var/tmp is a symlink, right?
pgpcSsISHEH9J.pgp
Description: PGP signature
Dnia piątek, 25 stycznia 2013 09:28:24 Ed Greshko pisze:
subject is closed, I now use chrony :)
thank you again
--
Jan Litwiński
http://netsjanek.blogspot.com/
http://netsjanek.bloog.pl/
Linux is like a wigwam no gates no windows but apache inside
--
users mailing list
users@lists.fedoraproject
On 01/25/2013 09:31 AM, Tom Horsley wrote:
> On Thu, 24 Jan 2013 17:23:10 -0800
> Rick Stevens wrote:
>
>> Package ypserv started...
> I'm not running ypserv, just ypbind, and sometimes it just
> isn't working when I boot. Tossing into rc.local something like
>
> /bin/bash -c 'sleep 10 ; service yp
On Thu, 24 Jan 2013 17:23:10 -0800
Rick Stevens wrote:
> Package ypserv started...
I'm not running ypserv, just ypbind, and sometimes it just
isn't working when I boot. Tossing into rc.local something like
/bin/bash -c 'sleep 10 ; service ypbind restart' > /dev/null 2>&1 < /dev/null &
always le
On 01/25/2013 09:22 AM, Jan Litwiński wrote:
> thsnk you for mantion about chronyd.service, I set up it and it works
> well, starts at boot.
> thank you
OK... Good
--
Programming today is a race between software engineers striving to build bigger
and better idiot-proof programs, and the U
On 01/25/2013 08:51 AM, Jan Litwiński wrote:
> Dnia piątek, 25 stycznia 2013 08:39:25 Ed Greshko pisze:
>> On 01/25/2013 07:46 AM, Jan Litwiński wrote:
>>> I have proglem with ntp service, I did:
>>>
>>> systemctl enable ntpd.service
>>> systemctl star
On 01/24/2013 05:08 PM, Tom Horsley issued this missive:
On Thu, 24 Jan 2013 19:55:46 -0500
Matthew Miller wrote:
Have you filed bugs for these? It's hard to fix problems if they're not
reported.
The biggest problem is NFS, and there are a slew of bugzillas
about NFS not working already. Ther
Dnia piątek, 25 stycznia 2013 08:39:25 Ed Greshko pisze:
> On 01/25/2013 07:46 AM, Jan Litwiński wrote:
> > I have proglem with ntp service, I did:
> >
> > systemctl enable ntpd.service
> > systemctl start ntpd.service
> >
> > but ntp don't start at b
On Thu, 24 Jan 2013 19:55:46 -0500
Matthew Miller wrote:
> Have you filed bugs for these? It's hard to fix problems if they're not
> reported.
The biggest problem is NFS, and there are a slew of bugzillas
about NFS not working already. There are also ypbind problems
which I also see bugzillas abo
Dnia piątek, 25 stycznia 2013 08:48:50 Ed Greshko pisze:
> On 01/25/2013 08:39 AM, Ed Greshko wrote:
> > Did you check the status after you started ntpd.service?
>
> I meant to type
>
> Did you check the status of ntpd.service after boot and before you
manually
> started it.
>
> (no cof
On Thu, Jan 24, 2013 at 06:56:14PM -0500, Tom Horsley wrote:
> > My question is what is correct
> > solution ?
> I don't know the correct solution, but I have a bunch of things
> I restart in my rc.local to get them to work right, so you are not
> alone.
Have you filed bugs for these? It's hard t
1 - 100 of 117 matches
Mail list logo
