Sponsored Content
Full Discussion: Following Cables for Fun!
The Lounge War Stories Following Cables for Fun! Post 302883655 by rbatte1 on Wednesday 15th of January 2014 12:52:58 PM
Old 01-15-2014
Looks familiar to me....... Smilie
 

9 More Discussions You Might Find Interesting

1. Solaris

Scsi cables - which ones?

Is there any specific scsi cables that you need to get when connecting a tape drive or external storage or does one type of cable fit all? ie. I can buy the following: HD68 to HD68 with Ferrites supports S-E Ultra/Wide transfer rates. But will this work for tape drives and storage? I... (1 Reply)
Discussion started by: frustrated1
1 Replies

2. IP Networking

fc cables

hi friends, we are using fc cables and fc switches,u might be aware of the cost factor of it so just wanted to know that Why do we need FC switches and fiber-optic cables? Is it not possible to use, say, twisted-pair copper cables instead of fiber-optic cables, and achieve almost comparable... (3 Replies)
Discussion started by: mxms755
3 Replies

3. Solaris

1 or 2 Fiber cables?

Hi Community, I'm working on Solaris 10 installation with 1 Server V490 and 1 StoredgeTek 3510 (Standalone configuration). I'd connect the Server to the Storedge with a fiber cable but I' m in doubt becouse I don't know if using 1 or 2 fiber cable. Could you provide me any solution? ... (2 Replies)
Discussion started by: Sunb3
2 Replies

4. What is on Your Mind?

fun scripts

Lets get a list of everyones funny scripts (8 Replies)
Discussion started by: JamieMurry
8 Replies

5. Shell Programming and Scripting

Fun with awk

uggc://ra.jvxvcrqvn.bet/jvxv/EBG13 #!/usr/bin/awk -f BEGIN { for (n=0;n<26;n++) { x=sprintf("%c",n+65); y=sprintf("%c",(n+13)%26+65) r=y; r=tolower(y) } } { b = "" for (n=1; x=substr($0,n,1); n++) b = b ((y=r)?y:x) print b } ... (0 Replies)
Discussion started by: colemar
0 Replies

6. Shell Programming and Scripting

More fun with awk

#!/usr/bin/ksh ls -l $@ | awk ' /^-/ { l = 5*log($5) h = sprintf("%7d %-72s",$5,$8) print "\x1B ls command with histogram of file sizes. The histogram scale is logaritmic, to avoid very short bars for smaller files or very long bars for bigger files. Screenshot: (4 Replies)
Discussion started by: colemar
4 Replies

7. Solaris

SUNFIRE V240 procedure to shutdown with safety in order to replace power cables

Question: Which commands to use to shutdown with safety the server; (2 Replies)
Discussion started by: doudou2012
2 Replies

8. Hardware

Flat cables vs normal circular cables

Do flat cables have any advantage over normal circular cables? I was looking at this. 6ft 2M Flat USB Sync Data Cable Charger Cord for iPhone4 4S 3G iPad1 2 3 Orange | eBay (2 Replies)
Discussion started by: cokedude
2 Replies

9. IP Networking

What RJ11 Cables Should I Use?

Hello All, I have a project I'm working on which involves a linux PC and a USB (*dialup) Modem in a remote location for telnet'ing to that PC by phone when the Ethernet connection is down. I have already purchased the USB modems I need and some dumb phones for line testing... Now I'm trying... (7 Replies)
Discussion started by: mrm5102
7 Replies
ct_rpc(3erl)						     Erlang Module Definition						      ct_rpc(3erl)

NAME
ct_rpc - Common Test specific layer on Erlang/OTP rpc. DESCRIPTION
Common Test specific layer on Erlang/OTP rpc. EXPORTS
app_node(App, Candidates) -> NodeName Types App = atom() Candidates = [NodeName] NodeName = atom() From a set of candidate nodes determines which of them is running the application App. If none of the candidate nodes is running the application the function will make the test case calling this function fail. This function is the same as calling app_node(App, Can- didates, true) . app_node(App, Candidates, FailOnBadRPC) -> NodeName Types App = atom() Candidates = [NodeName] NodeName = atom() FailOnBadRPC = true | false Same as app_node/2 only the FailOnBadRPC argument will determine if the search for a candidate node should stop or not if badrpc is received at some point. app_node(App, Candidates, FailOnBadRPC, Cookie) -> NodeName Types App = atom() Candidates = [NodeName] NodeName = atom() FailOnBadRPC = true | false Cookie = atom() Same as app_node/2 only the FailOnBadRPC argument will determine if the search for a candidate node should stop or not if badrpc is received at some point. The cookie on the client node will be set to Cookie for this rpc operation (use to match the server node cookie). call(Node, Module, Function, Args) -> term() | {badrpc, Reason} Same as call(Node, Module, Function, Args, infinity) call(Node, Module, Function, Args, TimeOut) -> term() | {badrpc, Reason} Types Node = NodeName | {Fun, FunArgs} Fun = function() FunArgs = term() NodeName = atom() Module = atom() Function = atom() Args = [term()] Reason = timeout | term() Evaluates apply(Module, Function, Args) on the node Node. Returns whatever Function returns or {badrpc, Reason} if the remote proce- dure call fails. If Node is {Fun, FunArgs} applying Fun to FunArgs should return a node name. call(Node, Module, Function, Args, TimeOut, Cookie) -> term() | {badrpc, Reason} Types Node = NodeName | {Fun, FunArgs} Fun = function() FunArgs = term() NodeName = atom() Module = atom() Function = atom() Args = [term()] Reason = timeout | term() Cookie = atom() Evaluates apply(Module, Function, Args) on the node Node. Returns whatever Function returns or {badrpc, Reason} if the remote proce- dure call fails. If Node is {Fun, FunArgs} applying Fun to FunArgs should return a node name. The cookie on the client node will be set to Cookie for this rpc operation (use to match the server node cookie). cast(Node, Module, Function, Args) -> ok Types Node = NodeName | {Fun, FunArgs} Fun = function() FunArgs = term() NodeName = atom() Module = atom() Function = atom() Args = [term()] Reason = timeout | term() Evaluates apply(Module, Function, Args) on the node Node. No response is delivered and the process which makes the call is not sus- pended until the evaluation is compleated as in the case of call/[3,4]. If Node is {Fun, FunArgs} applying Fun to FunArgs should return a node name. cast(Node, Module, Function, Args, Cookie) -> ok Types Node = NodeName | {Fun, FunArgs} Fun = function() FunArgs = term() NodeName = atom() Module = atom() Function = atom() Args = [term()] Reason = timeout | term() Cookie = atom() Evaluates apply(Module, Function, Args) on the node Node. No response is delivered and the process which makes the call is not sus- pended until the evaluation is compleated as in the case of call/[3,4]. If Node is {Fun, FunArgs} applying Fun to FunArgs should return a node name. The cookie on the client node will be set to Cookie for this rpc operation (use to match the server node cookie). AUTHORS
<> common_test 1.5.3 ct_rpc(3erl)
All times are GMT -4. The time now is 05:02 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy