search for: timstamps

Displaying 9 results from an estimated 9 matches for "timstamps".

Did you mean: timestamps
2009 Jul 19
1
transform(_data,...) using strptime gives an error
...3.4 14.0 25.5 34.6 8 2009/02/27 13:00 25.2 1.1 5.1 15.4 27.3 36.8 9 2009/02/27 14:00 28.6 0.2 8.7 19.4 30.9 40.0 10 2009/02/27 15:00 28.0 0.6 8.0 18.6 30.2 39.3 11 2009/02/27 16:00 28.3 0.9 8.3 18.9 30.5 39.5 The timstamps are character vectors: > str(sd) 'data.frame': 591 obs. of 7 variables: $ Tstamp : chr "2009/02/27 07:00" "2009/02/27 08:00" "2009/02/27 09:00" "2009/02/27 10:00" ... $ Density: num 30.5 32.2 32.7 26.7 26.6 23.3 25.2 28.6 28 28.3 ... $ Mes...
2006 Apr 10
1
RTP Timestamp errors
Hi list, I know * generates it's outgoing RTP stream based on the incomming RTP stream, i'm having some audio problems after i recieve an rtp reinvite from my carrier. Situation: Phone -- Asterisk A --- Asterisk B --- Carrier --- PSTN Asterisk A: reinvite = no Asterisk B: reinvite = no If i dial out on phone via asterisk A, Asterisk B relay's the INVITE to the carrier, after the
2005 Nov 03
8
Wintertime/summertime difference - Samba servers show wrong time ?
When the Central European Time was last switched back to standard, at 03:00 last Sunday, the October 30th, a process died on one of my Windows clients with a mysterious "unknown error". When it was restarted it just went merrily on with its task. Luckily it wasn't part of a life support system. I found out that the immediate cause was how file timestamps were interpreted/presented
2001 Oct 13
2
Samba 2.2.2 released
The Samba Team is proud to announce the release of Samba 2.2.2. This is the latest stable release of Samba. This is the version that all production Samba servers should be running for all current bug-fixes. There are several important oplock logic bugs that have been fixed in this release, so an upgrade is recommended. Binary packages will be released shortly for major platforms. The source
2001 Oct 13
2
Samba 2.2.2 released
The Samba Team is proud to announce the release of Samba 2.2.2. This is the latest stable release of Samba. This is the version that all production Samba servers should be running for all current bug-fixes. There are several important oplock logic bugs that have been fixed in this release, so an upgrade is recommended. Binary packages will be released shortly for major platforms. The source
2002 Feb 03
5
Samba 2.2.3 released
The Samba Team is proud to announce the release of Samba 2.2.3. This is the latest stable release of Samba. This is the version that all production Samba servers should be running for all current bug-fixes. There are several important scaling bugs that have been fixed in this release for large server systems so an upgrade is recommended. Binary packages will be released shortly for major
2002 Feb 03
5
Samba 2.2.3 released
The Samba Team is proud to announce the release of Samba 2.2.3. This is the latest stable release of Samba. This is the version that all production Samba servers should be running for all current bug-fixes. There are several important scaling bugs that have been fixed in this release for large server systems so an upgrade is recommended. Binary packages will be released shortly for major
2003 Dec 01
0
No subject
period of time (hours up to weeks sometimes), and then 'certain' pc's would no longer be able to connect to samba, but other pc's would still be working. And the pc's affected are not the same each time. this might be the case if what is REALLY going on is that the pc's that are STILL working never lost their connection to SAMBA/iX, so they already(still) have a working
2003 Dec 01
0
No subject
To the server from the local disk 7 mins 38 seconds Copying from and two the samba server from nt/win2k clients is okay, I didn't get a chance to get figures for this :/ I saw a post similar to this suggesting that it was a NIC problem and that it was in full duplex mode? Im not sure I could check this on a dos client. any suggestions? We are using a 10mbit dumb hub. The server that is