[moneydance] Moneydance 2007 beta2

[Doug B]

On Tuesday 09 January 2007 01:15, Fuzzy Fox wrote:
> Doug B <md at hatterhill.com> wrote:
> > Not printers...  You may not have the file.  Note above in what
> > Fuzzy Fox posted:  ...you can *create/update* an
> > /etc/cups/client.conf file...
> >
> > I have one, but it's all comments.  It isn't needed in most cases. 
> > I didn't edit the file on my box...  I was just reposting what
> > Fuzzy Fox had to say.  All I did was comment out the "Listen
> > /var/run/cups/cups.sock" line in my /etc/cups/client.conf and
> > restarted cups.
>
> This shows that there is still more to the problem than has been
 

What this also shows is that I shouldn't try to answer questions when 
I'm too tired.  It wasn't the /etc/cups/client.conf that I edited... it 
was the server file /etc/cups/cupsd.conf where the line was commented 
and edited. 


> pointed out so far.  I think I can summarize it like this:
>
>
> CUPS consists of two parts, a client and a server.  When you talk
> about "restarting CUPS" you are restarting the server.  There is no
> "client" process that needs to be restarted.  The "client" program is
> the program that is trying to print (such as "lpr", or "gimp" or
> "Moneydance").
 

I'm sure you're correct in that cups doesn't need a restart when editing 
the client file.  I've dealt with some poorly written stuff that reads 
all kinds of config files.  I've simply found it easier for me to 
restart the server when I edit any file associated with the 
service.  It's become a habit now. 

 
> However, from reading the results from this list, it would seem that
> Java DOES seem to respect the CUPS_SERVER environment variable.  It



A reminder to folks on setting the environment variable... it is only 
set for the session you are in.  If you open a terminal window, set the 
CUPS_SERVER=localhost, then try to open Moneydance using a menu entry 
or desktop icon, it won't use the newly set variable.  You would need 
to start MD from the command line in the same session (terminal 
window)that you set the variable in.

If you want to have it stick across reboots and logins, I think you 
could edit /etc/profile to add: 

CUPS_SERVER=localhost
export CUPS_SERVER 

logout and login again.  The variable should then be set globaly at 
every login. 


> Unfortunately, the only Linux system I currently have access to, does
> not have a printer, so this is not something I can test and report
> back results for.  Would anyone out there be willing to test some
> options?
>
> I think the best course would be to somehow cajole Java into using
> the same print method as the rest of the system, which is likely to
> be domain sockets.
>
> On my Ubuntu system, CUPS server ports are configured in the file
> /etc/cups/cups.d/ports.conf, which has these lines:
>
>     Listen localhost:631
>     Listen /var/run/cups/cups.sock
>
> So, my particular CUPS server is listening on both methods.
>



Before I 'fixed' my cupsd to use the IP instead of domain socket, I 
could still configure cups by putting localhost:631 into a browser 
window.  I can also pick up other cups servers broadcasting on port 
631.  It was obviously  listening on port 631 but still using the 
domain socket.  It would seem that listening to port 631 and using IP 
socket is not the same thing.  I'm certainly no expert though.  In the 
version of cups I'm using, using the IP socket appears to be the 
default and is overridden when the Listen /var/run/cups/cups.sock
line is active in the cupsd.conf.


> However, my system has no /etc/cups/cups.client file, so it is
> following some mystery default behavior.  What I'd like to do is to
> create the file /etc/cups/client.conf, and add this line:
>
>     ServerName /var/run/cups/cups.sock
>
> This would tell any printing client (hopefully including Java) that
> it should use the domain socket to print.  However, without a
> printer, I can't really test that.  Does anyone want to try this and
> see if it works?
>
> It is rather sad that every Linux distribution probably has a
> different default behavior for CUPS, and has configuration files in
> slightly different places, and puts the domain sockets in different
> locations, so that there is no "One True Way" to solve this problem
> once and for all, for all Moneydance users.
>
> But, maybe we can at least build up enough information to fill a
> Wiki. Who knows?

I am trying some things tonight ad will post to a new thread.

Doug