JASS - upgrading from Sol 9 to Sol 10

10 More Discussions You Might Find Interesting

1. Solaris

sol 10 sparc cant join dns

Hi I would like to ask if somehow i missed some files in configuration of joining a domain below is the procedure i take: modify /etc/nsswitch.conf host: file dns modify /etc/resolv.conf nameserver ipaddress nameserver ipaddress domain ft.domain.com search...

2. Solaris

GCC for X86 on SOL 10

Need help with GCC package. I did downloaded the same from sunfreeware.com for i86, however after doing the unzip I am unable to add the same with pkgadd as I am unable to get the sun standard format as SUNWgcc on my system. Thanks

3. UNIX for Advanced & Expert Users

luupgrade: Sol 8 -> Sol 10 u7 (5/09)

Greetings Forumers! I ran into an issue after running luupgrade on v880 running Solaris 8. I want to upgrade to Solaris 10. When I rebooted the system I noticed the file systems listed as such: # df -h Filesystem size used avail capacity Mounted on /dev/dsk/c1t1d0s0 ...

4. Solaris

Need help with mail service on Sol 10

Hello All: I am trying to configure mail service on Solaris 10 and I am unable to send using mailx. It appears the server may not be listening on port 25: bash-3.00# mconnect connecting to host localhost (127.0.0.1), port 25 connect: Connection refused services is configured to use port...

5. UNIX for Dummies Questions & Answers

Login Prompt - Sol 10

Hello When I login as root - my prompt is # I want to change this and I understand the setting (PS1=) needs to go into a file called .profile, but I don't know where this file is for the root user. The root users home folder is / when I type env. Should I be creating a home folder for the...

6. UNIX for Advanced & Expert Users

Sol 10 Sendmail issue

We have a Spark Solaris 10 box running behind a Pix 501 firewall, we are running NAT and I have mapped access to it from the outside world. Anyway, we can receive mail no problem just can't send. I receive this message bounce: The original message was received at Thu, 10 Jan 2008 17:04:29 -0600...

7. Solaris

config v120(sol 8) as a router

Hello all I'm trying to configure a v120 (sol8) as router. The exact setup is: 2900 switch | | eri0 eri1 (node1 v120 sol8)----------------------> eri0 (node2 v120 sol8) so node1 eri1 is connected to node2 eri0. Also, on node1...

8. UNIX for Dummies Questions & Answers

kernel parameter in SOL

Hello everbody: I have Sol9, and I need to check its kernekl parameters, do you know how to list them or in which file they can be found. Thanks in Advance

9. Solaris

Chinese characters on Sol 2.7

Hi there, I need to get a Chinese disclaimer attached to an email on a Solaris 2.7 box. The disclaimer we use is in English and stored as a text file although I've been asked to see if we can add the Chinsese one? Is it simply just a matter of adding the Chinese locale to the OS or is there...

10. Filesystems, Disks and Memory

Move a disk to Sol. 2.6

I removed an external Sun disk (with data on it) from an old 2.6 system and added the disk to another 2.6 system. The new system seems to recognize the system (verified by the format command). When try to mount I am getting, I got the error: mount: /dev/dsk/c1t1d0s6 is not this fstype. I...

LEARN ABOUT CENTOS

groupd

GROUPD(8)							      cluster								 GROUPD(8)

NAME

       groupd - compatibility daemon for fenced, dlm_controld and gfs_controld

SYNOPSIS

       groupd [OPTIONS]

DESCRIPTION

       The  groupd  daemon  and  libgroup  library  are used by the fenced, dlm_controld and gfs_controld daemons when they are operating in clus-
       ter2-compatible mode to perform a rolling cluster upgrade from cluster2 to cluster3.

       See cman(5) for more information on the upgrading configuration option needed to perform a rolling upgrade.

       When the upgrading option is enabled, cman adds the following to the online configuration:

	    <group groupd_compat="1"/>

       This setting causes the cman init script to start the groupd daemon, and causes the groupd, fenced, dlm_controld and  gfs_controld  daemons
       to operate in the old cluster2 mode so they will be compatible with cluster2 nodes in the cluster that have not yet been upgraded.

       The  upgrading setting, including the groupd_compat setting, cannot be changed in a running cluster.  The entire cluster must be taken off-
       line to change these because the new cluster3 default modes are not compatible with the old cluster2 modes.  The upgrading/compat  settings
       cause the new cluster3 daemons to run the old cluster2 code and protocols.

OPTIONS

       Command line options override a corresponding setting in cluster.conf.

       -D     Enable debugging to stderr and don't fork.

       -L     Enable debugging to log file.

       -g num groupd compatibility mode, 0 off, 1 on. Default 0.

       -h     Print a help message describing available options, then exit.

       -V     Print program version information, then exit.

SEE ALSO

       cman(5), fenced(8), dlm_controld(8), gfs_controld(8)

cluster 							    2009-01-19								 GROUPD(8)

Solaris