On 23.04.2012 14:52, Dean E. Weimer wrote:
On 23.04.2012 14:10, Chuck Swiger wrote:
On Apr 23, 2012, at 12:08 PM, Dean E. Weimer wrote:
Tried rebuilding without the with SSL option set, oddly it started
once after that, but a restart caused same behavior. gdb doesn't
give me anything that I k
On 23.04.2012 14:10, Chuck Swiger wrote:
On Apr 23, 2012, at 12:08 PM, Dean E. Weimer wrote:
Tried rebuilding without the with SSL option set, oddly it started
once after that, but a restart caused same behavior. gdb doesn't give
me anything that I know how to interpret, gdb -c /ntpd.core. (I
On Apr 23, 2012, at 12:08 PM, Dean E. Weimer wrote:
> Tried rebuilding without the with SSL option set, oddly it started once after
> that, but a restart caused same behavior. gdb doesn't give me anything that
> I know how to interpret, gdb -c /ntpd.core. (I haven't really used gdb
> before, s
On 23.04.2012 13:19, Chuck Swiger wrote:
On Apr 23, 2012, at 11:13 AM, Dean E. Weimer wrote:
I am running NTPD built from ports on system that has had world
rebuilt without ntp. After doing some port updates this morning to
the latest OpenSSL which caused ntp to rebuild as its built against
t
On Apr 23, 2012, at 11:13 AM, Dean E. Weimer wrote:
> I am running NTPD built from ports on system that has had world rebuilt
> without ntp. After doing some port updates this morning to the latest
> OpenSSL which caused ntp to rebuild as its built against the OpenSSL port.
> ntpd now core dum
I am running NTPD built from ports on system that has had world rebuilt
without ntp. After doing some port updates this morning to the latest
OpenSSL which caused ntp to rebuild as its built against the OpenSSL
port. ntpd now core dumps at start, in order to attempt and resolve the
issue I tr
Regarding ntpd, Lowell wrote
>
> > # deny-by-default policy
> > restrict default ignore
>
>
> You're probably running into problems with your restrict clause, but
> I'm not sure what offhand.
> Use the "-d" flag to ntpd (or more than one) to get more information
> on what it thinks the problem is.
>Also... another thought. You might try disabling IPv6 unless you need
>it. (remove 'options INET6' from kernconf)
Yes, after I did that and recompiled the kernel, it got rid of the error
message.
Thanks!
___
freebsd-questions@freebsd.org mailing list
h
Shelby Westman <[EMAIL PROTECTED]> writes:
> I am a relatively new freeBSD user. The problem I describe below happens on
> both a 5.4 install and a 6.0 RC1 install.
>
> Right after installing the OS, I enable ntpd in rc.conf, and setup a simple
> config file in /etc/ntp.conf. When I reboot, I get
Eric Schuele wrote:
Shelby Westman wrote:
Hello, all,
I am a relatively new freeBSD user. The problem I describe below
happens on
both a 5.4 install and a 6.0 RC1 install.
Right after installing the OS, I enable ntpd in rc.conf, and setup a
simple
Are you intending on running an NTP dae
Shelby Westman wrote:
Hello, all,
I am a relatively new freeBSD user. The problem I describe below happens on
both a 5.4 install and a 6.0 RC1 install.
Right after installing the OS, I enable ntpd in rc.conf, and setup a simple
Are you intending on running an NTP daemon? Or are you just tryi
Hello, all,
I am a relatively new freeBSD user. The problem I describe below happens on
both a 5.4 install and a 6.0 RC1 install.
Right after installing the OS, I enable ntpd in rc.conf, and setup a simple
config file in /etc/ntp.conf. When I reboot, I get this message:
Oct 22 10:40:57 alter ntp
At 12:37 PM 8/20/2005, Dmitry Mityugov wrote:
On 8/20/05, fire67 <[EMAIL PROTECTED]> wrote:
> Hello , i'm on freebsd 5.4 and i tried to configure ntpd but i
have this problem :
>
> ntpd[546]: bind() fd 16, family 28, port 123, addr
fe80:9::2bd:a0ff:fe08:0, in6_is_addr_multicast=0 flags=0 fail
On 8/20/05, fire67 <[EMAIL PROTECTED]> wrote:
> Hello , i'm on freebsd 5.4 and i tried to configure ntpd but i have this
> problem :
>
> ntpd[546]: bind() fd 16, family 28, port 123, addr fe80:9::2bd:a0ff:fe08:0,
> in6_is_addr_multicast=0 flags=0 fails: Can't assign requested address
>
> Anyon
# ifconfig
xl0: flags=8943 mtu 1500
options=9
inet 192.168.1.1 netmask 0xff00 broadcast 192.168.1.255
inet6 fe80::20a:5eff:fe3e:ebf7%xl0 prefixlen 64 scopeid 0x1
ether 00:0a:5e:3e:eb:f7
media: Ethernet autoselect (100baseTX )
status: active
vr0: flags=
In my rc.conf , i have that :
xntpd_enable="YES"
xntpd_program="/usr/sbin/ntpd"
xntpd_flags="-p /var/run/ntpd.pid"
In ntp.conf , i have that :
server 62.4.16.80 prefer
server 195.220.94.163
server 134.214.100.6
driftfile /var/db/ntp.drift
restrict 127.0.0.1 mask 255.255.0.0 nomodify notra
This is my ntpd and i haven't got ipv6 connection but i want that ntpd uses
ipv4 and not ipv4 and ipv6.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL
Hello , i'm on freebsd 5.4 and i tried to configure ntpd but i have this
problem :
ntpd[546]: bind() fd 16, family 28, port 123, addr fe80:9::2bd:a0ff:fe08:0,
in6_is_addr_multicast=0 flags=0 fails: Can't assign requested address
Anyone knowns this problem ?
On Sat, 22 Jan 2005 02:32, Lowell Gilbert wrote:
> Ian Moore <[EMAIL PROTECTED]> writes:
> > On Wed, 19 Jan 2005 00:54, Lowell Gilbert wrote:
> > > Ian Moore <[EMAIL PROTECTED]> writes:
> > > > I've just realised I'm not running a name server at all on my 5.3
> > > > system. I have 4.9 installed on
Ian Moore <[EMAIL PROTECTED]> writes:
> On Wed, 19 Jan 2005 00:54, Lowell Gilbert wrote:
> > Ian Moore <[EMAIL PROTECTED]> writes:
> > > I've just realised I'm not running a name server at all on my 5.3 system.
> > > I have 4.9 installed on this computer too & I'd set up the caching server
> > > o
On Wed, 19 Jan 2005 00:54, Lowell Gilbert wrote:
> Ian Moore <[EMAIL PROTECTED]> writes:
> > I've just realised I'm not running a name server at all on my 5.3 system.
> > I have 4.9 installed on this computer too & I'd set up the caching server
> > on it, I guess I forgot that step when I installed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday 18 January 2005 23:14, John wrote:
> On Tue, Jan 18, 2005 at 04:04:30PM -0600, John wrote:
> > On Tue, Jan 18, 2005 at 07:23:41AM -0600, John wrote:
> > > On Tue, Jan 18, 2005 at 07:26:16AM +0100, Christian Hiris wrote:
> > > > -BEGIN PG
On Tue, Jan 18, 2005 at 04:04:30PM -0600, John wrote:
> On Tue, Jan 18, 2005 at 07:23:41AM -0600, John wrote:
> > On Tue, Jan 18, 2005 at 07:26:16AM +0100, Christian Hiris wrote:
> > > -BEGIN PGP SIGNED MESSAGE-
> > > Hash: SHA1
> > >
> > > On Tuesday 18 January 2005 01:09, John wrote:
> >
On Tue, Jan 18, 2005 at 07:23:41AM -0600, John wrote:
> On Tue, Jan 18, 2005 at 07:26:16AM +0100, Christian Hiris wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> >
> > On Tuesday 18 January 2005 01:09, John wrote:
> >
> > > This is what goes into the log:
> > > Jan 17 18:04:29 pear
Ian Moore <[EMAIL PROTECTED]> writes:
> I've just realised I'm not running a name server at all on my 5.3 system. I
> have 4.9 installed on this computer too & I'd set up the caching server on
> it, I guess I forgot that step when I installed 5.3.
> I'll set it up & see that makes any difference
On Tue, Jan 18, 2005 at 07:26:16AM +0100, Christian Hiris wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Tuesday 18 January 2005 01:09, John wrote:
>
> > This is what goes into the log:
> > Jan 17 18:04:29 pearl ntpd[838]: ntpd 4.2.0-a Sun Jan 9 10:58:59 CST 2005
> > (1) Jan 17
On Tue, 18 Jan 2005 17:13, Christian Hiris wrote:
> On Tuesday 18 January 2005 07:19, Ian Moore wrote:
> > Now I'm not sure what the best way to get around this would be. I run a
> > caching name server on the machine, so I guess I can tweak it to force
> > localhost.foo.com resolve to 127.0.0.1
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday 18 January 2005 07:19, Ian Moore wrote:
>
> Now I'm not sure what the best way to get around this would be. I run a
> caching name server on the machine, so I guess I can tweak it to force
> localhost.foo.com resolve to 127.0.0.1
I'm runnin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday 18 January 2005 01:09, John wrote:
> This is what goes into the log:
> Jan 17 18:04:29 pearl ntpd[838]: ntpd 4.2.0-a Sun Jan 9 10:58:59 CST 2005
> (1) Jan 17 18:04:29 pearl ntpd[838]: bind() fd 7, family 2, port 123, addr
> 0.0.0.0,in_clas
On Tue, 18 Jan 2005 12:50, Christian Hiris wrote:
> On Tuesday 18 January 2005 01:09, John wrote:
> > On Mon, Jan 17, 2005 at 12:49:00PM -0600, John wrote:
> > > On Mon, Jan 17, 2005 at 12:22:48PM -0600, John wrote:
> > > > On Tue, Jan 11, 2005 at 11:23:28PM +0900, Rob wrote:
> > > > > Ian Moore wr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday 18 January 2005 05:23, Rob wrote:
> Christian Hiris wrote:
> > On the server ntp.matrix.net I run ntpd with the following config files
> > (This machine still runs 5.3-BETA-4):
> >
> > # cat /etc/rc.conf | grep ntp
> > ntpdate_flags="-b cloc
Christian Hiris wrote:
On the server ntp.matrix.net I run ntpd with the following config files (This
machine still runs 5.3-BETA-4):
# cat /etc/rc.conf | grep ntp
ntpdate_flags="-b clock.netcetera.dk tick.keso.fi"
ntpdate_enable="YES"
ntpd_enable="YES"
- -
No need for "ntpdate -b"
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday 18 January 2005 01:09, John wrote:
> On Mon, Jan 17, 2005 at 12:49:00PM -0600, John wrote:
> > On Mon, Jan 17, 2005 at 12:22:48PM -0600, John wrote:
> > > On Tue, Jan 11, 2005 at 11:23:28PM +0900, Rob wrote:
> > > > Ian Moore wrote:
> > > >
On Mon, Jan 17, 2005 at 12:49:00PM -0600, John wrote:
> On Mon, Jan 17, 2005 at 12:22:48PM -0600, John wrote:
> > On Tue, Jan 11, 2005 at 11:23:28PM +0900, Rob wrote:
> > > Ian Moore wrote:
> > > > Hi,
> > > > Ever since I upgraded from 5.2.1-RELEASE to 5.3-RELEASE, I've been
> > > > getting the
On Mon, Jan 17, 2005 at 12:22:48PM -0600, John wrote:
> On Tue, Jan 11, 2005 at 11:23:28PM +0900, Rob wrote:
> > Ian Moore wrote:
> > > Hi,
> > > Ever since I upgraded from 5.2.1-RELEASE to 5.3-RELEASE, I've been
> > > getting the
> > > following error on boot:
> > > ntpd[380]: bind() fd 7, famil
On Tue, Jan 11, 2005 at 11:23:28PM +0900, Rob wrote:
> Ian Moore wrote:
> > Hi,
> > Ever since I upgraded from 5.2.1-RELEASE to 5.3-RELEASE, I've been getting
> > the
> > following error on boot:
> > ntpd[380]: bind() fd 7, family 28, port 123, addr fe80:1
> > ::204:61ff:fe46:be89, in6_is_addr_mu
Ian Moore wrote:
Hi,
Ever since I upgraded from 5.2.1-RELEASE to 5.3-RELEASE, I've been getting the
following error on boot:
ntpd[380]: bind() fd 7, family 28, port 123, addr fe80:1
::204:61ff:fe46:be89, in6_is_addr_multicast=0 flags=0 fails: Can't assign
requested address
ntpd seems to be worki
Hi,
Ever since I upgraded from 5.2.1-RELEASE to 5.3-RELEASE, I've been getting the
following error on boot:
ntpd[380]: bind() fd 7, family 28, port 123, addr fe80:1
::204:61ff:fe46:be89, in6_is_addr_multicast=0 flags=0 fails: Can't assign
requested address
ntpd seems to be working from what I ca
38 matches
Mail list logo
