Configuring rsync on Solaris 2.8

koroma_a_at_mtn.co.za

To: <sunmanagers@sunmanagers.org>
Date: Wed, 14 Jan 2004 17:39:34 +0200

---
Sebastien DAUBIGNE 
sdaubigne@bordeaux-bersol.sema.slb.com
<mailto:sdaubigne@bordeaux-bersol.sema.slb.com>  - (+33)5.57.26.56.36
SchlumbergerSema - SGS/DWH/Pessac
------------------------------
Message: 2
Date: Wed, 14 Jan 2004 16:55:29 +0530
From: <amit.gpt@wipro.com>
Subject: Configuring rsync on Solaris 2.8
To: <sunmanagers@sunmanagers.org>
Message-ID:
	<024A1A56D6648947BD23C2BCA17300B40896F4@del-ggn-msg.wipro.com>
Content-Type: text/plain; charset="iso-8859-1"
Hi All,
I am planning to backup and synchronize one of our Clearcase Servers
using
rsync.Can somebody suggest the steps to configure the same on the
Solaris 2.8
Server.
Is there any other utility or tool through which I can maintain the
entire
copy ( with latest increments ) on a different server.
Regards
Amit
Confidentiality Notice
The information contained in this electronic message and any attachments
to
this message are intended
for the exclusive use of the addressee(s) and may contain confidential
or
privileged information. If
you are not the intended recipient, please notify the sender at Wipro or
Mailadmin@wipro.com immediately
and destroy all copies of this message and any attachments.
------------------------------
Message: 3
Date: Wed, 14 Jan 2004 07:07:16 -0500
From: "Hirchert, Dale L" <Dale.Hirchert-1@ksc.nasa.gov>
Subject: SUMMARY: L25 causing system to hang
To: "'sunmanagers@sunmanagers.org'" <sunmanagers@sunmanagers.org>
Message-ID:
	<1FFCF939CEB47140898A1076C54AF2B12CD599@kscems004.ksc.nasa.gov>
Content-Type: text/plain; charset="us-ascii"
After installing all recommended patches, and upgrading the firmware on
the V120 server, the culprit was a bad sd.conf file. This problem would
have been solved a lot sooner had the workaround in bugID# 4895444 been
correctly stated. Because of my problem and the recommendation of a Sun
engineer, the workaround in the bugID has since been corrected. The
workaround now correctly states that you can't have more than 8 LUNs per
target. This problem is currently applicable to the L25 tape drive. Here
is the recommended workaround copied from the bugID ( I only included
the fix here) :
Change the scsi target id of the L25 controller where we do not have any
targets that have more than 8 luns. In this case we need to delete
target 0 Lun
8,9,10 and 11. See Below for the changes that need to be made for the
sd.conf
file from the one above. In this example we have only 8 luns per target,
0-7.
                            #
                            # Copyright (c) 1992, by Sun Microsystems,
Inc.
                            #
                            #ident  "@(#)sd.conf    1.9     98/01/11
SMI"
                            name="sd" class="scsi" class_prop="atapi"
                                    target=0 lun=0;
                            name="sd" class="scsi" class_prop="atapi"
                                    target=0 lun=1;
                            name="sd" class="scsi" class_prop="atapi"
                                    target=0 lun=2;
                            name="sd" class="scsi" class_prop="atapi"
                                    target=0 lun=3;
                            name="sd" class="scsi" class_prop="atapi"
                                    target=0 lun=4;
                            name="sd" class="scsi" class_prop="atapi"
                                    target=0 lun=5;
                            name="sd" class="scsi" class_prop="atapi"
                                    target=0 lun=6;
                            name="sd" class="scsi" class_prop="atapi"
                                    target=0 lun=7;
                            name="sd" class="scsi" class_prop="atapi"
                                    target=1 lun=0;
                            name="sd" class="scsi" class_prop="atapi"
                                    target=2 lun=0;
                            name="sd" class="scsi" class_prop="atapi"
                                    target=3 lun=0;
                            name="sd" class="scsi"
                                    target=4 lun=0;
                            name="sd" class="scsi"
                                    target=5 lun=0;
                            name="sd" class="scsi"
                                    target=6 lun=0;
                            name="sd" class="scsi"
                                    target=8 lun=0;
                            name="sd" class="scsi"
                                    target=9 lun=0;
                            name="sd" class="scsi"
                                    target=10 lun=0;
                            name="sd" class="scsi"
                                    target=11 lun=0;
                            name="sd" class="scsi"
                                    target=12 lun=0;
                            name="sd" class="scsi"
                                    target=13 lun=0;
                            name="sd" class="scsi"
                                    target=14 lun=0;
                            name="sd" class="scsi"
                                    target=15 lun=0;
