I think you might have missed Frank's post earlier, here's what he said:
---
Also, going back to the original question, you may want to add an entry
for your DB server to /etc/c3.conf, or a separate "cluster" entry in
/etc/c3.conf, and possibly as a scphost in
/opt/opium/etc/sync_users.conf to keep passwords, etc up to date.
---Cheers,
Bernard
P.S. About the /scratch idea - we do that too on our NetApp and it seems to work fine. Given it is a /scratch space, I think it's fine to let it be 'free-for-all' for the users.
Sarat C Maruvada wrote:
Hello Everybody.Thank you very much for all your responses. I am currently working on the installation of DB node when a greater problem hit me. The hosts configuration is an inconvienince which can be handled in one of the ways you suggested, but a greater problem is the user access to db node. 1. The main purpose of DB node is to provide storage for huge data that will be required by the users.It can always be done such that root user installs the data and other users can read/make copies of it. 2. Better, each user can install their required data and access it across the cluster on NFS. 3. Provide a central /scratch directory with "wrx" for all users: completely insecure, or provide /scratch/username(or alternatively /home/username/scratch (/home/username comes from master node NFS,while scratch is NFS mounted space from DB node based on the user) space for all users providing access on log on... 4. THE PROBLEM!!!: user names maintained and synchronized by OSCAR on remaining nodes of the cluster but this node is not a part of OSCAR.What do I do?Maybe there is a obvious solution i missed...
Hope I put my problem across...any alternate designs would be most welcome...
Sincerely, Sarat.
On Tue, 3 Feb 2004, Art Wildman wrote:
Been following this thread with some interest, have seen very strange problems before with poorly configured /etc/hosts or dns...
This quick howto on 'Setting the Linux Hostname' was helpfull: http://www.cpqlinux.com/hostname.html
While installing Fedora the other day I noticed an interesting package called 'dnsmasq', that may be helpful to OSCAR installations like this...
Dag's Apt-RPMs site http://dag.wieers.com/home-made/apt/ (BTW, yum+apt are very cool ...any plans to support Fedora/yum updates?)
# yum info dnsmasq Gathering header information file(s) from server(s) Server: ATrpms for Fedora Core 1 good Server: ATrpms for Fedora Core 1 stable Server: Fedora Core 1 - i386 - Base Server: Fedora Linux 1 - i386 - core Server: Dag's RPMs for Fedora Core 1 stable Server: Fedora Core 1 - i386 - Extra Packages Server: Fedora Linux 1 - i386 - freshrpms Server: JPackage 1.5 for Fedora Core 1 Server: Livna 3rd party packages with questionable (in USA) licenses -- use at your own risk Server: Macromedia Flash Plugin for Fedora Core 1 Server: Fedora Core 1 NewRPMS.sunsite.dk Server: Fedora Linux 1 - i386 - updates Server: Fedora Core 1 - i386 - Released Updates Server: XFCE4 Packages Compatible with Fedora Core 1 Finding updated packages Downloading needed headers Looking in Available Packages:
Name : dnsmasq Arch : i386 Version: 2.2 Release: 0.rhfc1.dag Size : 166.25 kB Group : System Environment/Daemons Repo : Dag's RPMs for Fedora Core 1 stable Summary: A lightweight caching nameserver. Description: Dnsmasq is lightweight, easy to configure DNS forwarder and DHCP server. It is designed to provide DNS (domain name) and, optionally, DHCP services to a small network. It can serve the names of local machines which are not in the global DNS. The DHCP server integrates with the DNS server and allows machines with DHCP-allocated address to appear in the DNS with names configured either in each host or in a central configuration file. Dnsmasq supports static and dynamic DHCP leases and BOOTP for network booting of diskless machines.
-HTH [EMAIL PROTECTED]
Bernard Li wrote:
Okay so /etc/hosts keeps track of the changes made in the top section, but I guess the problem is each time you add/remove a node it thinks that they are all changes and therefore there are multiple occurences of the same hostname in the resulting /etc/hosts.
So I guess the bottom line is you can add the host in the /etc/hosts file on each node and OSCAR/SIS should not really blow it away.
Sorry for the confusion.
Cheers,
Bernard
------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ Oscar-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/oscar-users
