similar to: rsync & Time Zones

It's much easier than that. The linux box keeps time in GMT, and displays it in the configured time zone. Try this, on the linux box: "touch testfile ls -l testfile TZ=EST5 export TZ ls -l testfile" You will see the displayed time change, because it's being translated from epoch time (that's what I call it, anyway) - seconds since midnight, January 1, 1970. Your windows

I''m not sure if this fits in Rails'' core but since I spent sometime trying to solve a problem and couldn''t find any solution, I decided to share this method I''ve created to extend ActiveRecord::Relation. Here''s a Gist of it: https://gist.github.com/leods92/7164159 The problem is that when we try grouping timestamps by date, SQL returns unexpected

POSIXt vectors do not support different time zones element-to-element. If you want to keep track of timezones per element, you have to create a vector of timestamps (I would recommend POSIXct using UTC) and a parallel vector of timezone strings. How you manipulate these depends on your use cases, but from R's perspective you will have to manipulate them element-by-element. I complained about

Sys.setenv(TZ = "GMT") will set the local time zone to GMT so there would only be one time zone regardless of whether local or GMT were used. On Thu, Oct 10, 2024 at 11:17?AM Jan van der Laan <rhelp at eoos.dds.nl> wrote: > > Thanks. > > On 10/10/24 16:13, Jeff Newmiller wrote: > > POSIXt vectors do not support different time zones element-to-element. > >

Thanks. On 10/10/24 16:13, Jeff Newmiller wrote: > POSIXt vectors do not support different time zones element-to-element. > I complained about this on this list a couple of decades ago, and was chastised for it. Evidently handling timezones per element was considered to be too impractically slow to be a standard feature. This is where it is unclear to me what the purpose is of the

Hi, I have 2 Debian testing boxes running a very similar setup (both running the latest aptosid kernel); on one of them, since the iptables/libxtables10 packages have been upgraded from 1.4.19.1-1 to 1.4.20-2, shorewall-init can''t start shorewall anymore and for this reason ifupdown also fails triggering firewall up. Shorewall can be successfully started later on, and ifupdown starts

It is not completely clear to me how time zones work with POSIXlt objects. For POSIXct, I can understand what happens: time is always stored in GMT, the `tzone` attribute only affects how the times are displayed. All computations etc. are done in GMT. POSIXlt objects have both a `tzone` attribute and a `zone` field. It seems that the `zone` field is largely ignored. It only seems to be used

I have read the documentation, performed the diagnostic tests, checked the archives, so if the answer is there, please accept my apologies in advance and simply direct me. I am running redhat Linux 2.0.3 and using smbmount to mount several directories from NT3.51 servers which are distributed gloablly in different timezones. Once mounted the files all have local timestamps which makes syncing

?s 15:13 de 10/10/2024, Jeff Newmiller via R-help escreveu: > POSIXt vectors do not support different time zones element-to-element. > > If you want to keep track of timezones per element, you have to create a vector of timestamps (I would recommend POSIXct using UTC) and a parallel vector of timezone strings. How you manipulate these depends on your use cases, but from R's

Dear Experts, I would like to ask everybody: what would you advise to use as a storage cluster, or as a distributed filesystem. I made my own research of what I can do, but I hit a snag with my seemingly best choice, so I decided to stay away from it finally, and ask clever people what they would use. My requirements are: 1. I would like to have one big (say, comparable to petabyte)

For a same configuration in which the default policy is drop and only one connection is accepted in rules, continuous pinging to devices will stop squarely in 4.0.15 as soon as a very basic firewall is enabled whereas in 4.4.26.1, pinging will still continue after the firewall is enabled. All tests are done with proper reboot of the unit3 where the firewall is applied: unit1 <---> eth4

Hello, I'm having a major problem with the timestamps in both the Icecast access.log and error.log. The timestamp on the logfiles themselves is accurate, but the logging of the various connections to my streams is in UTC. No matter how I try to configure the hwclock or the system clock, the log timestamp is always UTC, which is 8 hours ahead of my current time zone. I've even tried

I've configured a secondary slave nameserver based on what I consider rather expert advice, but it's not working as expected. I'm trying to determine if I've done something wrong with basic configuration or if there are AD/DC nuances afoot. The main nameserver is the domain Active Directory/Domain Controller running Samba 4.4.16 on Slackware64 14.2. This has been running for a few

Hello. I would like to transfer files which have changed on another box. The rsync man page says: --size-only ..This is useful when starting to use rsync after using another mirroring system which may not preserve timestamps exactly.. Which is my situation. My problem is that the size-only switch (clearly) ignores files with different content, but that have the same size. I'd like to

Hi All, I used the following script from the dtrace manual to measure how long a particular process runs on the cpu. Modified it to look at the exact timestamps: [i] sched:::on-cpu { self->ts = timestamp; printf("on=%d\n", self->ts) } sched:::off-cpu /self->ts/ { printf("off=%d\n", timestamp) self->ts = 0; } [/i] The output looks like this: [i]on=24591 off=24603

I have a set of labels arranged along a timeframe in a. Each label has a timestamp and marks a state until the next label. The dataframe a contains 5 such timestamps and 5 associated labels. This means, on a continious scale between 1-100, there are 5 markers. E.g. 'abc' marks the timestampls between 10 and 19, 'def' marks the timestamps between 20 and 32, and so on. a <-

Hi Steven, Yes, both file systems are the same. rsync -nri --modify-window=1 <src> <dest> Gives me the following for most files >f..T....... 2015_167_1_1__Boy_What_A_Girl_R2/2015_167_1_1__Boy_What_A_Girl__UHD_DPX_R2/ BWAG_R2_00138428.dpx Although a few have >f..T......n 2015_167_1_1__Boy_What_A_Girl_R2/2015_167_1_1__Boy_What_A_Girl__UHD_DPX_R2/ BWAG_R2_00135909.dpx

Hi R experts, I have the following timeseries data: #example data structure a <- c(NA,1,NA,5,NA,NA,NA,10,NA,NA) c <- c(1:10) df <- data.frame(timestamp=a, sequence=c) print(df) where i would like to linearly interpolate between the points 1,5, and 10 in 'timestamp'. Original timestamps should not be modified. Here the code I use to run the interpolation (so far): # linear

Hi, I'm working on the ticket #743 omindex: delay libmagic checks <https://trac.xapian.org/ticket/743>. As the ticket's Description mention, the call to libmagic is expensive than call the stat, so we can check the size by call the stat to get size before call libmagic to get a mime type. But how about the timestamps check? since timestamps check need to iterate the DB to check if

My server runs S10u5. All slices are UFS. I run a couple of sparse zones on a seperate slice mounted on /zones. When S10u6 comes out booting of ZFS will become possible. That is great news. However, will it be possible to have those zones I run now too? I always understood ZFS and root zones are difficult. I hope to be able to change all FS to ZFS, including the space for the sparse zones. Does