Thanks to all those that offered suggestions.
Dale
ORIGINAL POSTING:
 Have recently purchased an L25 tape drive system, hooking it up to a
V120, using a PCI SCSI-3 dual channel I/O card. The problem occurs when
trying to reboot the V120. The L25 causes the V120 to hang during the
boot process. Sunsolve reported a similar problem and suggested checking
the sd.conf. I have checked the sd.conf file, and have had another admin
check it as well, and we both agree the sd.conf file is correct. At the
ok> prompt, probe-scsi-all reports correctly the library(robot) and the
drive SCSI IDs that are set for the L25. The V120 is so badly hung that
it fails to recognize a "stop-A", thus requiring a power cycle for a
reboot. I have also loaded the recommended patch as suggested from the
Sun system handbook for the L25, but this provided no success. 
------------------------------
Message: 4
Date: Wed, 14 Jan 2004 04:18:27 -0800 (PST)
From: Raji <sun4help@yahoo.com>
Subject: ultra 10 memory identify
To: sunmanagers@sunmanagers.org
Message-ID: <20040114121827.87716.qmail@web61008.mail.yahoo.com>
Content-Type: text/plain; charset="us-ascii"
how to identify dimm1 memory slot in ultra 10 .

Thanks 

Rajesh 
Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes
------------------------------
Message: 5
Date: Wed, 14 Jan 2004 04:25:01 -0800 (PST)
From: Sun Fire <starcat524@yahoo.com>
Subject: Xsun is chewing 95% cpu
To: sunmanagers@sunmanagers.org
Message-ID: <20040114122501.96142.qmail@web21205.mail.yahoo.com>
Content-Type: text/plain; charset=us-ascii
Dear Sun Managers,
I've a V120, Solaris 8 with Sun XVR-100 Graphics
Accelerator and the XVR-100 patch 114537-19 is
installed.
In this system, Xsun is chewing up 95% of my CPU
resources. After I reboot the problem goes away but
comes back again after 20mins. We have stopped all our
applications for a while but the resources did not
realise. I tried to kill Xsun, its releases the
resources but problem came back again.
Would much appreciate if someone out there can shed
some light on this issue.
Thanks in advance.
Regards,
Andrew
__________________________________
Do you Yahoo!?
Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes
http://hotjobs.sweepstakes.yahoo.com/signingbonus
------------------------------
Message: 6
Date: 14 Jan 2004 14:59:08 +0100
From: dominik_kowalczyk@poczta.fm
Subject: SUMMARY(2): SSH2 &amp;amp; forcing password problem
To: sunmanagers@sunmanagers.org
Message-ID: <20040114135912.40EEA1EC8C0@front.interia.pl>
Content-Type: TEXT/plain; CHARSET=ISO-8859-2
there were some requests to say more about scripts...
so in fact it's nothing big;
1. creating user:
scipt creates user, set default (not blank!!!) start password and create
stamp-file (e.g. $LOGNAME.pass)
2. first login
in profile there is executed script to check if stamp-file exists, if
yes,
user is asked for a new password (standard passwd $LOGNAME command);
after password has been changed stamp-file is deleted;
3. IMPORTANT: we cannot allow password to expire (SSH2 not support
password
forcing!)
I've written script to check passwords' expire date, and if (lets say) 7
days
left, a stamp-file is created again and user is forced to change
password
if use this idea, the passwords will never expire
4. change password
the script deletes the user's password (not necessary in fact), set
default
one and create stamp-file to force user to change the default password
during
the first login;
and it works fine for me:)
is this answer ok?
pozdr,
DK
________________________________________________________________________
__
> hey,
>
> in fact I didn't get the answer for my question, but I've found sth on
> the
> net...
>
> so:
> this is well known bug: SSH2 supports passwords aging but doesn't
support
> password root forcing yet(!!!) (acording to Darren Tuckers' OpenSSH
site)
>
> what I've done:
> I've written a script that force user to change the password during
first
> login and second one to monitor passwords' aging (we cannot allow
password
> to
> expire!!!)
>
>
>
> pozdr,
> DK
>
>
________________________________________________________________________
___
> > hey,
> >
> > I've installed ssh2 and since then I've got problem with forcing for
a
> > new
> > password- does anyone had the same and have any solution for this???
> >
> > I've tried SSH2 3.1.0 and OpenSSH 3.7.1p2 and the result was the
> same...In
> > the
> > past, when I had SSH1 installed, everything was ok;
> >
> >
> > does anyone has asny idea or any other solution to force user to
change
> > his
> > default password during the first login?
> >
> >
> >
> > thanks in advance,
> > DK
> > _______________________________________________
> > sunmanagers mailing list
> > sunmanagers@sunmanagers.org
> > http://www.sunmanagers.org/mailman/listinfo/sunmanagers
> _______________________________________________
> sunmanagers mailing list
> sunmanagers@sunmanagers.org
> http://www.sunmanagers.org/mailman/listinfo/sunmanagers
------------------------------
Message: 7
Date: Wed, 14 Jan 2004 09:09:54 -0500
From: Alan G Beardsley <Alan_G_Beardsley@raytheon.com>
Subject: Sun Storedge D1000 Disk Upgrade
To: sunmanagers@sunmanagers.org
Message-ID: <OF613EF115.99CA9147-ON85256E1B.0047ECC9@mck.us.ray.com>
Content-Type: text/plain; charset=US-ASCII
Question:
I have a Sun Storedge D1000 mirrored RAID (0+1) with Disksuite on a Sun
Ultra 80, Solaris 7.   The mirrored RAID has 12  (6 on each side of the
mirror) 18GB IBM Ultrastar Ultra3 SCSI disks Model DDYS-T18350 10K RPM.
There is a system disk on each side of the mirror (18GB) which I want to
leave as is and replace the  remaining 10-18GB disks with 36GB disks
using
Disksuite.    The 36GB disks are SEAGATE Cheetah Model ST336607LC 10K
RPM.
Since the architecture (geometry) of the Seagate disks is different than
the IBM Ultrastar can I use Disksuite and break the mirror on one side,
replace the 5-18GB IBM disks with the 36GB Seagate disks and resync and
then growfs the 36 GB disks  first on one side of the mirror and then
repeat the process for the other side of the mirror or do I have to use
Disksuite only to configure the new 36GB disks on each side of the
mirror
and then restore all the user data from backup tape since the
architecture
of the 18GB and 36GB disks is different ?   Can you outline the steps
that
need to be followed to accomplish the disk replacement ?
Thanks, I will summarize.

   Alan Beardsley                  Raytheon              

   EA Applications Analyst         Network Centric       
   Senior Mechanical Engineer      Systems               
                                   50 Apple Hill Drive   
                                   T1LB22                
   978.858.1897 phone              Tewksbury, MA 01876   
   xxx.xxx.xxxx pager              USA                   
   978.858.1481 fax                                      

   Alan_G_Beardsley@raytheon.com                         
