similar to: internet connection tester script

Hi. I have the following code in a loop. It splits a vector into subvectors of equal size. But if the size of the original vector is not an exact multiple of the desired subvector size, then the first few subvectors have one more element than the last few. I know that the cut function could be used to determine where to break up the vector, but it doesn't seem to provide control over

Anyone using it? http://beta.eset.com/linux What are the experiences? Does it slows down the pc? Do we need it? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20110123/4831dc0b/attachment-0002.html>

Hi, M new with samba i just installed sambav3 and configure the sam.conf file to join a windows domain(win 2000). when i use net rpc bind to join this solaris bix it says joind the domain. but m not able to ping the solaris box from windows machine as well as the reverse. could you please suggest me if i need to do some other configuration.. Thanks in advance Regards Sids

"to memory" means: mounting a ~2 GByte filesystem [ tmpfs?, or ramfs? ], and put the "/tmp" on it. [ e.g.: 4 GByte ram in the pc ]. what to write in the "/etc/fstab"? I would like to collect the [ answers too:P ]: Advantages: - Memory is way faster then HDD/SSD, so it could speed things up - "SSD amortization" is less Disadvantages: - Security?

https://www.psc.edu/networking/projects/hpn-ssh/hpn-v-ssh-tput.jpg "SCP and the underlying SSH2 protocol implementation in OpenSSH is network performance limited by statically defined internal flow control buffers. These buffers often end up acting as a bottleneck for network throughput of SCP, especially on long and high bandwith network links. Modifying the ssh code to allow the buffers

Just starting to do the research on this one....I've got a customer who is showing interest in replacing any older Panasonic unit providing service to 96 tip/ring lines from a single PRI. Does anyone have any recent experience with a decent (as in, plays nice with * and has a reasonable per-port cost) channel bank or similar? Mediatrix only goes up to 24 port, as far as I can tell, which

How to disable autorun? Are there any hidden autorun features on a standard CentOS install?? http://securitytube.net/USB-Autorun-attacks-against-Linux-at-Shmoocon-2011-video.aspx -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20110207/c3f7644f/attachment-0001.html>

I am hoping to replace my Nortel 8x24 switch with Asterisk. Right now my cabling comes from my outside phone box into my office and into a punchdown block and leaves the punchdown block as an amphenol connector which currently plugs into the Nortel swicth. A second amphenol connector them plugs into the switch and extends to another punchdown block that I believe carries the lines throughout the

Say I get an ADIT 600 with two FXS8A and one FXO8A from ebay. a. Is it good for Asterisk? b. How do I connect the extensions and lines to it? Do I need a special jack? Can I get that jack in every corner? c. where can I find help for configuring it? d. what kind of backup does it have? Does it need to be reconfigured after a power outage? Shoval Tomer, IT Manager, SofTov Advanced Systems, Ltd.

http://i.imgur.com/rUKeu.png how could i configure the GNOME-panel to have several columns [if there are many applications]? ~~like this: http://i.imgur.com/ElgAA.jpg Thank you! -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20110203/14e5ab1a/attachment-0001.html>

The situation is that I want to have certain extensions that can only call nationwide and others that can make international calls (with a different provider). I suppose, you could also see this as a scenario that could involve multiple internal extensions that get matched to specific outbound trunks. I have tried to find appropriate commands in the Asterisk documentation, but could find nothing

More prep work for immutable biovecs - with immutable bvecs drivers won't be able to use the biovec directly, they'll need to use helpers that take into account bio->bi_iter.bi_bvec_done. This updates callers for the new usage without changing the implementation yet. Signed-off-by: Kent Overstreet <koverstreet at google.com> Cc: Jens Axboe <axboe at kernel.dk> Cc: Geert

More prep work for immutable biovecs - with immutable bvecs drivers won't be able to use the biovec directly, they'll need to use helpers that take into account bio->bi_iter.bi_bvec_done. This updates callers for the new usage without changing the implementation yet. Signed-off-by: Kent Overstreet <koverstreet at google.com> Cc: Jens Axboe <axboe at kernel.dk> Cc: Geert

More prep work for immutable biovecs - with immutable bvecs drivers won't be able to use the biovec directly, they'll need to use helpers that take into account bio->bi_iter.bi_bvec_done. This updates callers for the new usage without changing the implementation yet. Signed-off-by: Kent Overstreet <kmo at daterainc.com> Cc: Jens Axboe <axboe at kernel.dk> Cc: Geert

More prep work for immutable biovecs - with immutable bvecs drivers won't be able to use the biovec directly, they'll need to use helpers that take into account bio->bi_iter.bi_bvec_done. This updates callers for the new usage without changing the implementation yet. Signed-off-by: Kent Overstreet <kmo at daterainc.com> Cc: Jens Axboe <axboe at kernel.dk> Cc: Geert

More prep work for immutable biovecs - with immutable bvecs drivers won't be able to use the biovec directly, they'll need to use helpers that take into account bio->bi_iter.bi_bvec_done. This updates callers for the new usage without changing the implementation yet. Signed-off-by: Kent Overstreet <kmo at daterainc.com> Cc: Jens Axboe <axboe at kernel.dk> Cc: Geert

More prep work for immutable biovecs - with immutable bvecs drivers won't be able to use the biovec directly, they'll need to use helpers that take into account bio->bi_iter.bi_bvec_done. This updates callers for the new usage without changing the implementation yet. Signed-off-by: Kent Overstreet <kmo at daterainc.com> Cc: Jens Axboe <axboe at kernel.dk> Cc: Geert

More prep work for immutable biovecs - with immutable bvecs drivers won't be able to use the biovec directly, they'll need to use helpers that take into account bio->bi_iter.bi_bvec_done. This updates callers for the new usage without changing the implementation yet. Signed-off-by: Kent Overstreet <kmo at daterainc.com> Cc: Jens Axboe <axboe at kernel.dk> Cc: Geert

More prep work for immutable biovecs - with immutable bvecs drivers won't be able to use the biovec directly, they'll need to use helpers that take into account bio->bi_iter.bi_bvec_done. This updates callers for the new usage without changing the implementation yet. Signed-off-by: Kent Overstreet <kmo at daterainc.com> Cc: Jens Axboe <axboe at kernel.dk> Cc: Geert

More prep work for immutable biovecs - with immutable bvecs drivers won't be able to use the biovec directly, they'll need to use helpers that take into account bio->bi_iter.bi_bvec_done. This updates callers for the new usage without changing the implementation yet. Signed-off-by: Kent Overstreet <koverstreet at google.com> Cc: Jens Axboe <axboe at kernel.dk> Cc: Geert