search for: msecs

Full_Name: John Brzustowski Version: R-devel-trunk, R-2.4.0 OS: linux, gcc 4.0.3 Submission from: (NULL) (206.248.157.184) This isn't a bug, but an easily-remedied performance issue. SYMPTOM > for (i in 1000 * (1:20)) { y <- paste(rep("asdf", times=i), collapse=" ") t <- system.time(strsplit(y, " ", fixed=TRUE)) cat(sprintf("i=%5d

I just finished compiling openssh-2.1.0p3 on a SCO openserver system. I generated the keys fine and genereated the host keys both rsa and dsa without problems. ssh (version1) works great. I tried to use ssh (version 2) and after being prompted to login, it quits. I am attaching a script file of... ssh -v -2 root at sco to see if you can find the problem. Let me know how I can help. [root at

Hi, I am using Van Dyke SecureCRT 3.2.1 to access an AIX server running OpenSSH-2.5.0p1. Using ssh1 with X11 forwarding enabled, the server reports the following error (in the client session): Packet integrity error. (34) This problem was not evident in 2.3.0p1. Running sshd in debug gives the output: debug1: sshd version OpenSSH_2.5.1p1 debug1: load_private_key_autodetect: type 0 RSA1

>Dear Speex developers >I am going to port Speex on LPC2368 >I tested Speex encoding and the mesurments shows ~40ms cpu time for one >frame >Do you know who ported speex to NXP or other 32bit platform? >Best Regards >Zohar fox I have an own optimisation for Speex for different versions of ARM architecture. Here is Measurements of performance for STM32 72 MHz. 4000

Hi Ben, here is the output from sshd -d -d -d: mvs2:sygm:/usr/local/sbin:#./sshd -d -d -d debug3: Reading output from 'ls -alni /var/log' debug3: Time elapsed: 459 msec debug2: Command 'ls -alni /var/log' timed out debug3: Got 0.00 bytes of entropy from 'ls -alni /var/log' debug3: Reading output from 'ls -alni /var/adm' debug3: Time elapsed: 143 msec debug2:

...ut *timeout) +{ + SwfdecAsValue ret; + SwfdecInterval *interval = SWFDEC_INTERVAL (((guchar *) timeout) + - G_STRUCT_OFFSET (SwfdecInterval, timeout)); + SwfdecAsContext *context = SWFDEC_AS_OBJECT (interval)->context; + + if (interval->repeat) { + timeout->timestamp += SWFDEC_MSECS_TO_TICKS (interval->msecs); + swfdec_player_add_timeout (SWFDEC_PLAYER (context), timeout); + } else { + interval->timeout.callback = NULL; + } + if (interval->fun_name) { + swfdec_as_object_call (interval->object, interval->fun_name, + interval->n_args, interval->...

Hi Ben, I test the command sshd -d -d -d several times and mostly the sshd-Daemon not started and sometimes the sshd-Daemon started, with the message: debug1: Seeded RNG with 16 bytes from programs debug1: Seeded RNG with 3 bytes from system calls debug1: sshd version OpenSSH_2.9p1 debug1: private host key: #0 type 0 RSA1 debug1: Bind to port 22 on 0.0.0.0. Server listening on 0.0.0.0 port 22.

...92.168.101.102 Supported: path, gruu Expires: 3600 Content-Length: 0 - - - [ Status > Log ] [0] 24/12/2001 00:00:27: Phone::uboot_version:1.1.3-u [1] 24/12/2001 00:00:29: Conf setup: code: 500, host: 127.0.0.1:80, file: /dummy.htm [0] 24/12/2001 08:00:31: TaskMon: LCS 21/0 recv LPCP took 1271 msecs [0] 24/12/2001 08:00:31: LoopMon: LCS 21 took 1271 (290/0) msecs, read 1, 3/1 tasks [1] 24/12/2001 08:00:32: TLS: Warning: Certificate with subject Country: ; State: ; Locality ; Organization: ; Common Name: pbx.domain.com; eMail: has expired according to the local time of the phone. [0] 24/12/2001...

...+{ + SwfdecNetStream *stream; + + if (SWFDEC_AS_OBJECT_CLASS (swfdec_net_stream_parent_class)->get (object, variable, val, flags)) + return TRUE; + + stream = SWFDEC_NET_STREAM (object); + /* FIXME: need case insensitive comparisons? */ + if (variable == SWFDEC_AS_STR_time) { + guint msecs; + if (stream->flvdecoder == NULL || + !swfdec_flv_decoder_get_video_info (stream->flvdecoder, &msecs, NULL)) { + SWFDEC_AS_VALUE_SET_INT (val, 0); + } else { + if (msecs >= stream->current_time) + msecs = 0; + else + msecs = stream->current_time - msecs; +...

Here's the appropriate output with blow-by-blow explanation embedded... I start by making a connection with X11 forwarding enabled: polycut:~> ssh -v -v -v -X dazel OpenSSH_2.9.9p2, SSH protocols 1.5/2.0, OpenSSL 0x0090602f debug1: Reading configuration data /opt/openssh-2.9.9p2/etc/ssh_config debug3: Reading output from 'ls -alni /var/log' debug3: Time elapsed: 23 msec debug3:

Hi folks, The following are initial virtio-scsi + target vhost benchmark results using multiple target LUNs per vhost and multiple virtio PCI adapters to scale the total number of virtio-scsi LUNs into a single KVM guest. The test setup is currently using 4x SCSI LUNs per vhost WWPN, with 8x virtio PCI adapters for a total of 32x 500MB ramdisk LUNs into a single guest, along with each backend

Hi folks, The following are initial virtio-scsi + target vhost benchmark results using multiple target LUNs per vhost and multiple virtio PCI adapters to scale the total number of virtio-scsi LUNs into a single KVM guest. The test setup is currently using 4x SCSI LUNs per vhost WWPN, with 8x virtio PCI adapters for a total of 32x 500MB ramdisk LUNs into a single guest, along with each backend

When I run a remote xterm, the ssh hangs even after I quit the xterm. Below is the output for the following sequence: client> ssh -v -v -v dazel xterm xterm> exit client> ^C The outcome is always the same - the ssh doesn't exit with I quit the xterm... I have to hit CTRL-C on the client side. polycut:~> ssh -v -v -v dazel xterm OpenSSH_2.9p2, SSH protocols 1.5/2.0, OpenSSL

What I've done so far: Studied man samba Connected to my parents XP box on my LAN (two different connections, even). root@omega-fleet root]# smbclient -L 64.131.112.121 added interface ip=192.168.1.11 bcast=192.168.1.255 nmask=255.255.255.0 added interface ip=192.168.1.10 bcast=192.168.1.255 nmask=255.255.255.0 session request to some.ip failed (Called name not present) session request to

...bian distro to build the latest (via git). That has been 'uneventful' - which is good, but I am confused by the output of "make check". An excerpt: test_program_setup ................................................... : ok Debug: Trying to connect 127.0.0.1:52694 (timeout 5000 msecs) test_program_success ................................................. : ok Debug: Trying to connect 127.0.0.1:52694 (timeout 5000 msecs) test_program_io (async) .............................................. : ok Debug: Trying to connect 127.0.0.1:52694 (timeout 5000 msecs) test_program_failure ....

...(via git). > > That has been 'uneventful' - which is good, but I am confused by the > output of "make check". An excerpt: > > test_program_setup ................................................... > : ok > Debug: Trying to connect 127.0.0.1:52694 (timeout 5000 msecs) > test_program_success ................................................. > : ok > Debug: Trying to connect 127.0.0.1:52694 (timeout 5000 msecs) > test_program_io (async) .............................................. > : ok > Debug: Trying to connect 127.0.0.1:52694 (timeout 5000...

At the most recent Xen Summit, Thomas Friebel presented a paper ("Preventing Guests from Spinning Around", http://xen.org/files/xensummitboston08/LHP.pdf) investigating the interactions between spinlocks and virtual machines. Specifically, he looked at what happens when a lock-holding VCPU gets involuntarily preempted. The obvious first order effect is that while the VCPU is not

At the most recent Xen Summit, Thomas Friebel presented a paper ("Preventing Guests from Spinning Around", http://xen.org/files/xensummitboston08/LHP.pdf) investigating the interactions between spinlocks and virtual machines. Specifically, he looked at what happens when a lock-holding VCPU gets involuntarily preempted. The obvious first order effect is that while the VCPU is not

At the most recent Xen Summit, Thomas Friebel presented a paper ("Preventing Guests from Spinning Around", http://xen.org/files/xensummitboston08/LHP.pdf) investigating the interactions between spinlocks and virtual machines. Specifically, he looked at what happens when a lock-holding VCPU gets involuntarily preempted. The obvious first order effect is that while the VCPU is not

Good day. Asterisk 13.7.2, res_pjsip. There is a problem of loss of registration of several devices. This happens not on all devices, but problem devices a lot. Below is the log of registration of a contact of one device. Is suspect two things: 1. delete a contact after the contact is added. But, like, it's a feature of code that may already be fixed. 2. deleting a contact much earlier