Re: debugging saned

• Previous message: Petter Reinholdtsen: "Re: remove option -pedantic from standard gcc options?"
• Maybe in reply to: Brian Craft: "debugging saned"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[Jochen Eisinger]
> Disable saned in your inetd.conf and start saned from your command
> line like this

Or make a shell script wrapper for saned, to set the environemnt.
This way you can also peek into the communication.

Log messages might end up in syslog (if stderr is a socket, debug
messages are sent to syslog).

Rename saned to for example saned.exe, and make a script saned like
this:

  #!/bin/sh
  SANE_DEBUG_HP=128
  export SANE_DEBUG_HP
  cd /tmp
  exec $0.exe 2> saned.$$.stderr | tee saned.$$.stdout

This will make two files with stdout and stderr from the last session
in /tmp/. The debug information will be in saned.*.stderr.

-- 
##>  Petter Reinholdtsen  <##  |  pere@td.org.uit.no
--
Source code, list archive, and docs: http://www.mostang.com/sane/
To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com

• Next message: Petter Reinholdtsen: "Re: [snapscan] Sourceforge request submitted"
• Previous message: Petter Reinholdtsen: "Re: remove option -pedantic from standard gcc options?"
• Maybe in reply to: Brian Craft: "debugging saned"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Sun Oct 15 2000 - 08:31:40 PDT