Keep in mind that Cups is a entirely new printing system that is more
orientated towards Windows printing than Pick printing. If it is
generating so much issues then un-install it and re-install lprng or
lpd.

Keep in mind that Cups in theory wants to receive a postscript job
that it then will convert using ghostscript to the appropriate
printer. It does have raw options but I am sure it then has no
knowledge of the contents of the job.

If it cannot successfully complete a print job it makes sense that it
will restart the job. Lprng and LPD and more stream orientated and
know less about the content of a job and just focus on transmitting
the job to the printer. For D3 it will probably work better to just
re-install lprng.

- Patrick

Scott Ballinger <scott (AT) ccvcorp (DOT) com> wrote

Dave:

You may kick me for saying this, but, what about D3NT? We've basically
moved away from D3Linux for the reasons outlined in these posts:

1) Can't upgrade D3 when support moves to a more recent version of Linux
(i.e. to upgrade D3 requires an upgrade of the O/S too).
2) Support for our application tends to include support for Linux too (with
no additional revenue) but not for Windows (as users usually have a Windows
consultant available).
4) All other RDUS products seem to work well with D3NT and are easy to
install (e.g. FlashConnect, PDP.NET, etc).

It is true that we need to be careful with D3NT. However, for our clients
(5-35) user systems, D3NT is quite nice and stable. In addition, our
application is certified over D3NT while "flash" compiling our code. We
give up some things, but not much. Anyway, as I've mentioned earlier, you
get extra support and stability with D3NT.

In addition, the last several sub-versions of D3 are production stable;
unlike pre 7.3 releases.

I'm ducking now. :-)

Bill

"Dave Weaver" <weaver22 (AT) pacbell (DOT) net> wrote

I just heard that they were unsuccessful at compiling the LPRNG source to
give us the original spooler daemons. I'm not sure what they are going to
try next.


"Patrick Payne" <patrickpayne (AT) yahoo (DOT) com> wrote

Bill, while I personally prefer D3NT for development I think VARs need
to really run D3NT through the mill with their apps before
recommending it for end-user deployment. There are a couple reasons
why I say this:

1) Issue with VME frame consumption not resolved.
2) VME/FSI incompatibilities.
3) Trigger issues reported over time seem to be a recurring issue.
4) Issues with indexes in FSI.

Please don't ask "what issues?", all I'm doing is echoing what I see
and hear. When D3NT becomes a kick-the-tires drop-dead stable
platform then I'll sing the praises too but for now my confidence is
not as high for larger sites as for Linux or AIX.

That said, is there still a performance issue with D3 Linux, raw
volumes, etc? Is it better with or without Update Protection?

These are the only issues I know of that seem to be haunting these
platforms from one release to the next. Of course there are
occasional issues like this printer thing with RHEL. All I can say is
(again) get the betas and do the best you can to beat the software up
Before it goes production. If you've already done this and a problem
slipped through, well, we can only do so much...

T


"Bill H" <wphaskett (AT) THISISMUNGEDatt (DOT) net> wrote:

Then again, we have nothing but problems with d3 aix 7.2.1 and now
7.3.0. GFE's left, right, center. constant problems with printing.
ports don't close properly. we have yet to go back to flash code (we
were core dumping at least once a month, when flashed). its been a
year now since moving from our old dg box and still rd has yet to iron
out all the problems with d3.

Maybe with all of this PDP.net and small d3nt installations rd is
concentrating on the windows platform more than the rest (just a
guess). The flashconnect beta was only released for d3nt. I remember
someone in here commenting on how rd seems to be buddybuddy with ms.

I'm just speculating but I wouldn't doubt if d3 aix and linux were
worked on in rd's spare time while their main focus is the d3nt and
other windows platform products.

-Adam

Adam,

I don't know why you are having so many problems with D3/AIX. I have a half
dozen or so of my larger sites running RS6000's with D3/AIX. I have not seen
a GFE (or an inconsistent group) in ages. Nor have we had any other
problems. Do you think this could be a hardware issue?

Jeff
--

Jeffrey Kaufman
Key Data Systems Group
www.keydata.us
559-432-3832
559-432-4657 fax

Western Pacific Supply
www.westpacsupply.com
888-WestPac

<ashelley (AT) inlandkwpp (DOT) com> wrote

