similar to: strange behavior with "dos filetime resolution = yes"

On Tue, Jan 26, 2016 at 11:57:58AM +0100, Hubert Gilch wrote: > Hello, > > i see a strange behavior with timestamps of files on a samba share > (4.2.6 on SLES 12 SP1 and 4.1.8 on Ubuntu 14.04) with "dos filetime > resolution = yes": On older samba versions, windows properties > dialogue correctly shows only even seconds, but (at least) the two > indicated versions

Hello useRs, Pls help with removing a single interaction term from a formula: summary( glm.turn.2 <- glm(cbind(turn.cnt,tot.cnt-turn.cnt)~sn+poly(relAge,2,raw=T)+termfac+rate:termfac,data=fix, family="quasibinomial") ) Gives Coefficients: Estimate Std. Error t value Pr(>|t|) (Intercept) -7.028467

I am using an example posted in this help forum to work with a file. the head of the file looks like: 988887 2007-03-05 2007-06-01 90 3 5.450 205500.00 999.00 999.000 0.000 0 0 988887 2007-03-06 2007-06-01 90 3 5.450 205500.00 999.00 999.000 0.000 1 0 988887 2007-03-07 2007-06-01 90 3 5.450 205500.00 999.00 999.000 -0.100 2 0 988887 2007-03-08 2007-06-01 90 3 5.450 205500.00 999.00 999.000 -0.100

I am attemting to use glmD in order to use latex(obj) afterwards. Glm works fine, glmD throws an error: > conv.go <- glmD(cbind(go.cnt,tot.cnt-go.cnt)~sn+rcs(relAge,4)+termfac+rate:termfac+ + I(relAge*term>(term-1.25))+I((prevbal/tot.cnt)*1e-4)+prod+newmort+ +

Hello, i had to upgrade a server from 3.6 to 4.0.10. Now i have a problem had already i solved again. The problem is that a machines program is old and require dos filetime resolution = yes but i does not work with the new 4.0.10 [produktion] path=/home/filestore/produktion browseable = yes writable = yes # create mask = 0777 # directory mask = 0777 #

Hi all, I am having a weird problem with the filetimes, which I can not seem to get under control: The Scenario: I have a file: test.pl 06.07.2005 14:00 Now I make a copy of the FIle to my local harddrive and the date (creation date) stay the same. Now when I put this file pack on the samba share the date and time also stays the same. Now if I login to the samba server via ssh and

Hello! On Win9x clients: With dos filetime = no, if the owner change the file the file's modify date will be the owners workstation date, if another user change the file the files modify date will be the samba servers date. On WinNT clients the behavior is uniform: even if the owner change the file, the file's modify date will be the samba servers date. How can I achieve that the Win9x

Signed-off-by: Alex Nelson <ajnelson at cs.ucsc.edu> --- xml/hivexml.c | 20 +++++++++++++++++--- 1 files changed, 17 insertions(+), 3 deletions(-) diff --git a/xml/hivexml.c b/xml/hivexml.c index 5030c24..98b90c5 100644 --- a/xml/hivexml.c +++ b/xml/hivexml.c @@ -185,6 +185,8 @@ filetime_to_8601 (int64_t windows_ticks) char *ret; time_t t; struct tm *tm; + int64_t sub_seconds;

I am not getting much benefit from using oplocks = False or dos filetime resolution = True in Samba 1.9.18p3 on Solaris 2.5.1 and the Developer Studio in Digital Visual Fortran (v6.0) on WinNT4,SP4. I am also setting my PC clock to the samba server. I still get a lot of messages from the Studio informing me the source code files and workspaces have changed outside the editor or Studio

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

Greetings useRs, Can anyone provide an example how to use ff to feed a very large data frame to glm? The data.frame cannot be loaded in R using conventional read.csv as it is too big. glm(...,data=ff.file) ?? Thank you Stephen B

Hello everbody, this is really urgent. at the moment the status is as follows: We changed the primafy group to a group without german characters: "?,?,?". It works fine, as long as the primary group as full access to the file. If not, it doesn't work. The Problem in detail: Situation 1: User is member of DOMAIN+GROUP. DOMAIN+GROUP is owner of file utime is called and