search for: pdt

...single value rather than a vector, from inputs that I thought were reasonable. Here's an example to illustrate: > t0 <- ISOdatetime(2002,6,24,0,0,10) ## expected a sequence of 16 times 1 second apart > seq.POSIXt(from=t0,to=t0+15,by='1 sec') [1] "2002-06-24 00:00:10 PDT" ## traces to this call > seq.default(1024902010,1024902025,by=1) [1] 1024902010 > ## which is due to the following expressions in seq.default() del <- to - from ## a few lines omitted dd <- abs(del)/max(abs(to), abs(from)) if (dd < sqrt(.Machine$doubl...

These source addresses are likely spoofed, but am still curious whether other FreeBSD admins saw a preponderance of DNS probes originating from Microsoft corp subnets ahead of the recent ISC bind vulnerability announcement? Roger Marquis Jul 28 16:51:23 PDT named[...]: client 94.245.67.253#10546: query (cache) 'output.txt/A/IN' denied Jul 28 16:51:23 PDT named[...]: client 94.245.67.253#10543: query (cache) 'output.txt/A/IN' denied Jul 28 16:51:18 PDT named[...]: client 94.245.67.253#10546: query (cache) 'output.txt/A/IN' d...

...yude Paul wrote: > Since we're going to be implementing suspend/resume reprobing very soon, > we need to make sure we are extra careful to ensure that our locking > actually protects the topology state where we expect it to. Turns out > this isn't the case with drm_dp_port_setup_pdt() and > drm_dp_port_teardown_pdt(), both of which change port->mstb without > grabbing &mgr->lock. > > Additionally, since most callers of these functions are just using it to > teardown the port's previous PDT and setup a new one we can simplify > things a bit and...

...de, and will write Rd files for them. -Don > hrs <- 3600 > dys <- 24*hrs ## ## time range 60 hours ## pretty.ct() chooses 3 hours as a pretty interval ## nhr <- 60 > t1 <- ISOdatetime(2002,6,14,0,0,0)+hrs*runif(5,0,nhr) > pretty.ct(t1) [1] "2002-06-15 03:00:00 PDT" "2002-06-15 06:00:00 PDT" "2002-06-15 09:00:00 PDT" "2002-06-15 12:00:00 PDT" [5] "2002-06-15 15:00:00 PDT" "2002-06-15 18:00:00 PDT" "2002-06-15 21:00:00 PDT" "2002-06-16 00:00:00 PDT" [9] "2002-06-16 03:00:00 P...

...; > Since we're going to be implementing suspend/resume reprobing very soon, > > we need to make sure we are extra careful to ensure that our locking > > actually protects the topology state where we expect it to. Turns out > > this isn't the case with drm_dp_port_setup_pdt() and > > drm_dp_port_teardown_pdt(), both of which change port->mstb without > > grabbing &mgr->lock. > > > > Additionally, since most callers of these functions are just using it to > > teardown the port's previous PDT and setup a new one we can simpli...

Since we're going to be implementing suspend/resume reprobing very soon, we need to make sure we are extra careful to ensure that our locking actually protects the topology state where we expect it to. Turns out this isn't the case with drm_dp_port_setup_pdt() and drm_dp_port_teardown_pdt(), both of which change port->mstb without grabbing &mgr->lock. Additionally, since most callers of these functions are just using it to teardown the port's previous PDT and setup a new one we can simplify things a bit and combine drm_dp_port_setup_pdt(...

Since we're going to be implementing suspend/resume reprobing very soon, we need to make sure we are extra careful to ensure that our locking actually protects the topology state where we expect it to. Turns out this isn't the case with drm_dp_port_setup_pdt() and drm_dp_port_teardown_pdt(), both of which change port->mstb without grabbing &mgr->lock. Additionally, since most callers of these functions are just using it to teardown the port's previous PDT and setup a new one we can simplify things a bit and combine drm_dp_port_setup_pdt(...

...he leading 10 digits and convert to POSIXct as.POSIXct(as.numeric(gsub("(^.{10}).+","", Timestamp)), origin="1970-01-01") as.POSIXct(as.numeric(gsub("(^.{10}).+","\\1", ais$Timestamp)), origin="1970-01-01") [1] "2017-07-11 07:09:57 PDT" "2017-07-11 06:45:37 PDT" "2017-07-11 06:40:34 PDT" "2017-07-11 06:34:46 PDT" "2017-07-11 06:32:26 PDT" [6] "2017-07-11 06:29:34 PDT" "2017-07-11 06:26:37 PDT" "2017-07-11 06:20:24 PDT" "2017-07-11 06:17:18 PDT"...

...irly large set of data with the following attributes: >str(raw.data) `data.frame': 1429 obs. of 16 variables: $ TStamp :`POSIXlt', format: chr "2001-11-25 02:00:00" "2001-11-25 01:55:00" "2001-11-25 01:50:00" "2001-11-25 01:45:00" ... $ iPDT.AHU14.14: num 0.0122 0.0125 0.0120 0.0120 0.0122 ... $ iPDT.AHU14.15: num 0.0121 0.0123 0.0119 0.0119 0.0121 ... $ iPDT.AHU14.16: num 0.00635 0.00657 0.00608 0.00608 0.00631 ... $ iPDT.AHU14.17: num 0.0300 0.0304 0.0302 0.0300 0.0303 ... $ iPDT.AHU15.15: num 0.0986 0.0984 0.0980 0.0979 0.0...

