similar to: DO NOT REPLY [Bug 6672] New: mtim.tv_nsec not used when reading time of a file

having trouble compiling dovecot-1.1hg latest pull I'm amost thinking _GNU_SOURCE needs to be defined as its built to work Any suggestions welcome. make[4]: Nothing to be done for `all'. make[4]: Leaving directory `/home/dan/software_projects/dovecot-1.1/src/lib-storage/list' Making all in index make[4]: Entering directory

On Aug 10, 2018, at 1:28 PM, Marshall Clow via cfe-dev <cfe-dev at lists.llvm.org> wrote: > > * The clock stuff being added in C++20 has already been discussed here. I’ve missed the discussions on file_time_type, however I thought I should throw in my opinion here before it is too late to do anything about it. I believe it is a mistake to model file_time_type with 128 bits. It

The existing APIs guestfs_stat, guestfs_lstat and guestfs_lstatlist return a stat structure that contains atime, mtime and ctime fields that store only the timestamp in seconds. Modern filesystems can store timestamps down to nanosecond granularity, and the ordinary glibc stat(2) wrapper will return these in "hidden" stat fields: struct timespec st_atim; /* Time of last

Full_Name: Tim Middelkoop Version: 0.64.0 OS: IRIX 6.3 on O2 Submission from: (NULL) (128.119.88.192) Various IRIX complile issues src/nmath/pnt.c IRIX cc does not like double negatives Makeconf,config.site,etc/Makeconf f77 pic hack, should change Makeconf.in or other... change -PIC with -KPIC enjoy, tim... === diff -ru orig/R-0.64.0/src/nmath/pnt.c R-0.64.0/src/nmath/pnt.c ---

I'm looking to clarify this entry I found in a changelog(line 2062ish) on a CentOS 5 box for Apache 2.2.3 *) mod_include no longer allows an ETag header on 304 responses. PR 19355. [Geoffrey Young <geoff apache.org>, Andr? Malo] Loading the mod_include module prevents any ETags headers from being sent from the box. If I comment out mod_include, ETags are sent as expected.

On systems using nanoseconds differences should be taken into consideration. --- a/generator.c 2014-06-14 01:05:08.000000000 +0200 +++ b/generator.c 2014-12-25 11:19:54.000000000 +0100 @@ -588,7 +588,13 @@ if (ignore_times) return 0; - return cmp_time(st->st_mtime, file->modtime) == 0; + return cmp_time(st->st_mtime, file->modtime) == 0 +#ifdef ST_MTIME_NSEC + ?

Hey all, Found a email thread from Jan 2007 discussing the inability to set request headers (like ETag and If-Modified-Since) through the API, and this is something that''s bothering me a bit. Currently the "way" to do this is to subclass Mechanize and override set_headers(). That seems fine for headers that you''d like to send in every request or for classes of request,

Hi all, I'd like to output structured data for all of the gathered timers with the full nanosecond numbers to a file, say JSON for example. Does the timer infrastructure support this, or at least installing some custom print handlers? If not, does any of that sound like an interesting patch? David

Hi All, I recently committed <filesystem> to trunk. I wanted to bring attention to some quirks it currently has. First, it's been put in a separate library, libc++fs, for now. Users are responsible for linking the library when they use filesystem. Second, it should still not be considered ABI stable. Vendors should be aware of this before shipping it. Hopefully all the standard and

Windows-32 has a time structure called FILETIME, a 64-bit value representing the number of 100-nanosecond intervals since January 1, 1601 (UTC). That is not a typo, the year is 1601. Does anyone have a clue(or algorhithm)for how this is converted to something a little more POSIX-like ? Thank you, Derek -- Derek N. Eder Gothenburg University VINKLA - Vigilance and Neurocognition

Okay, well the OpenBSD install/chroot guide is a good starting point.... Anyhow, Can someone shed some light on these particular error messages? [Sat Dec 17 18:42:34 2005] [notice] Initializing etag from /var/www/logs/etag-state [Sat Dec 17 18:42:34 2005] [notice] chrooted in /var/www [Sat Dec 17 18:42:34 2005] [notice] changed to uid 1, gid 1 [Sat Dec 17 18:42:34 2005] [notice] Apache/1.3.29

Apple File System Guide is released. https://developer.apple.com/library/prerelease/content/documentation/FileManagement/Conceptual/APFS_Guide/GeneralCharacteristics/GeneralCharacteristics.html >Nanosecond Timestamp Granularity > >APFS supports 1 nanosecond timestamp granularity, which improves >upon the 1 second timestamp granularity of HFS+. >Compatibility > >You can share

https://bugzilla.samba.org/show_bug.cgi?id=12742 Bug ID: 12742 Summary: a proposal: fix bogus nanosecond mtimes on transfer (patch included) Product: rsync Version: 3.1.1 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 Component: core

Hi, I''m using Mechanize, and I''ve developed a lot of code around it. I''d like to be able to check the Etag header during a get to see if the page has changed, as well as some other http header information. Can I do that without hacking Mechanize myself? Does anyone have any examples of how to do this? William

Dear All, Along with the files that suddenly disappear, we have a bit of a problem with these that do not. Namely, in my test runs I can see a small but stable set of files, that rsync is repeatedly trying to transfer, and then repeatedly fails to updates their times ; and then the story repeats itself. The situation is illustrated by the log snippet below, where I have changed file names to

While digging through the time code, I found something very strange in do_settime: x = (secs * 1000000000ULL) + (u64)nsecs - system_time_base; y = do_div(x, 1000000000); spin_lock(&wc_lock); wc_sec = _wc_sec = (u32)x; wc_nsec = _wc_nsec = (u32)y; spin_unlock(&wc_lock); The value "x" appears to be the number of nanoseconds, while the value

PHRASE QUERY Xapian::Query((MBOX:12345678-1234-1234-1234-1234567890ab AND (LP:backup:(pos=1) PHRASE 6 LP:c::(pos=2) PHRASE 6 LP:program files:(pos=3) PHRASE 6 LP:Mozilla Firefox:(pos=4) PHRASE 6 LP:res:(pos=5) PHRASE 6 LP: table-add-column-after-hover.gif:(pos=6)))) AND QUERY Xapian::Query((MBOX:12345678-1234-1234-1234-1234567890ab AND LP:backup:(pos=1) AND LP:c::(pos=2) AND LP:program

figured out how to use ldapsearch also to get what I want. Also found how to convert AD time to unix time Another thing I wanted calculated was when an account expires. ldapsearch -h ad.mydomain.tld -b dc=ad,dc=mydomain,dc=tld "(sAMAccountName=$user)" gives all the good information about a user. here is how I used it to tell me all accounts expiring this next month. h=ad.mydomain.tld

HI there, I?ve discovered DTrace few days ago and I?m currently stuck on a cpu stats problem. I?m trying to poll the cpu_t.cpu_acct[] array to pull idle, system and user values. So, I made this little script: ------------------------------------------------------------------------------------------------------ #!/usr/sbin/dtrace -s #pragma D option quiet this uint64_t start; this hrtime_t

On Aug 10, 2018, at 9:35 PM, Eric Fiselier <eric at efcs.ca> wrote: > > Part of me is still concerned with the future, and the filesystems which are yet to exist. > Me too. But it is best to target modern systems when targeting future systems adds an unnecessary cost. When future systems come into being, it is likely because future hardware is making those future systems