------------------------------
Message: 8
Date: Wed, 14 Jan 2004 09:26:08 -0500
From: "Martin Ma" <mma@admin.fsu.edu>
Subject: I got ld.so.1 corrupt problem, my mounted filesystem is
	empty!!
To: <sunmanagers@sunmanagers.org>
Message-ID: <000001c3daaa$5a2426c0$5238c992@FNAI.org>
Content-Type: text/plain; charset="us-ascii"
Hello every

My ultra 450 run Solaris 7, I got ld.so.1 corrupt problem.
I called for help last week.

I got a lot of help form you guys, but I need more!!

Here are the procedures I did:

1. I boot it from CD:
 OK: boot cdrom -s

2. I did fsck:
#fsck -y /dev/rdsk/c0t0d0s0
It returns:
** /dev/dsk/c0t0d0s0
** Last mount on !
** phase 1 -check blocks and sizes
Incorrect block count I=176460 (2 should be 0)
Correct? Yes
** phase 2 -check pathnames
** phase 3 -check connectivity
** phase 4 -check refrence counts
unref file I=176460 owner=root mode=100644
soze=0 MTime=dec 31 05:35 2003
clear? Yes 
link count file I= 176460 owner=root mode=100644
Size=948 MTime=dec 31 05:35 2003
Count 2 should be 1
Adjust? Yes
66551 files 2638814 used 5458275 free

