10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hello,
We are planning to setup a Email server with High Availability for email services so that if SMTP/POP/IMAP goes down on one server, the services switch to second server.
We are planning to use a Linux machines from a hosting provider and will do it using DNS with multiple MX records with... (0 Replies)
Discussion started by: sunnysthakur
0 Replies
2. Red Hat
Hi,
I want to create gfs storage. But getting error as below:
--> Finished Dependency Resolution
Error: Package: pacemaker-1.1.12-22.el7_1.2.x86_64 (rhel-ha-for-rhel-7-server-eus-rpms)
Requires: sbd
You could try using --skip-broken to work around the problem
You could try... (1 Reply)
Discussion started by: mzainal
1 Replies
3. Solaris
hi guys
I posted problem last time I didn't find answer to my issue.
my problem is as below:
I have two servers which work as an actif/standby in high availability system.
but when i use command HASTAT -a i have the following message: couldn' find actif node.
the servers are sun... (1 Reply)
Discussion started by: zineb06
1 Replies
4. Red Hat
How can we implement a service in HA, which in not available in HA.
like sldap or customize application.
Requirement Details.
NODE1 service slapd is running.(Require)
NODE2 service slapd is running.(Require)
on both the node replication is happening.
Now here requirement is need... (2 Replies)
Discussion started by: Priy
2 Replies
5. AIX
Hi,
Can someone help and give the answer for the following questions:
1. When PowerHA SystemMirror 7.1 is installed on AIX 7.1, what RSCT component does Cluster Aware AIX (CAA) replace?
A. Group Services
B. Resource Manager
C. Topology Services
D. Resource Monitoring and Control... (2 Replies)
Discussion started by: walterchang100
2 Replies
6. UNIX for Dummies Questions & Answers
Hi,
I want to set up a iscsi high availability with sheepdog distributed storage.
Here is my system set up. Four nodes with sheepdog distributed storage and i am sharing this storage through iscsi using two nodes as well as using a virtual ip set up using ucarp.Two nodes using same iqn. And... (0 Replies)
Discussion started by: jobycxa
0 Replies
7. Solaris
HI Experts,
Could some one help me in configuring high availability zone on Sun Cluster
Reg: Sudhan (3 Replies)
Discussion started by: sudhan143
3 Replies
8. UNIX for Advanced & Expert Users
Hi folks,
(Sorry I don't know what its technology is termed exactly. High Availability OR load balancing)
What I'm going to explore is as follows:-
For example, on Physical Servers;
Server-1 - LAMP, a working server
Server-2 - LAMP, for redundancy
While Server-1 is working all... (3 Replies)
Discussion started by: satimis
3 Replies
9. UNIX for Advanced & Expert Users
we're in the process of reviewing of unix infrastructure main objective is to consolidate on the less versions possible
key decision factors are scalability and high availability options given our multi-datacenter infrastructure, features like HP's continental cluster are top on our wish list... (9 Replies)
Discussion started by: iacopet
9 Replies
10. AIX
Hi all
I was just wondering what modes AIX supports for port trunking ( bonding, etherchannel, link aggregation or whatever you want to call it )
I'm in particular looking for a high availability mode ( other than 802.3ad ) (2 Replies)
Discussion started by: art
2 Replies
ROOTD(1) General Commands Manual ROOTD(1)
NAME
rootd - The ROOT file server daemon
SYNOPSIS
rootd [options]
DESCRIPTION
This manual page documents briefly the rootd program.
rootd is a ROOT remote file server daemon.
This small server is started either by inetd(8) (or xinetd(8)) when a client requests a connection to a rootd server or by hand (i.e. from
the command line). The rootd server works with the ROOT TNetFile, TFTP and TNetSystem classes. It allows access to remote directories and
ROOT files in either read or write mode from any ROOT interactive session. By default rootd listens on port 1094, assigned to it by IANA.
STARTING VIA (X)INETD
To run rootd via inetd(8) or xinetd(8) the port 1094 must be assigned to rootd in /etc/services; the following line should be added, if not
present:
rootd 1094/tcp
If the system uses inetd, add the following line to /etc/inetd.conf:
rootd stream tcp nowait root <bindir>/rootd rootd -i
where <bindir> is the directory you have installed rootd in.
The inetd(8) daemon must re-read its configuration file to become aware of the new service. This can be done either by killing and restart-
ing it manually
kill -HUP <pid inetd>
or, if SYSV init(8) scripts are used, by restarting it, e.g.
/etc/init.d/inetd restart
If the system uses xinetd(8) instead, a file named 'rootd' should be created under /etc/xinetd.d with content:
# default: off
# description: The rootd daemon
#
service rootd
{
disable = no
flags = REUSE
socket_type = stream
wait = no
user = root
server = <bindir>/rootd
server_args = -i
}
where, again, <bindir> is the directory you have installed rootd in.
The xinetd(8) daemon must be restarted:
/sbin/service xinetd restart
If you installed ROOT using some pre-compiled package (for example a Redhat Linux or a Debian GNU/Linux package), this may already be done
for you.
The above configuration examples start the daemon with superuser privileges. Please refer to the inetd(8) or xinetd(8) documentation for
ways of limiting the privileges.
STARTING BY HAND
You can also start rootd by hand running directly under your private account (no root system privileges needed). For example to start rootd
listening on port 5151 just type:
rootd -p 5151
Notice: no & is needed rootd will go in background by itself.
ANONYMOUS LOGINS
rootd can also be configured for anonymous usage (like anonymous ftp). To setup rootd to accept anonymous logins do the following (while
being logged in as root):
1 Add the following line to /etc/passwd:
rootd:*:71:72:Anonymous rootd:/var/spool/rootd:/bin/false
where you may modify the uid, gid (71, 72) and the home directory to suite your system.
2 Add the following line to /etc/group:
rootd:*:72:rootd
where the gid must match the gid in /etc/passwd
3
Create the directories:
/var/spool/rootd
mkdir /var/spool/rootd/tmp
chmod 777 /var/spool/rootd/tmp
Where /var/spool/rootd must match the rootd home directory as specified in the rootd /etc/passwd entry.
4 To make writable directories for anonymous do, for example:
mkdir /var/spool/rootd/pub
chown rootd:rootd /var/spool/rootd/pub
That's all.
If you installed ROOT using some pre-compiled package (for example a Redhat Linux or a Debian GNU/Linux package), this may already be done
for you.
Several remarks:
* You can login to an anonymous server either with the names anonymous or rootd.
* The passwd should be of type user@host.domain Only the @ is enforced for the time being.
* In anonymous mode the top of the file tree is set to the rootd home directory, therefore only files below the home directory can be
accessed.
* Anonymous mode only works when the server is started via inetd(8) or xinetd(8).
ABOUT PASSWORD AUTHENTICATION
In system using shadow passwords, full access to the password field of the user information structure requires special privileges; this is
typically granted if rootd is started by inetd(8) or xinetd(8), as the in above examples. If the daemon is started in unprivileged mode,
either from a regular account or by (x)inetd with reduced privileges, password-based authentication require users to create a file
$HOME/.rootdpass containing an encrypted password (using crypt(3)). The system tests the existence of this file before checking the system
password files. An encrypted password can be created in the following way:
perl -e '$pw = crypt("<secretpasswd>","salt"); print "$pw0'
storing the output string in $HOME/.rootdpass .
If the $HOME/.rootdpass does not exists and the system password file cannot be accessed, rootd attempts to run the authentication via an
sshd(8) daemon.
OPTIONS
-b <tcpwindowsize>
specifies the tcp window size in bytes (e.g. see http://www.psc.edu/networking/perf_tune.html). Default is 65535. Only change
default for pipes with a high bandwidth*delay product.
-d <level>
level of debug info written to syslogd 0 = no debug (default), 1 = minimum, 2 = medium, 3 = maximum.
-D <rootdaemonrc>
read access rules from file <rootdaemonrc>. By default <root_etc_dir>/system.rootdaemonrc is used for access rules; for privately
started daemons $HOME/.rootdaemonrc (if present) is read first.
-f run in the foreground (output on the window); useful for debugging purposes.
-i indicates that rootd was started by inetd(8) or xinetd(8).
-noauth
do not require client authentication
-p <port#>[-<port2#>]
specifies the port number to listen on. Use port-port2 to find the first available port in the indicated range. Use 0-N for range
relative to default service port.
-r files can only be opened in read-only mode
-s <sshd_port#>
specifies the port number for the sshd daemon used for authentication (default is 22).
-T <tmpdir>
specifies the directory path to be used to place temporary files; default is /usr/tmp. Useful when running with limited privileges.
-w do not check /etc/hosts.equiv, $HOME/.rhosts for password-based authentication; by default these files are checked first by calling
ruserok(...); if this option is specified a password is always required.
SEE ALSO
root(1), proofd(1), system.rootdaemonrc(1)
For more information on the ROOT system, please refer to http://root.cern.ch <http://root.cern.ch/>
ORIGINAL AUTHORS
The ROOT team (see web page above):
Rene Brun and Fons Rademakers
COPYRIGHT
This library is free software; you can redistribute it and/or modify it under the terms of the GNU Lesser General Public License as pub-
lished by the Free Software Foundation; either version 2.1 of the License, or (at your option) any later version.
This library is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MER-
CHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public License for more details.
You should have received a copy of the GNU Lesser General Public License along with this library; if not, write to the Free Software Foun-
dation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
AUTHOR
This manual page was originally written by Christian Holm Christensen <cholm@nbi.dk>, for the Debian GNU/Linux system and ROOT version 3.
It has been modified by G. Ganis <g.ganis@cern.ch> to document new features included in ROOT version 4.
ROOT
Version 4 ROOTD(1)
