From: Bohuslav Kabrda <bkabrda@...>
Date: 2012-10-05T16:34:41+09:00
Subject: [ruby-core:47843] Re: [ruby-trunk - Bug #7109][Open] File.utime doesn't set nanoseconds

----- Original Message -----
> 2012/10/5 bkabrda (Bohuslav Kabrda) <bkabrda@redhat.com>:
> 
> > I'm having a problem with File.utime on RHEL 5/CentOS 5. The
> > File.utime method seems not to set nanoseconds properly, see the
> > attached test case, that fails (the nanoseconds get rounded to
> > thousand, so in fact I get microseconds). The test doesn't seem to
> > fail on newer platforms with the same Ruby version, though (RHEL
> > 6/CentOS 6, Fedora 17). Note, that when creating/modifying files,
> > the nanoseconds get set and are returned properly, so it seems
> > that they are supported by filesystem.
> 
> utimensat system call is required to set nanosecond filestamp.
> It is available since Linux 2.6.22.
> (glibc support is also required but I'm not sure the exact version.)
> 
> I guess RHEL 5/CentOS 5 is older than that.
> --
> Tanaka Akira
> 
> 

True, kernel version is 2.6.19. So is there another way to solve this or do I have to get along with microseconds?

Thanks.

-- 
Regards,
Bohuslav "Slavek" Kabrda.