Re: clockctl(4) vs settimeofday(2)

On Dec 7, 9:56am, rich.nesw...@gmail.com (Rich Neswold) wrote: -- Subject: Re: clockctl(4) vs settimeofday(2) | > Using the syscall is simpler and cheaper, so I think the man page should | > be updated. | | Is settimeofday() called frequently enough that "cheaper" is a concern? | What is more

Re: clockctl(4) vs settimeofday(2)

In article , Paul Goyette wrote: >According to the clockctl(4) man page, operations on system time should >first try the /dev/clockctl device, and only fall-back to the syscall() >if the device is not available: > >

Re: clockctl(4) vs settimeofday(2)

On Mon, 7 Dec 2015, Christos Zoulas wrote: On Dec 7, 9:56am, rich.nesw...@gmail.com (Rich Neswold) wrote: -- Subject: Re: clockctl(4) vs settimeofday(2) | > Using the syscall is simpler and cheaper, so I think the man page should | > be updated. | | Is settimeofday() called frequently enough

Latest amd64 snapshot has problems with disk sizes

Just tried to install current using the latest AMD64 snapshot 201512071640Z on a blank SATA drive. Boots up off the memory stick OK and after allocating partitions it fails when trying to newfs the first partition rwd0a. An error: ioctl DIOCGMEDIASIZE failed 19 appears in the log messages

Re: clockctl(4) vs settimeofday(2)

On Dec 8, 6:42am, p...@vps1.whooppee.com (Paul Goyette) wrote: -- Subject: Re: clockctl(4) vs settimeofday(2) | > If you know that you are not going to succeed (because you are not | > root), you should cache the fd, and just do the ioctl each time | > you want to sync to reduce latency. The

daily CVS update output

Updating src tree: P src/distrib/sets/lists/modules/mi P src/lib/libc/sys/adjtime.2 P src/lib/libc/sys/clock_settime.2 P src/lib/libc/sys/gettimeofday.2 P src/lib/libc/sys/ntp_adjtime.2 P src/lib/libutil/parsedate.3 P src/lib/libutil/parsedate.y P src/sbin/drvctl/drvctl.c P