10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi,
I am having a little trouble getting notify-send to work the way I would like it to.
I am using ubuntu - karmic koala 2.6.31-19-generic #56-Ubuntu SMP
So here's the problem
run the following commands one after the other.
notify-send -i info -t 100000 -- "Hi" "world" &
notify-send -i... (3 Replies)
Discussion started by: linuxpenguin
3 Replies
2. Solaris
How can we make rdist to work over ssh? By default rdist works with rsh protocol which is now the host server is refuses to accept the rsh connection. How to find rdist version which I am running? How to upgrade it to latest version?
Working environment is solaris 9 and solaris 10. (1 Reply)
Discussion started by: naveenjami
1 Replies
3. UNIX for Dummies Questions & Answers
I need to rdist some files from unix to window XP, where the source file is in Unix box. I can't get a way to do it as it always prompted me permission denied.
rdist -c migtest.tar <ipaddr>:/filedir/migtest.tar
updating host <ipaddr>
Permission denied.
I'd tried to ftp and put the file... (0 Replies)
Discussion started by: lenniegu
0 Replies
4. HP-UX
Hello,
I am looking for either the rdist binaries or code for HPUX 11.11.
Thanks (1 Reply)
Discussion started by: rfisher001
1 Replies
5. HP-UX
Can any body please tell me the return codes of RDIST tool?
I am using RDIST (through an UNIX script) to synchronize files between two servers say ukblx151(source) & ukapx050(target).
RDIST raises an alert mail (through notify option) in case of success & also failure but there is a problem if... (0 Replies)
Discussion started by: vishal_ranjan
0 Replies
6. Shell Programming and Scripting
Hi,
Earlier i am posting some files using rdist.
rdist -h -f <file-name>
File-name is file which contains details of servername,host,source & destination.
Now server has changed and it is giving connection refused error.What i have to do.
error is:
updating <servername>... (7 Replies)
Discussion started by: Mar1006
7 Replies
7. UNIX for Dummies Questions & Answers
I have a .rdist & .sh files.
shell script contains code like this
rdist -h -f <rdist file>
when this script executed i am getting the following error.
rdist:<full path of files>: Permission denied.
I verified the folder on the other system by connecting FTP.It doesn't has write... (0 Replies)
Discussion started by: Mar1006
0 Replies
8. UNIX for Advanced & Expert Users
I am trying to synchronize to boxes running True64 Unix one as a live backup of the other for user directories.
When running rdist, I receive the message "Permission Denied" when each directory is accessed with the sole exception of my own directory.
This has to be an automated process which... (1 Reply)
Discussion started by: doug_hutch
1 Replies
9. UNIX for Advanced & Expert Users
How do I rdist a directory from one server to another, excluding soft and hard links?
current rdist syntax:
1 2 * * * cd /apps/oasis/prdsch/log; rdist -c j1*.log oasis@oastdby:/apps/schiller/oasis/prdsch/log
31 2 * * * cd /apps/oasis/prdsch/log; rdist -c oasis_bin_trans*.log... (6 Replies)
Discussion started by: captainzeb
6 Replies
10. UNIX for Advanced & Expert Users
Does anyone know of any known bugs/issues with the RDIST utility on HP unix?
I am trying to set up replication between two servers. All seems to work okay to start with, but the rdist program always terminates with a value of 1 - i.e. signifying an error. However - no error message or even warning... (1 Reply)
Discussion started by: man_with_no_nam
1 Replies
sm-notify(8) System Manager's Manual sm-notify(8)
NAME
sm-notify - Send out NSM reboot notifications
SYNOPSIS
/sbin/sm-notify [-dfq] [-m time] [-p port] [-P path] [-v my_name ]
DESCRIPTION
File locking over NFS (v2 and v3) requires a facility to notify peers in case of a reboot, so that clients can reclaim locks after a server
crash, and/or servers can release locks held by the rebooted client.
This is a two-step process: during normal operations, a mechanism is required to keep track of which hosts need to be informed of a reboot.
And of course, notifications need to be sent out during reboot. The protocol used for this is called NSM, for Network Status Monitor.
This implementation separates these into separate program. rpc.statd tracks hosts which need to be notified and this sm-notify performs
the notification. When rpc.statd is started it will typically started sm-notify but this is configurable.
Operation
For each NFS client or server machine to be monitored, rpc.statd creates a file in /var/lib/nfs/sm, and removes the file if monitoring is
no longer required.
When the machine is rebooted, sm-notify iterates through these files and notifies the peer statd server on those machines.
Each machine has an NSM state , which is basically an integer counter that is incremented each time the machine reboots. This counter is
stored in /var/lib/nfs/state, and updated by sm-notify.
Security
sm-notify has little need for root privileges and so drops them as soon as possible. It continues to need to make changes to the sm and
sm.bak directories so to be able to drop privileges, these must be writable by a non-privileged user. If these directories are owned by a
non-root user, sm-notify will drop privilege to match that user once it has created sockets for sending out request (for which it needs
privileged) but before it processes any reply (which is the most likely source of possible privilege abuse).
OPTIONS
-m failtime
When notifying hosts, sm-notify will try to contact each host for up to 15 minutes, and will give up if unable to reach it within
this time frame.
Using the -m option, you can override this. A value of 0 tells sm-notify to retry indefinitely; any other value is interpreted as
the maximum retry time in minutes.
-v ipaddr-or-hostname
This option tells sm-notify to bind to the specified ipaddr, (or the ipaddr of the given hostname) so that all notification packets
originate from this address. This is useful for NFS failover. The given name is also used as the name of this host in the NSM
request.
-p port
instructs sm-notify to bind to the indicated IP port number. If this option is not given, it will try to bind to a randomly chosen
privileged port below 1024.
-q Be quiet. This suppresses all messages except error messages while collecting the list of hosts.
-P /path/to/state/directory
If sm-notify should look in a no-standard place of state file, the path can be given here. The directories sm and sm.bak and the
file state must exist in that directory with the standard names.
-f If the state path has not been reset with -P, sm-notify will normally create a file in /var/run to indicate that it has been run.
If this file is found when sm-notify starts, it will not run again (as it is normally only needed once per reboot). If -f (for
force) is given, sm-notify will run even if the file in /var/run is present.
-n Do not update the NSM state. This is for testing only. Setting this flag implies -f.
-d Enables debugging. By default, sm-notify forks and puts itself in the background after obtaining the list of hosts from
/var/lib/nfs/sm.
FILES
/var/lib/nfs/state
/var/lib/nfs/sm/*
/var/lib/nfs/sm.bak/*
/var/run/sm-notify.pid
SEE ALSO
rpc.nfsd(8), portmap(8)
AUTHORS
Olaf Kirch <okir@suse.de>
19 Mar 2007 sm-notify(8)