Can't get ntp to work
My ntpd stopped synchronizing clock sometime ago (default ntp.conf). To debug the problem I've tried running ntpdate and got strange results: > # ntpdate 0.freebsd.pool.ntp.org > 18 Oct 13:53:14 ntpdate[55102]: no server suitable for synchronization found > > # ntpdate -u 0.freebsd.pool.ntp.org > 18 Oct 13:53:19 ntpdate[55119]: adjust time server 193.25.222.240 offset > 0.002672 sec This would point to broken firewall BUT: > # nmap -p123 -sU 0.freebsd.pool.ntp.org > > Starting Nmap 6.49BETA5 ( https://nmap.org ) at 2015-10-18 13:52 CEST > Nmap scan report for 0.freebsd.pool.ntp.org (193.25.222.240) > Host is up (0.027s latency). > Other addresses for 0.freebsd.pool.ntp.org (not scanned): 94.154.96.7 > 95.158.95.123 46.175.224.7 > rDNS record for 193.25.222.240: afrodyta.complex.net.pl > PORTSTATE SERVICE > 123/udp open ntp > > Nmap done: 1 IP address (1 host up) scanned in 0.64 seconds So there is nothing blocking the traffic. Any ideas ? ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
mountd suddenly stopped working
I have just rebooted an old system after 100 days of uptime and this came up: Jun 30 15:39:00 ghost mountd[1592]: can't change attributes for /tftpboot Jun 30 15:39:00 ghost mountd[1592]: bad exports list line /tftpboot -ro -mapall Both /etc/exports and /tftpboot are many years old and didn't cause any problems until today. I have tried fsck and rebooting but it didn't help. uname -a FreeBSD ghost.pnet.one.pl 8.2-STABLE FreeBSD 8.2-STABLE #6: Sun Nov 13 05:32:38 CET 2011 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: mountd suddenly stopped working
On Sat, 30 Jun 2012 16:21:18 +0200, Ronald Klop wrote: On Sat, 30 Jun 2012 15:53:53 +0200, Marcin Wisnicki mwisnicki+free...@gmail.com wrote: I have just rebooted an old system after 100 days of uptime and this came up: Jun 30 15:39:00 ghost mountd[1592]: can't change attributes for /tftpboot Jun 30 15:39:00 ghost mountd[1592]: bad exports list line /tftpboot -ro -mapall Than probably somebody changed something else. Can you provide the content of your exports file? OK, I've found the reason. There were two paths exported with same attributes: /tftpboot -ro -mapall=nobody /vol/tank1 -ro -mapall=nobody As long as there is a filesystem mounted on /vol/tank1, above exports will work. Since I've disconnected that drive, there was nothing mounted this time. Apparently mountd does not allow exporting multiple paths from a single filesystem on separate lines if they happen to have identical attributes. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: snd_hda : sometimes sound sometimes not
On Thu, 12 May 2011 08:47:13 +0200, David Demelier wrote: Hello, I don't know if there is a lot of changes in the snd_hda driver in the -STABLE branch but since I upgraded to it sometimes I have sound and sometimes not. Try disabling MSI in loader.conf: hw.pci.enable_msix=0 hw.pci.enable_msi=0 and see if it works. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Portmaster questions (Was: Re: Using Portupgrade?)
On Sun, 03 Aug 2008 22:14:54 -0700, Doug Barton wrote: It's really not appropriate to hijack the portupgrade thread for this, so I'm starting a new subject. Also, please respect followups to -ports. Alex Goncharov wrote: Don't remember everything of that sort but here are a couple of things I would like to ask portmaster users' opinion and advice about: 1. I see a significant difference in the time it takes to get the same information using the two tools: As I understand it, portupgrade uses the INDEX file to determine whether ports are up to date. Actually I think it uses bdb cache of index (INDEX-7.db) and also lies about it (says up-to-date with port instead of up-to-date with index). It's not even doing a good job at it, standard pkg_version significantly outperforms it: # time portversion -v | wc -l 769 real0m15.027s user0m9.235s sys 0m5.173s # time pkg_version -Iv | wc -l 769 real0m4.707s user0m3.648s sys 0m0.798s ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
