![]() |
By a straight rebuild, do you mean running: #emerge -u hylafax That is what I did. (I didn't actually unmerge the old one; is that something that is really important to do?) Since I didn't pay too much attention to what was there and what wasn't before the upgrade, I'm hesitant to file a bug report when it might not have been the problem, but I certainly was able to send a fax before the upgrade. The biggest problem I was having before the upgrade was with the init.d script that came with the 4.1.7 release, which was not a gentoo style script. I was in the process of writing my own script for it when I came across the upgrade that had a gentoo style script included. Thanks for your reponse. > On Thu, 2003-11-20 at 14:23, Aidan Van Dyk wrote: > > How did you upgrade? > > > > It looks like your hylafax spool (/var/spool/hylafax) no longer has the > > client directory (or the permisions in it are wrong). > > > > ls -ld /var/spool/hylafax/client > > drwxr-xr-x 2 uucp uucp 4096 Nov 20 13:34 /var/spool/hylafax/client > > > > I'm the Gentoo ebuild guy for hylafax, and it should be a straight > rebuild the 4.1.8 package and unmerge the old one. Since the 4.1.7 > ebuild had no problems, I didn't spend a bunch of time testing the 4.1.8 > (since it was just a security update). Kindof an assumption on my part, > but the 4.1.8 ebuild is still marked ~x86 (meaning not part of the > stable ebuild list). > > Davison, if you can file a Gentoo bug report, I'll take a look and see > if it's a problem with the ebuild. Go here: > > http://bugs.gentoo.org > > Thanks, Steve > > > > * Davison Long <davlist@xxxxxxxxxxxxxxx> [031120 17:21]: > > > I'm running the latest version of Gentoo Linux and HylaFAX 4.1.8 > > > > > > I just upgraded to the 4.1.8 release and now I'm have a MAJOR problem. > > > I cannot send any faxes or even run the faxstat utility. Everything > > > that follows is occuring on localhost (no remote clients). The > > > following is what the faxstat utility returns: > > > > > > #faxstat -vs > > > Trying localhost (127.0.0.1) at port 4559... > > > Connected to localhost. > > > 420 luther.vagop.com server cannot initialize: Could not create > > > client/2044: No such file or directory > > > > > > Digging deeper, I check the system logs and find the following lines: > > > > > > Nov 21 02:46:11 luther FaxQueuer[2033]: HylaFAX (tm) Version 4.1.8 > > > Nov 21 02:46:11 luther FaxQueuer[2033]: Copyright (c) 1990-1996 Sam > > > Leffler > > > Nov 21 02:46:11 luther FaxQueuer[2033]: Copyright (c) 1991-1996 Silicon > > > Graphics, Inc. > > > Nov 21 02:46:11 luther FaxGetty[1815]: HELLO > > > Nov 21 02:46:11 luther FaxQueuer[2033]: Could not scan client directory > > > for clients > > > Nov 21 02:46:11 luther HylaFAX[2037]: HylaFAX INET Protocol Server: > > > restarted. > > > Nov 21 02:46:20 luther HylaFAX[2040]: connection refused (Could not > > > create client/2040: No such file or directory) from localhost > > > [127.0.0.1] > > > > > > Notice the "could not scan client directory for clients", and the last > > > line caused by the faxstat attempt. > > > > > > My hosts.hfaxd has not changed, and it simply contains: > > > localhost > > > 127.0.0.1 > > > > > > What could be the problem here?? I can't find anything in the archives > > > or on google about this specific problem, and nothing similar seems to > > > address my problem. Could this be a bug in the 4.1.8 release? Any > > > help would be GREATLY appreciated. Thanks, > > > > > > Davison Long > > > > > > > ____________________ HylaFAX(tm) Users Mailing List _______________________ > To subscribe/unsubscribe, click http://lists.hylafax.org/cgi- bin/lsg2.cgi > On UNIX: mail -s unsubscribe hylafax-users-request@xxxxxxxxxxx < /dev/null > *To learn about commercial HylaFAX(tm) support, mail sales@xxxxxxxxxxxx* > > > ____________________ HylaFAX(tm) Users Mailing List _______________________ To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi On UNIX: mail -s unsubscribe hylafax-users-request@xxxxxxxxxxx < /dev/null *To learn about commercial HylaFAX(tm) support, mail sales@xxxxxxxxxxxx*