I was thinking about what Scott suggested concerning using syslog(3) for the error messages when I thought it might be a good idea to change where scs2pdf writes it's output. So I made it so that if the environment variable TN5250_PDF is set scs2pdf would open the filename specified there, otherwise it opens stdout. But after doing so I realized that by smart use of the outputfile argument to lp5250d pretty much anything could be done without needing an environment variable. So I'm wondering if anyone can think of a use for being to set the name of the generated PDF via a method other than the outputcommand argument. Its only about 10 lines of code, but this ain't MicroSoft and we don't features for the sake of having features.
I'm still thinking about syslog. It is probably the best way to, any enterprise-level (buzzword!) program ought to tell people what it is doing if they need it. Maybe with priority LOG_DEBUG? Anyway, if people think its useful, the diff is at: http://www.eaerich.com/tn5250.diff This includes an update to the ChangeLog. James Rich [EMAIL PROTECTED] _______________________________________________ This is the Linux 5250 Development Project (LINUX5250) mailing list To post a message email: [EMAIL PROTECTED] To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/linux5250 or email: [EMAIL PROTECTED] Before posting, please take a moment to review the archives at http://archive.midrange.com/linux5250.
