Linux rsync list file directory on rsync server

How to list file and directory on rsync server. The Linux rsync command example below show how to use the rsync list file and directory on rsync server.

1. make sure that rsync command install on your Linux system.
2. Execute rsync server-domain-name::directory as show on the example below...

Linux rsync command example

[fedora10@fedora ~]$ rsync mirrors.ispros.com.bd::fedora



drwxr-xr-x        4096 2007/05/22 05:37:48 .
drwxr-xr-x        4096 2006/10/17 20:46:37 core
drwxr-xr-x        4096 2010/08/01 03:06:42 development
drwxrwxr-x        4096 2009/05/16 05:58:30 extras
drwxr-xr-x        4096 2010/10/27 07:13:03 releases
drwxrwsr-x        4096 2010/08/28 03:54:20 updates
[fedora10@fedora ~]$


or


[fedora10@fedora ~]$ rsync mirrors.kernel.org::fedora
 
rsync for batter sync :-)

Public key for google-chrome-stable_current_i386.rpm is not installed

Install  google chrome on fedora 14, but error message say that Public key for google-chrome-stable_current_i386.rpm is not installed.

solution for Public key for google-chrome-stable_current_i386.rpm is not installed:

1. Download Google Chrome on your Fedora PC/Server.

2.  Locate the googel chrome rpm file on Download directory.

3. Execute yum command as show below to install google chrome without Public key check...


[root@linux Downloads]# yum -y --nogpgcheck localinstall google-chrome-stable_current_i386.rpm

4. Please note that yum will install all require rpm file in order to install google chrome (dependencies package)

failchk: DB_RUNRECOVERY: Fatal error

Try to update Fedora 14 to day but, yum only display error that say fatal error , run database recovery...
 
[root@linux ~]# yum --skip-broken -y  update
rpmdb: Thread/process 2620/failed: Thread died in Berkeley DB library
error: db3 error(-30974) from dbenv->failchk: DB_RUNRECOVERY: Fatal error, run database recovery
error: cannot open Packages index using db3 -  (-30974)
error: cannot open Packages database in /var/lib/rpm
CRITICAL:yum.main:

Error: rpmdb open failed


Solution 1:

1.  Fix the rpm database by run database recovery, as show on command example below:

[root@linux ~]# db_recover -h /var/lib/rpm

Clean yum cache:
[root@linux ~]# yum clean all

and then proceed to update Fedora again.... or try

Solution 2:

Skip the run databese recovery... just create or rebuild new rpm database

Remove old rpm database:
[root@linux ~]# rm -f /var/lib/rpm/_db*

Rebuilt RPM database (.. rebuilt rpm database process may take hours to finish):
[root@linux ~]# rpm --rebuilddb

Clean yum cache:

[root@linux ~]# yum clean all

UPDATE FEDORA:
now just try update your Linux Fedora
[root@linux ~]# yum --skip-broken -y update

( Please note, that you must execute the above command as root user )