NAME

       xfmtype - xfm file type tester

SYNOPSIS

       xfmtype -m magic_file [-f] filename ...

DESCRIPTION

       The  xfmtype program reads a magic configuration file and tests each file in its command line to tell its
       type according to the configuration file.

       The format of the configuration file is the similar to magic(5) with the differences described in 0

OPTIONS

       -f file
           Consider the following argument as a file, even if it begins with `-'.

       -m file
           Specifies a configuration file. You can specify more than one  configuration  file  with  several  -m
           flags.  They  are  read  in the order in which they are found. Configuration files do not have effect
           until they are encountered in the command line. So, files to test in the  command  line  before  that
           switch will not be affected by it.

BUILT IN TYPES

       If  no  rule  matches a specified field or the type cannot be determined because of other reasons, one of
       the following built in types is returned:

       inode/x-unreadable The file could not be read.

       inode/x-empty File size is zero.

       text/plain The file looks like ACSII.
       xfm will look into xfm_mime.type(5) for more guessing.

       application/octet-stream Other regular file.
       xfm will look into xfm_mime.type(5) for more guessing.

       inode/directory A directory.

       inode/chardevice A character device.

       inode/blockdevice A block device.

       inode/pipe A names pipe (fifo).

       inode/socket A socket.

       inode/default None of the above.

BUGS

       Bad configuration lines cause undefined behavior. In general they are silently ignored, but that  is  not
       guaranteed.
       There are no warning or error message except for the regular expression syntax.
       There should be a syntax checking mode.
       All of the above apply to xfm too.

SEE ALSO

       xfm(1), xfm_magic(5), file(1), magic(5).

COPYRIGHT

       Copyright (c) 1995 CNM-US
       Copyright (c) 1995 Juan D. Martin

AUTHOR

       Juan D. Martin (juando@cnm.us.es)
       (but modified heavily by Bernhard R. Link)