Sponsored Content
Full Discussion: Fun with FreeBSD
Special Forums News, Links, Events and Announcements Fun with FreeBSD Post 15967 by killerserv on Friday 22nd of February 2002 06:30:26 AM
Old 02-22-2002
MySQL Fun with FreeBSD

Fun With Automounting on FreeBSD

Link: Nice tips for FreeBSD Unix.

http://ezine.daemonnews.org/200202/automounting.html
 

7 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

fun with tar

ok, i've figured out my problem with distributed, in Solaris GUI if you click on a tar file it will untar it for you, using paramiters I don't know. now, I've got a tar file in / called dnetc-solaris26-x86.tar i want to install it to the "/Veitch" directory how exactly do I use the tar... (17 Replies)
Discussion started by: veitcha
17 Replies

2. UNIX for Advanced & Expert Users

like to have fun in terminal

Hai Friends I have installed FreeBSD in my system... I have installed it to work in text mode don't have the GUI. The default text color is Black background with White Foreground. I want it to be with Black background with Green Foreground. How could i do that. Thanks in advance Collins (4 Replies)
Discussion started by: collins
4 Replies

3. Programming

Application crashes in FreeBSD 7.1 while working ok in FreeBSD 6.3

Hello there, My mulithreaded application (which is too large to represent the source code here) is crashing after installing FreeBSD 7.1-RELEASE/amd64. It worked properly on others machines (Dual Cores with 4GB of RAM - FreeBSD 6.2-RELEASE/i386). The current machine has 2x Core 2 Duo... (1 Reply)
Discussion started by: Seenquev
1 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. War Stories

Following Cables for Fun!

Hi Folks, I came accross this picture taken a number of years ago now, I just thought I'd share it with you guys. We were in the process of removing equipment from the Data Centre and had followed the cable through to this area, where one of the old patch areas had been. When we lifted the... (2 Replies)
Discussion started by: gull04
2 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:56 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy