I know that the mysql.sock will be created when MySQL starts up on the new system. I have this every time I clone a system and MySQL always starts up fine. I suspect that the nscd.socket is the same sort of an ipl to ipl entity.
/Thomas Kern /301-903-2211 > -----Original Message----- > From: James Melin [mailto:[EMAIL PROTECTED] > Sent: Tuesday, September 16, 2003 16:27 > To: [EMAIL PROTECTED] > Subject: Re: Far 3390-mod 9's > > > Using this strategy from the link on Linux VM > > mount /dev/dasdh1 /mnt > cd /var > tar -clpSf - . | (cd /mnt; tar -xpSf - ) > > produced 3 errors > > tar: ./lib/mysql/mysql.sock: socket ignored > tar: ./run/printer: socket ignored > tar: ./run/.nscd_socket: socket ignored > > Those three errors translated into missing items in the copy > > rockhopper:/var # diff -r /var /mnt > Binary files /var/db2/.fmcd.lock and /mnt/db2/.fmcd.lock differ > Only in /var/lib/mysql: mysql.sock > Only in /var/run: .nscd_socket > Only in /var/run: printer > > I am concerned that such things are not being copied in this > manner. Is > there a way to make TAR grab these as well? >
