On Tue, 11 Nov 2014, Bruce Lilly wrote:
==> time.32.1 <==
real 0.43
user 0.38
sys 0.03
Such short run-times are not particularly accurate since times(2) only
counts time in terms of kernel clock ticks (e.g. 100hz) and other
factors may also dominate the run times. Use OpenIndiana/Solaris
- Original Message -
> From: "Marcel Telka"
> To: "Discussion list for OpenIndiana"
> Sent: Tuesday, November 11, 2014 2:31:55 PM
> Subject: Re: [OpenIndiana-discuss] ZFS ACLs - Cannot Write Microsoft Office
> Files over CIFS
>
> I'm not sure it is related, but you might want to look at
On Tue, Nov 11, 2014 at 01:45:32PM -0600, Andrew Martin wrote:
> Hello,
>
> I am running an OpenIndiana server with a ZFS pool exporting a share over both
> NFSv4 and CIFS. The CIFS export is mounted by Windows 7 clients. On this
> share,
> I have the following ACLs configured for directories:
>
Hello,
I am running an OpenIndiana server with a ZFS pool exporting a share over both
NFSv4 and CIFS. The CIFS export is mounted by Windows 7 clients. On this share,
I have the following ACLs configured for directories:
0:owner@:list_directory/read_data/add_file/write_data/add_subdirectory
Bruce Lilly wrote:
I ran a test by building both 32-bit and 64-bit versions of Ted Faber's
[...]
Simple test input to demonstrate 32-bit time_t issue:
# cat test.grap
.G1
frame invis
label bot strftime("%Y-%m-%dT%H:%M:%S", strptime("%Y-%m-%dT%H:%M:%S",
"2038-01-20T23:59:59"))
.G2
64-bit resul
Some past comments about 32-bit vs. 64-bit and some recent test results.
Bob Friesenhahn
> While it would be nice if Solaris software was all 64-bit, in actual
practice I notice no difference in day to day use between systems with
32-bit applications and 64-bit. Only certain memory-hungry appli
