10 More Discussions You Might Find Interesting
1. Linux
Hello friends,
I work on Linux servers via SSH (putty) and run "screen" to preserve my sessions so I can attach/detach them at anytime I wish without losing the connectivity/process disruption which is working perfectly fine.
As my team members also have root access to those servers, it is... (7 Replies)
Discussion started by: prvnrk
7 Replies
2. HP-UX
Hi,
I have this Unix script that kills a user session. When I run it, my screen goes blank. How do I prevent the blank screen?
Ex: I open 2 Unix sessions. The main PID for my 1st session is 1234. In the second session I issue a "kill -HUP 1234". The first session gets killed but the second... (5 Replies)
Discussion started by: rm-r
5 Replies
3. UNIX for Advanced & Expert Users
hello,
i have an AIX 6.1 server which has Informix 11.5 Database Engine. When i want to export some databases from the instance for backup or for any other use i can do it with dbexport (informix command). The problem is that when i run this command or when i run script which run this command,... (2 Replies)
Discussion started by: omonoiatis9
2 Replies
4. Shell Programming and Scripting
hi, i am on AIX 5.3. I would like to write scripts that initiate or reattach to a screen session to run some commands either from unix or Universe. Can anyone assist me with a with a wuick primer on this. I can attach or initiate a screen manually and then run the commands but I would like to... (6 Replies)
Discussion started by: dustytina
6 Replies
5. Shell Programming and Scripting
Im trying to make a script that prints 2 messages to a screen session, one after the other.
screen -x session44 -X stuff "`printf "Test 1\r"`"
This works fine, but adding a second lien with a different message yields no results.
Changed Subject: Please Follow Forum Rules Regarding... (1 Reply)
Discussion started by: kylecn
1 Replies
6. Shell Programming and Scripting
Hello everyone,
Following command sends word 'test' followed by an enter into a screen session (in our case screen_1). How do I print the result, if that would result ? How do I print the result, even if the program running in the session is locked ?
Thank you :)
screen -S screen_1 -X... (5 Replies)
Discussion started by: akula_1986
5 Replies
7. Fedora
Hello sir,
Im in a Fedora 9 system.
Im using screen to invoke the session that is created by me.
Whenever we open the terminal then a session is created by the operating system. I want to know what is the name of default session in screen command.
I could not get it using "screen -ls". Can you... (3 Replies)
Discussion started by: nsharath
3 Replies
8. Solaris
Hi people,
I have a Solstice Backup 6.0.3 installed in server X1 and one installed in server X2.
I need to start de recover in X2 and the somes files existing in X1.
- Well, i begin this process in X2 with
#nwadmin -s X1 &
and i select "Save Set/ Recover". I select the datas and click in... (0 Replies)
Discussion started by: denisgomes
0 Replies
9. Programming
hi ,
Could any one tell me the command for clearing the screen in GDB session (1 Reply)
Discussion started by: useless79
1 Replies
10. Shell Programming and Scripting
Good day. :)
I don't know exactly where or how to post this kind of stuff, but I though I'd like to have a look at my "Screen Saver" in progress. Comments welcome.
This uses bash. Just copy and pase into any file. Make o+x and run. Feel free to edit and change all u like.
Thanks.
... (0 Replies)
Discussion started by: Blooper
0 Replies
NSDC(8) NSDC 3.2.12 NSDC(8)
NAME
nsdc - Name Server Daemon (NSD) control script.
SYNOPSIS
nsdc [-c configfile] start | stop | reload | rebuild | restart | running | update | notify | patch
DESCRIPTION
Nsdc is the shell script that used to control nsd(8) and zonec(8) from NSD distribution. Nsdc is also suitable to be linked into /etc/rc.d
directory on BSD like systems for automatic startup of nsd(8) at boot time.
At every invokation, nsdc will try to read the nsd.conf(5) configuration file. An example of such configuration file is distributed with
the NSD package as nsd.conf.sample. The config file is checked for errors before it is used, see nsd-checkconf(8).
Possible nsdc applications are:
start Start nsd(8).
stop Shut down nsd(8) by sending SIGTERM to it.
reload Initiate nsd(8) name space database reload by sending SIGHUP.
rebuild
Rebuild the nsd(8) database by invoking zonec(8) with appropriate arguments.
restart
Restart nsd(8). This equals to nsdc stop && nsdc start.
running
Check whether nsd(8) is running. Returns error message and error code if it is not running, and no message and zero error code oth-
erwise.
update Updates all the slave zones which have allow-notify: from localhost (127.0.0.1 or ::1) allowed. If a TSIG key is specified for the
allow-notify statement in the config file, it will be used to secure the notify. Note that NSD keeps track of zone timeouts automat-
ically, this is only needed if you want to manually force updates by sending notify messages to the localhost.
Another method you can use is to stop nsd, delete the xfrd.state file and then start nsd again. It will try to update all zones.
This method does not require allow-notify: statements.
notify Sends notify messages to all the slaves for all the zones that have the notify: keyword in the nsd.conf file. If a TSIG key is spec-
ified for a notify statement, it will be used to secure the notification message to that slave server.
patch Merge zone transfer changes back to zone files. It reads in the nsd database (nsd.db) and difffile (ixfr.db), and overwrites the
zone text files if they have been updated. Running this regularly ensures that the difffile does not grow infinitely. If any zone
text files have been changed (including those of the master zones), the nsd.db is rebuild and nsd is reloaded.
OPTIONS
-c configfile
Specify configfile to use instead of the default /etc/nsd3/nsd.conf.
FILES
/etc/nsd3/nsd.conf
Configuration file for nsd to change default pathnames and NSD flags. The zone names, pathnames to zone files and access control
lists are also in nsd.conf(5).
/var/lib/nsd3/nsd.db
default NSD database
/var/lib/nsd3/nsd.db.lock
Lockfile for the NSD database access by operator tools.
/var/lib/nsd3/ixfr.db
Journal of zone transfers, the diff file containing the new zone contents transferred.
/var/lib/nsd3/xfrd.state
State for the zone transfer process of NSD. Contains timeouts for the zones and whether zones are expired.
/var/run/nsd3/nsd.pid
the process id of the name server.
DIAGNOSTICS
Nsdc will return zero return code if operation was successful and an error message to standard output plus a non-zero return code other-
wise.
SEE ALSO
nsd(8), nsd.conf(5), nsd-checkconf(8), nsd-notify(8), nsd-patch(8), nsd-xfer(8), zonec(8)
AUTHORS
NSD was written by NLnet Labs and RIPE NCC joint team. Please see CREDITS file in the distribution for further details.
BUGS
Syntax checking of the config file is rudimentary and error messages may be wrong. If you do a nsdc patch, whilst a (long) zone transfer is
busy, the zone transfer contents will be partially lost. After a reload, this will be detected and the zone transfer should be restarted.
The reload that happens at the end of nsdc patch also frees up memory churn in NSD caused by zone transfers.
NLnet Labs jul 19, 2012 NSDC(8)