3. Then I did mount:
# mount -F ufs /dev/dsk/c0t0d0s0 /mnt
Mount ok now

4. And then did cp:
#cp -f /lib/ld.so.1 /mnt/usr/lib
# cd /
5. # umount /mnt

everything looks fine!
Then reboot

Then the messages return:
..
Warning force load of misc /md_trans failed
Warning force load of misc /md_raid failed
Warning force load of misc /md_hostspares failed
TSI: gtxp is GIX8P @ 1152x900
Hostname is ****
Loadkeys: cannot read /usr/lib/ld.so.1
Fsck: cannot read /usr/lib/ld.so.1
The filesystem /dev/md/rdsk/d0 is being checked
Fsck: cannot read /usr/lib/ld.so.1
Killed
Warning -fatal error from fsck -error 137
Unable to repare the filesystem run fsck manually (fsck -F ufs
/dev/md/rdsk/d0)
System will reboot when you exit the shell

Type control-d to proceed with normal startup,
(or give root password for system maintenance)

when I press control-D system reboot and then error repeat again
when I give root password to logon to console
the following message appear:
i386: Cannot read /usr/lib/ld.so.1
killed
quota: Cannot read /usr/lib/ld.so.1
killed
cat: Cannot read /usr/lib/ld.so.1
killed
mail: Cannot read /usr/lib/ld.so.1
killed

And no command can run except "cd"

And then I boot from CDROM again
Repeat procedurals 1 to 4:
1. Boot CDROM -s
2. #fsck -y /dev/rdsk/c0t0d0s0
3.  mount -F ufs /dev/dsk/c0t0d0s0 /mnt
4. #cp -f /lib/ld.so.1 /mnt/usr/lib
and 
#cd /
#cd /mnt
ls
I can see my original filesystems and folders, but each folder is empty.

Brain said if /dev/md/rdsk/d0 is a mirror device, I have to detach the
second half of the mirror.
Pawel said that might explain the ld.so.1 replacement doesn't work
I know this is a good idea, and I need to check if it was mirrored or
not, but I don't know how, because when boot from CDROM in single mode 
the command:
# Metastat d0
doesn't work

What should I do?

 Help me, guys!

Thanks again!!
------------------------------
Message: 9
Date: Wed, 14 Jan 2004 15:05:00 -0000
From: John Dunn <john.dunn@sefas.co.uk>
Subject: [SUMMARY]  How to install samba?
To: sunmanagers@sunmanagers.org
Message-ID:
	<A05E0089719FD311911400A0249EE7E5B50263@guest-wv-50.ripe.net>
Content-Type: text/plain; charset="iso-8859-1"
Thanks for all the replies.
The following about covers it. :
You need to be root and execute the following commands:
# gunzip samba-2.2.8a-1-sol8-suncc-32bit.pkg.gz
# pkgadd -d samba-2.2.8a-1-sol8-suncc-32bit.pkg
------------------------------
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
End of sunmanagers Digest, Vol 10, Issue 24
*******************************************
NOTE: This e-mail message is subject to the MTN Group disclaimer see http://www.mtn.co.za/email_disclaimer.asp
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers

Configuring rsync on Solaris 2.8

Relevant Pages