| | 1 | $FreeBSD: src/tools/3.0-upgrade/README,v 1.2.2.1 2002/08/08 10:05:55 ru Exp $ |
| | 2 | $DragonFly: src/tools/3.0-upgrade/Attic/README,v 1.2 2003/06/17 04:29:10 dillon Exp $ |
| | 3 | |
| | 4 | By 1996/12/04, the utmp element size has been changed, in order to |
| | 5 | allow for longer usernames. This change renders all existing wtmp |
| | 6 | files unusable. The cvt-wtmp utility is provided as an aid to convert |
| | 7 | your old wtmp files into the new format, so you don't lose the |
| | 8 | existing track record. |
| | 9 | |
| | 10 | The tool cannot handle gzip'ed wtmp backups, so unzip them first if |
| | 11 | you need. Then simply call it as: |
| | 12 | |
| | 13 | ./cvt-wtmp /var/log/wtmp* |
| | 14 | |
| | 15 | The old wtmp files are being renamed to <file>.bak, so nothing will be |
| | 16 | lost even in case of a failure. If you are only about to test whether |
| | 17 | the tool will grok your files correctly, you can run it as: |
| | 18 | |
| | 19 | ./cvt-wtmp -n /var/log/wtmp* |
| | 20 | |
| | 21 | The tool tries an ``educated guess'', based on the reasonability of |
| | 22 | the timestamp values in the wtmp file. If it fails to recognize the |
| | 23 | format of your wtmp, it normally bails out, or at least ignores |
| | 24 | garbage records. In this case, rename the .bak files to the original |
| | 25 | name, and try to force the conversion: |
| | 26 | |
| | 27 | ./cvt-wtmp -f /var/log/wtmp.xxx |
| | 28 | |
| | 29 | Make sure to verify the result however! |
| | 30 | |
| | 31 | |
| | 32 | Dresden, Jan 2, 1996 Joerg <joerg@FreeBSD.org> |
projects / dragonfly.git / blame_incremental