Description of problem:
 A berkeley hash db file is not recognised as such by file, giving
 a rather useless output:-
   $ file /tmp/test.db
   /tmp/test.db: (1628767744 words)

 This appears to be picking up this entry from the magic database:-
  #---------------------------------------------
  # cracklib:  file (1) magic for cracklib v2.7
  ....
  0	long	0
  >4	belong	0x70775631	Cracklib password index, big endian ("64-bit")
  >12	belong	>0		(%i words)

 which appears *above* the more specific Berkeley DB section

Version-Release number of selected component (if applicable):
 file-4.15-fc4.1

How reproducible:
 Every time...

Steps to Reproduce:
1. echo "one\ntwo"|db_load -T -t hash /tmp/test.db
2. file /tmp/test.db
  
Actual results:
 /tmp/test.db: (1628767744 words)


Expected results:
 /tmp/test.db: Berkeley DB (Hash, version 8, native byte-order)


Additional info:
 Works correctly on RHEL4