# debugging saned

From: Brian Craft (bcboy@thecraftstudio.com)
Date: Fri Oct 13 2000 - 12:22:33 PDT

- Next message: Jochen Eisinger: "Re: Mustek/LifeTec/Medion parport CIS driver"
  - Previous message: Petter Reinholdtsen: "Re: [snapscan] Sourceforge request submitted"
  - Next in thread: Jochen Eisinger: "Re: debugging saned"
  - Reply: Jochen Eisinger: "Re: debugging saned"
  - Reply: Petter Reinholdtsen: "Re: debugging saned"
  - Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

  Anyone have any hints for debugging saned? I haven't found a way
  to use the -d option, since saned bails out after every request. You
  can't actually run a client with debugging enabled in saned. Looks like
  xsane is sending a NET_EXIT in between every request. And it seems
  you can't use -d when running from inetd, because -d makes it open
  its own socket (losing the incoming connection from inetd).

  b.c.

      --
      Source code, list archive, and docs: http://www.mostang.com/sane/
      To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com

  - Next message: Jochen Eisinger: "Re: Mustek/LifeTec/Medion parport CIS driver"
  - Previous message: Petter Reinholdtsen: "Re: [snapscan] Sourceforge request submitted"
  - Next in thread: Jochen Eisinger: "Re: debugging saned"
  - Reply: Jochen Eisinger: "Re: debugging saned"
  - Reply: Petter Reinholdtsen: "Re: debugging saned"
  - Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

  This archive was generated by hypermail 2b29 : Fri Oct 13 2000 - 11:56:02 PDT