|
Re: Why does USB backend 'Always write USB printer defs, with unknown for d: msg#00002printing.cups.devel
jeremy.shaw-77kvfFC2TplBDgjK7y7TUQ@xxxxxxxxxxxxxxxx wrote: Hello, Yes. Without this, any USB printer that was connected after cupsd was started would not be accessible. If you can get the USB hotplug stuff to work under Linux (initially, to send the HUP signal to cupsd, but in the future we'll be providing a utility for sending add/delete commands to the scheduler) -- ______________________________________________________________________ Michael Sweet, Easy Software Products mike-B9D8k9nSxTHQT0dZR+AlfA@xxxxxxxxxxxxxxxx Printing Software for UNIX http://www.easysw.com |
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | Why does USB backend 'Always write USB printer defs, with unknown for devices that are not connected.' ?: 00002, jeremy . shaw-77kvfFC2TplBDgjK7y7TUQ |
|---|---|
| Next by Date: | unwanted blank margins in raster data: 00002, Nigel Pegram |
| Previous by Thread: | Why does USB backend 'Always write USB printer defs, with unknown for devices that are not connected.' ?i: 00002, jeremy . shaw-77kvfFC2TplBDgjK7y7TUQ |
| Next by Thread: | unwanted blank margins in raster data: 00002, Nigel Pegram |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |