[Esd-l] error on procmail

[Adi Linden]

I came across this in the archive but didn't see a solution anywhere.

> > I also get this in the file every time it runs
> > 
> > <---snip---
> > type: type: No such file or directory
> > type: type: No such file or directory
> > ---snip--->
>
> That's odd. I thought "type" was a shell builtin.
>
> Can you run "type mktemp" when you log in normally?

I am getting the same errors when running procmail. The 'type' command is 
indeed a shell builtin:

    [adilinden at yoda adilinden]$ type mktemp
    mktemp is /bin/mktemp

And there is no binary in the filesystem:

    [adilinden at yoda adilinden]$ which type
    /usr/bin/which: no type in (/bin:/usr/bin:/usr/local/bin:/usr/bin/X11:/usr/X11R6/bin:/home/mailusers/adilinden/bin)

And here is an strace from executing procmail with the relevant parts that 
generate the error message:

  [pid 10227] open("type", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory)
  [pid 10227] stat64(".", {st_mode=S_IFDIR|0700, st_size=4096, ...}) = 0
  [pid 10227] stat64("/usr/bin/type", 0xbffff9c0) = -1 ENOENT (No such file or directory)
  [pid 10227] stat64("/home/mailusers/adilinden/bin/type", 0xbffff9c0) = -1 ENOENT (No such file or directory)
  [pid 10227] stat64("/bin/type", 0xbffff9c0) = -1 ENOENT (No such file or directory)
  [pid 10227] stat64("/usr/bin/type", 0xbffff9c0) = -1 ENOENT (No such file or directory)
  [pid 10227] stat64("/sbin/type", 0xbffff9c0) = -1 ENOENT (No such file or directory)
  [pid 10227] stat64("/usr/sbin/type", 0xbffff9c0) = -1 ENOENT (No such file or directory)
  [pid 10227] stat64("/usr/local/bin/type", 0xbffff9c0) = -1 ENOENT (No such file or directory)
  [pid 10227] stat64("/usr/X11R6/bin/type", 0xbffff9c0) = -1 ENOENT (No such file or directory)
  [pid 10227] stat64("/usr/local/bin/type", 0xbffff9c0) = -1 ENOENT (No such file or directory)
  [pid 10227] write(2, "type: type: No such file or dire"..., 38type: type: No such file or directory
  ) = 38
  [pid 10227] _exit(127)                  = ?

Any suggestions on how I can get rid of the pesty 'type:...' error 
generated by procmail?

Thanks,
Adi