Hmmm...not quite sure where to go to fix this up. Samba 4 PDC, 1 W2K3R2, 1 W2K8R2 additional DC's. samba.log perpetually spewing: [Fri Jun 11 14:47:42 2010 PDT, 0 librpc/rpc/dcerpc_util.c:619:dcerpc_pipe_auth_recv()] Failed to bind to uuid e3514235-4b06-11d1-ab04-00c04fc2dcd2 - NT_STATUS_INVALID_PARAMETER [Fri Jun 11 14:47:42 2010 PDT, 0 dsdb/repl/drepl_notify.c:189:dreplsrv_notify_op_callback()] dreplsrv_notify: Failed to send DsReplicaSync to 58bfc8...

...5-917d-21418ac96f06 DSA invocationId: b5e8a8b6-ada3-472f-bee8-4e7d9ab813bc ==== INBOUND NEIGHBORS ==== CN=Configuration,dc=ad,dc=example,dc=com McBride\DC1 via RPC DSA object GUID: a908c575-ddb1-4e89-98e1-97d3e55bf213 Last attempt @ Sun Aug 11 15:40:51 2019 PDT failed, result 8453 (WERR_DS_DRA_ACCESS_DENIED) 6664 consecutive failure(s). Last success @ Sun Aug 11 15:40:51 2019 PDT CN=Configuration,dc=ad,dc=example,dc=com McBride\DC3 via RPC DSA object GUID: 76c41b36-54e8-4e7c-a9ea-4b2e26b0097e...

...d daylight savings time. Assuming my assessment is correct, I have a potential solution to offer. If a time in daylight savings time is rounded such that the rounded value is on the other side of the transition, the isdst element does not get changed accordingly. I have tested only the case of PDT rounded to PST in the US/Pacific time zone. I have tested it on (only) two different platforms, with slightly different results. See below. More specifically, in the US/Pacific time zone the transition from standard to daylight savings time takes place at 02:00 on the first Sunday in April,...

I have Solaris 10 U7 that is exporting ZFS filesytem. The client is Solaris 9 U7. I can mount the filesytem just fine but I am unable to write to it. showmount -e shows my mount is set for everyone. the dfstab file has option rw set. So what gives? Phillip -- This message posted from opensolaris.org

Good Morning! My apologies for what may be considered an infantile question: I have data that I would like to plot, positive integers for the y-axis, and time coordinates of the "Sun Apr 20 22:45:27 PDT 2003" format for the x-axis. I have tried: x1 <- 1050352610 x2 <- 1050352999 x3 <- 1050858319 class(x1) <- "POSIXct" class(x2) <- "POSIXct" class(x3) <- "POSIXct" X <- c(x1, x2, x3) ... ... plot(X, Y, type = "l") I end up with &quo...

>Search took -125.376129 seconds I double checked with a handheld stopwatch, and at no point did the hands spin backwards. Known problem?

...verflow.com/questions/5963269/how-to-make-a-great-r-reproducible-example > > [2] http://adv-r.had.co.nz/Reproducibility.html > > [3] https://cran.r-project.org/web/packages/reprex/index.html > -- > Sent from my phone. Please excuse my brevity. > > On July 10, 2017 8:31:30 AM PDT, Cristina Silva <csilva at ipma.pt> > wrote: >>Hi, >> >>I am extracting positions data from the marine traffic website. The >>table has a "Timestamp" column which, in the browser, appears with >> the >>format yyyy-mm-dd HH:MM (UTC), e.g. 2017...

...uities in the spring or fall. The data comes in a csv file, which I'm reading with myvariable <- read.csv("my_data_file.csv",header=FALSE, col.names=c("timedate","values"),colClasses=c("POSIXct","numeric")) The time zone comes in as PST or PDT, as appropriate. That leads to problems in the spring: > temps$timedate[2185:2190] [1] "2006-04-02 00:00:00 PST" "2006-04-02 01:00:00 PST" [3] NA "2006-04-02 03:00:00 PDT" [5] "2006-04-02 04:00:00 PDT" "2006-04-02 05:00:00 PDT...

...; POSIXct > > as.POSIXct(as.numeric(gsub("(^.{10}).+","", Timestamp)), > origin="1970-01-01") > > as.POSIXct(as.numeric(gsub("(^.{10}).+","\\1", ais$Timestamp)), > origin="1970-01-01") > [1] "2017-07-11 07:09:57 PDT" "2017-07-11 06:45:37 PDT" "2017-07-11 > 06:40:34 PDT" "2017-07-11 06:34:46 PDT" "2017-07-11 06:32:26 PDT" > [6] "2017-07-11 06:29:34 PDT" "2017-07-11 06:26:37 PDT" "2017-07-11 > 06:20:24 PDT" "2017-07-11 06:1...

This will allow us to add some locking for port->* members, in particular the PDT and ->connector, which can't be done from drm_dp_destroy_port() since we don't know what locks the caller might be holding. Changes since v2: * Clarify commit message Cc: Juston Li <juston.li at intel.com> Cc: Imre Deak <imre.deak at intel.com> Cc: Ville Syrjälä <ville.s...

This will allow us to add some locking for port->* members, in particular the PDT and ->connector, which can't be done from drm_dp_destroy_port() since we don't know what locks the caller might be holding. Note that we already do this in delayed_destroy_work (renamed from destroy_connector_work in this patch) for ports, we're just making it so mstbs are also dest...