Stan Sieler ([log in to unmask]) wrote:

: I tried doing:

:    :listspf ; seleq [dev = foo]

: to see if he could use LISTSPF in a sneaky manner, but listspf
: fails to validate that the "device" is a valid device of any kind :(

: Of course, if that bug were fixed (i.e., if the listspf "dev" was
: defined to only allow valid printer classes)...then that would be
: a workaround to the problem of identifying a valid printer class.

"Not a bug", he said defensively, and a little bit testily.  LISTSPF
traverses device queues in the SPFDIR, based on entries found in a
second (internal) table, the target name queue header table.  A device
entry is not made in that table until a spool file is created for
that device.  So a failure to find any files for [dev=foo] could easily
be due to the fact that no files have been generated for it since the
system was booted.  That does *not* mean the device does not exist or
has not been configured.  It merely means that LISTSPF tried to find
files on a queue for it and did not.

If you want a command to verify your configuration, invent one
(VALIDATEDEVICE or some such).  Don't overload other commands with
unrelated functionality.  And don't call it a bug (unless you can
find a spec that says LISTSPF will identify all non-existent devices).

-Larry "coming down off the wall now" Byler-