10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi,
I have a months worth of data that I need to separate into weekly files. There is a date column with dates in the following format: YYYYMMDD.
I'm thinking I can create the weekly files by using a grep command combined with an IF command and specify each day of the specific week I'm... (1 Reply)
Discussion started by: cwl
1 Replies
2. Shell Programming and Scripting
Please have a look at below examples. Why do these 3 sed commands deliver the same result? Especially, why are there 4 "x" in the result instead of 3?
1.
echo "abc" | sed 's/d*/x/g'
xaxbxcx
2.
echo "abc" | sed 's/d*/&x/g'
xaxbxcx
3.
echo "abc" | sed 's/d*/x&/g'
xaxbxcx
Thanks for... (2 Replies)
Discussion started by: Werner Gross
2 Replies
3. Solaris
greetings,
I am new to solaris, have a basic question.
I have to check for patch 137111-04 (as prerequisite) for installing Oracle.
# patchadd -p | grep 137111-04
# patchadd -p | grep 137111
Patch: 137137-09 Obsoletes: 120741-01 120986-12 120992-02 121008-02 121274-01 121414-01... (2 Replies)
Discussion started by: mubeenmd
2 Replies
4. Shell Programming and Scripting
sorry for being dumb here, but is there a way my for loop can take an entire line of a file into consideration instead of each word in a line... ill explain
if i have a file like this
# cat list
serial: 23124
hostname: server1
and a script that does this
# cat list.sh
#!/bin/sh
... (6 Replies)
Discussion started by: hcclnoodles
6 Replies
5. Shell Programming and Scripting
hi,
I have a basic question,,
i am in a directory called
/intas/OCU_3.9.1/sbin
ocuut1@france>mv itsa_tcs itsa_tcs_old
mv: itsa_tcs_old: rename: Permission denied
i am logging as the owner of the file.
when i am doing this i am getting the above error of permission denied.
I know... (3 Replies)
Discussion started by: namishtiwari
3 Replies
6. HP-UX
Could someone tell me the command to find out the OS version which will give 12 character not the 9 characters(which is usually machine id).
uname -i gives machine id and uname -a is more comprehensive way to look.
Thanks! (4 Replies)
Discussion started by: catwomen
4 Replies
7. UNIX for Dummies Questions & Answers
Hello all. Let me start off by saying I know a little more then it seems by me asking this question... here goes
I have an old 486 box and I want to start messing around with unix. I've been taking classes for 3 or 4 years in c programming in unix, so I am used to the commands and such, but I... (1 Reply)
Discussion started by: robherms
1 Replies
8. UNIX for Dummies Questions & Answers
How to know if my AIX 5.2 is running at 64bits?
THANKS (5 Replies)
Discussion started by: GermanSkull
5 Replies
9. UNIX for Dummies Questions & Answers
hey...when i type who...what does "pts" field mean???
eg pts 0 etc (1 Reply)
Discussion started by: urwannabefriend
1 Replies
10. UNIX for Dummies Questions & Answers
I have some basic doubts. Can someone clarify in this forum?
1)if
then
eval ' tset -s -Q -m ':?hp' '
else
eval ' tset -s -Q '
what does it exactly mean in .profile?
2) what are 'nobody' and 'noaccess' usernames in /etc/passwd file.
... (3 Replies)
Discussion started by: asutoshch
3 Replies
nns_intro(3tcl) Name service facility nns_intro(3tcl)
__________________________________________________________________________________________________________________________________________________
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(3tcl), nameserv::auto(3tcl), nameserv::common(3tcl), nameserv::protocol(3tcl), nameserv::server(3tcl), nnsd(3tcl), nss(3tcl)
KEYWORDS
client, name service, server
CATEGORY
Networking
COPYRIGHT
Copyright (c) 2008 Andreas Kupries <andreas_kupries@users.sourceforge.net>
nns 1.0 nns_intro(3tcl)