>what can be reason for the NET device not to be found Probably it does not yet exist when scandb starts. Even when startup scripts are initiated in the proper order, the actual dependency may be that a network script finishes (or something started by a network script finishes) before scanbd starts.
If scanbd cannot find a device it needs, perhaps it should wait a bit and try again. Maybe an argument that explicitly requests this behavior. -- sane-devel mailing list: [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject "unsubscribe your_password" to [email protected]