On Tue, 08 Jun 2004 23:11:48 GMT, "Jeffrey Kaufman"
<jeffreykaufman (AT) sbcglobal (DOT) net> wrote:

doubtful, rd is supplying patches to us so if they aren't convinced
its a hardware issue so i can hardly be. We never have had to reboot
the hardware for any other reason other than being instructed to by
rd. No weird error messages (except the ones from d3).

the reason why we bought the box we did was because of d3
compatibility only. nothing else runs on this computer other than d3
and the ftp server.

just mark us in the books for someone who is/does have problems with
d3/aix. I'd love to have more insight as to why we have had so many
problems but I just can't: it just looks like problems with d3.

-Adam

On Tue, 08 Jun 2004 21:14:09 -0700, Dave Weaver wrote:

What is the compile problem ? Why don't you get the latest sources from
http://www.lprng.com/ and compile. LPRng runs on just about everything,
so I'd say it's extremely unlikely to not work with RH.

"BB" <none (AT) nowhere (DOT) nohow> wrote

The problem is that RH ES is not a stock vanilla kernel. Most things
are not going to compile with it. I got error messages trying to
compile lprng from their latest source RPM file from their website.
But it gets worse than that. Serial port cards won't compile either.
Many vendors like Digi and Cyclades are not targeting these
non-vanilla kernels. Don't expect binary RPM packages for your
favorite 3rd party open source projects, either. Just try and find
them on www.rpmfind.net, their not there.

And for some stupid reason Redhat has turned off dynamic module
loading in the RH ES kernel. So, now you have to recompile the entire
kernel just to try things out which increases the risk that existing
modules "fall out" of the kernel because we are not familiar enough
with this process. I haven't had to recompile the kernel since they
added dynamic module support years ago.

Redhat should really step up and compile stuff for RH ES and post them
for download. Nobody else is doing it. They could at least keep up the
hardware compatibility list, but they don't. I tried to talk to
Raining Data many times about going with Fedora but they refused. RH
ES is turning out to be a poor choice.

However, I did create a link to the rtty solution on RH ES (thanks Tom
McTeer):
http://www.d3linux.com/rtty/

P.S. I did load Fedora linux on a brand new Dell 1U rack mount server
and it didn't need any extra drivers. This was with their Perc RAID
card and Gigabit ethernet drivers already in Fedora. Way to go Linux
community!!

Herb
Pathfinders Software
www.pfinders.com

The real issue with AIX is cost. Because of this replacing the box
will be the last thing you will do. I too think you are having
hardware problems. I moved up to D3/Aix 2 years ago and have had 0
gfe's. I feel I do stress my system pretty good. I have commented
back and for with you before on this issue. We have 150-215 users,
50+ printers (that print very large print jobs that contain multiple
HP downloaded background forms. Therefore we are sending lots of
special characters thru our queue), web services accessed via pipes,
lots of q-pointer calls to unix files that are on a NFS mounted
server.

Basically I feel I am doing everything weird you can do and have 0
problems with D3/aix. A sister company was running upwards of 500
users with a similiar setup (without the web interface stuff) and was
also having no issues. Another sister company runs the backend of
E*Trades mortgage site and is probably in the 500 user range also and
utilizes flashconnect to expose pick functions to the E*trade web
site.

My setup is

IBM p650 (6 processor capable, we have 4)
d3 7.3.0.RS (no patches loaded)
4 gigs ram
simple raid 5 (3 drive) external chassis (normal scsi)
2 drive scsi mirror in box for root system
Aix 5L with all linux extentions loaded.

Now, I must also say I have never allowed IBM in to load any patches.
They have asked a few times but we have never got together to do it.
Why fix what is not broke.

To be getting so many GFE's really tells me you have a hardware/memory
issue somewhere. Ibm stuff is usually really good at telling you when
you have a problem. This capability may be directing people to think
it is not the hardware, but this capability is not perfect. But
again, if it was Intel/Amd stuff I would just buy a new machine and
verify that was not my problem. But with $50,000 to $100,000 machines
this is much more difficult.

- Patrick

ashelley (AT) inlandkwpp (DOT) com wrote in message news:<pjhcc0hmo6vdeft3uapbiqur6l73imib3o (AT) 4ax (DOT) com>...