Previous Thread
Next Thread
Print Thread
No error message when {printer}.pfx can't be read #1567 21 Sep 12 09:31 AM
A
Anonymous
Unregistered
Anonymous
Unregistered
A
When TRACE LP is ON, A-Shell displays the printing process is some detail, and includes something like:
Trace: Prefix: sys:mdunes.pfx, Suffix:
Trace: concatenating.
Trace: .../mdunes.pfx to .../tskaaa.003
Trace: .../srvdsp.lst to .../tskaaa.003
Send .../tskaaa.003 to aux/local ptr

The problem is, if because of a permissions violation A-Shell can't actually read the pfx file, there is no trace error message indicating this problem. It would be nice if trace could include an error message when it couldn't read the pfx file. It might even be worth an error message when TRACE LP is OFF.

Re: No error message when {printer}.pfx can't be read #1568 21 Sep 12 10:47 AM
Joined: Jun 2001
Posts: 11,645
J
Jack McGregor Online Content
Member
Online Content
Member
J
Joined: Jun 2001
Posts: 11,645
I'm not sure how to justify this, but for some reason it is logging those errors to the syslog() facility rather than the normal ashlog.log. Obviously not very useful unless you knew to look there, and even then it makes little sense. It's on the list to fix...


Moderated by  Jack McGregor, Ty Griffin 

Powered by UBB.threads™ PHP Forum Software 7.7.3