Either use /etc/inittab, or for more control, put your start / stop script in /etc/init.d, and link your S and K scripts from /etc/rc2.d to the script.
Typically, a basic init.d script will look something like:
Then:
where S99 and K01 are the sequence during a startup / shutdown that your application will be started and stopped in relation to other S and K scripts in rc2.d.
Hi
I have changed my timezone using the command
export TZ='Asia/Calcutta"
but teh affect is taking place only in teh shell where I am logged in. If I export teh variable when I open the new session, things are fine.
Can I affetct the change universally, without restarting the server.
... (2 Replies)
Dear guys,
Pls help me this case. I telnet normally to Solaris. After restarting it manually, I can only console, cannot telnet from my latop although I can ping it. I checked
/etc/default/login
/usr/sbin/in.telnetd
/etc/inet/inetd.conf
All these files are the same.
I don't see telnet... (2 Replies)
Hello people,
My solaris server is rebooting, not sure how!!! Which log should I look in to? I checked /var/adm/messages and dmesg also. How do I check older dmesg logs? I checked lastlog and also ran the last command. Nothing useful pointing to why server rebooted.
Also when server reboots I... (4 Replies)
I'm trying to power on our SUN m4000 server after a recent shutdown. When I try to connect to the xscf console I'm getting prompted for a password. The system is not asking for a login just a password. Below is the output from the xscf console.
Anyone know how I can safely get back to the... (0 Replies)
Hi!
I have useud SMIT to configured my static adress for AIX but when I restart the AIX the ipadress is not shown when I print netstat -in or ifconfig -a.
I have to configure the ip whit smit to have it start!
How can I starting the ip during boot? (6 Replies)
Hi,
please explain that how to find the rootcause of aix servers reboot itself.
Which log or commands should be used to analyse the reboot incident?
Please explain in detail. (3 Replies)
Hi
When I do on console a stop, the script prompts for password
> stop_idm_suite.sh
Suite system password:Here experct of the shell script stop_idm_suite.sh
DoIt()
{
# prompt System password
echo ""
${BMC_JAVA_HOME}/java -Didm.suite.home=${BMC_IDM_SUITE_HOME} -classpath... (1 Reply)
If I want to restart sysedge on a solaris box and it does not want to come up. It gets stucked. How can I check where the sysedge pid file so I can delete it and try to start sysedge again?
What can cause sysedge to not come up?
Thanks, (0 Replies)
Hi All,
My application uses three different sub-services to make complete application up and running to normal.
The entry of all the three services are present in /etc/init.d directory with proper softlink created to application home path where it actually exists.
In one rare case one of the... (3 Replies)
Good afternoon
I need your help please.
There is a Mantenance Windos which needs to Restart de Database Server 192.x.x.97 to set up some configuration
Is it mandatory or not to stop/start Applcation server that runs in 192.x.x.95 ?
Is it mandatory or not to stop/start apache and Tomcat?... (3 Replies)
Discussion started by: alexcol
3 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)