the updates you made to the script displays only one row and i wanted all 50 servers to be displayed.
My changes are not working either:
Errors i am getting:
My suggestion was not a skeleton or pseudocode, I expected it to work as-is and you didn't need to modify it to add extra loops. It already had a loop which read servers from your server file one by one and fed them into ssh individually. Did you try my original, unmodified code?
$server_list is a file, therefore, 'for x in $server_list' makes no sense. You read from files.
I have created a script "myscript.sh"
I need to run this script with diffrent parameters.
The parameters are stored in a file myparam.txt.
I need to run myscript.sh script for every parameter supplied in myparam.txt.
Example:
If myparam.txt contains following lines:
param1
param2
param3... (3 Replies)
I am trying to right a function which uses a file descriptor to write to a log file. The problem is that the on the print statement the file descriptor is called bad. Now when I first open the file and print to it in the f_open function by passing the descriptor to f_print_log all works well,... (6 Replies)
hi
I have a shell script say primary.sh . There is a file called params
my scenario is
primary.sh should read all the values and echo it
for example
i should pass like
$primary.sh params
output would be
Abc
... (2 Replies)
Hi All,
I have written a shell script and the script is working fine, I am passing my MIT_ID(NUMBER VALUE) to the shell script from the command prompt and my script is executing as expected.
Now I have to pass all the MIT_ID's from a .txt file to the shell script,as I am automating this I... (6 Replies)
I have an for loop that reads the following file
cat param.cfg
val1:env1:opt1
val2:env2:opt2
val3:env3:opt3
val4:env4:opt4
.
.
The for loop extracts the each line of the file so that at any one point, the value of i is
val1:env1:opt1 etc...
I would like to extract each... (19 Replies)
Hi
Im trying to run zip shell command from an Oracle job, but this has limitations.
This should take a few of explanaition,..
Oracle allows me to execute a command and then I can set up a fixed number of arguments. Ex: (summarizing in something like..):
JOB DEFINITION
job_name: test... (4 Replies)
Hi ,
I am passing date parameter through file
my shell script testing.sh is
#set -x
#set -v
asd=$1
asd1=$2
echo $asd
echo $asd1
Passing parameter as below
sh testing.sh `cat file1.txt`
Output (2 Replies)
Hello Everyone,
I have developed a shell script which takes schema id and password as parameter to login into database using sqlplus,runs a query and mails the result.
My requirement is that, I dont want to pass userid and password as parameters.Instead,I want to pass say Environment... (4 Replies)
Below is the command
mv AP_FLEXCUBE_INTERFACE10.txt FTPYMNTE_`date "+%Y%m%d%H%M%S" | tr '' ''`.TXT
it is changing the file name to a different name according to time stamp dynamically. I want to capture that dynamic file name present in the directory to a variable .
After that i want to... (6 Replies)
Discussion started by: sujit das
6 Replies
LEARN ABOUT MOJAVE
nns_intro
nns_intro(n) Name service facility nns_intro(n)
__________________________________________________________________________________________________________________________________________________NAME
nns_intro - Name service facility, introduction
DESCRIPTION
nns (short for nano nameservice) is a facility built for the package comm, adding a simple name service to it. It is also built on top of
comm, using it for the exchange of messages between the client and server parts.
This name service facility has nothing to do with the Internet's Domain Name System, otherwise known as DNS. If the reader is looking for a
package dealing with that please see either of the packages dns and resolv, both found in Tcllib too.
Tcllib provides 2 applications and 4 packages which are working together and provide access to the facility at different levels.
APPLICATIONS
The application nnsd provides a simple name server which can be run by anybody anywhere on their system, as they see fit. It is also an
example on the use of the server-side package nameserv::server.
Complementing this server is the nns client application. A possible, but no very sensible use would be to enter name/port bindings into a
server from a shell script. Not sensible, as shell scripts normally do not provide a comm-based service.
The only case for this to make some sense would be in a shell script wrapped around a Tcl script FOO which is using comm, to register the
listening port used by FOO. However even there it would much more sensible to extend FOO to use the nameservice directly. And in regard on
how to that nns can be used as both example and template. Beyond that it may also be useful to perform nameservice queries from shell
scripts.
The third application, nnslog is a stripped down form of the nns client application. It is reduced to perform a continuous search for all
changes and logs all received events to stdout.
Both clients use the nameserv::auto package to automatically hande the loss and restoration of the connection to the server.
PACKAGES
The two main packages implementing the service are nameserv and nameserv::server, i.e. client and server. The latter has not much of an
API, just enough to start, stop, and configure it. See the application nnsd on how to use it.
The basic client, in package nameserv, provides the main API to manipulate and query the service. An example of its use is the application
nns.
The second client package, nameserv::auto is API compatible to the basic client, but provides the additional functionality that it will
automatically restore data like bound names when the connection to the name service was lost and then reestablished. I.e. it automatically
detects the loss of the server and re-enters the data when the server comes back.
The package nameserv::common is of no interest to users. It is an internal package containing code and definitions common to the packages
nameserv and nameserv::server.
All packages use the uevent package for the reporting of special circumstances via events, and reserve the uevent-tag nameserv for their
exclusive use. All their events will be posted to that tag.
INTERNALS
The document Name service facility, client/server protocol specifies the protocol used by the packages nameserv and nameserv::server to
talk to each other. It is of no interest to users of either the packages or applications.
Developers wishing to modify and/or extend or to just understand the internals of the nameservice facility however are strongly advised to
read it.
BUGS, IDEAS, FEEDBACK
This document, will undoubtedly contain bugs and other problems. Please report such in the category nameserv of the Tcllib SF Trackers
[http://sourceforge.net/tracker/?group_id=12883]. Please also report any ideas for enhancements you may have for either package and/or
documentation. Please also report any ideas for enhancements you may have.
SEE ALSO
nameserv(n), nameserv::auto(n), nameserv::common(n), nameserv::protocol(n), nameserv::server(n), nnsd(n), nss(n)
KEYWORDS
client, name service, server
CATEGORY
Networking
COPYRIGHT
Copyright (c) 2008 Andreas Kupries <andreas_kupries@users.sourceforge.net>
nns 1.0 nns_intro(n)