Looking for unix print queue (NOT spooler)

[kaih]

I am looking for an honest to goodness managable print queue for unix. The lpsched spooler is not sufficiently reliable for some of our applications and I have to jump through hoops to let anyone besides root manage it.<br>
<br>
I really like LP Plus by Plus Technologies (<A HREF="

http://www.plustechnologies.com"

TARGET="_new">

http://www.plustechnologies.com</A>)

but my manager says that it is probably priced out of our budget. Does anyone know of a cheaper (ideally free, but I do have &lt;I&gt;some&lt;\I&gt; money) print queue with at least some of these characteristics (in decreasing order of priority):<br>
<br>
- first level support can delete or put jobs on hold.<br>
- confirmation to status monitor that printer successfully received print jobs.<br>
- restart big jobs from the point they were interupted.<br>
- multiple versions of a file can be in the same queue at the same time.<br>
- can choose to save or delete spooled file. Not the source file that was printed, but the print stream.<br>
<br>
Thanks,<br>
Kai.<br>

 

[mrregan]

Kai,<br>
What kind of problems are you trying to overcome?

 

[MikeLacey]

Your manager's response is probably spot on there. There are some very good proprietary spoolors out there (HP's Openspool springs to mind) but they're not cheap.<br>
<br>
We could help you get over *some* of the problems you'd like to fix<br>
<br>
1) first level supp control of jobs - yep<br>
2) confirmation - hmm - don't know - maybe<br>
3) restart jobs - don't think so<br>
4) multiple versions of file at same time - yep<br>
5) save/delete spool file - yep<br>
<br>
Probably be best to take them one at a time - each with it's own thread here.<br>
<br>
regards<br>
<br>
Mike<br>
<p>Mike Lacey<br><a href=mailto:Mike_Lacey@Cargill.Com>Mike_Lacey@Cargill.Com</a><br><a href=

http://www.cargill.com/>

Cargill's Corporate Web Site</a><br>

 

[kaih]

We ended up just writing a sudo script to let Operations cancel print jobs. We also made the &quot;copy&quot; parameter the default, so it copies the file to the spool instead of just a pointer to the file. <br>
<br>
That handled the two most critical issues, immediate cancels and multiple versions of the file. <br>
<br>
The decision was that if the user needs a restart they will just have to rerun the job.<br>
<br>
Thanks.<br>
Kai.<br>

 

[MikeLacey]

You're *way* ahead of me Kai &lt;smile&gt; <p>Mike Lacey<br><a href=mailto:Mike_Lacey@Cargill.Com>Mike_Lacey@Cargill.Com</a><br><a href=

http://www.cargill.com/>

Cargill's Corporate Web Site</a><br>