Ok, I have over 3,000 links.

When I build my site with the build all it builds the pages up to 1/4 of the way.
that has to do with the server/hosting company. Which is not a problem.
But I notice that when I build with the build all it builds the pages correctly up to when it stops.

Now if I do a build Staggered (Auto) which has been working fine. I noticed that
a lot of the pages say zero links, when there are links there.
On the build all the ones that is shows show links and builds them.
Staggered (Auto) Some pages have links some don't

Need Help.
John

As has been mentioned many times in this forum...use telnet to build your directory, it is a lot faster and uses less CPU.

Also, you getting close to the limit of LINKS 2.0 in terms of number of records and if your links.db size has exceeded 1.0 MG, then it time to upgrade to LINKS SQL.

Regards,

------------------
Eliot Lee....
Former Handle: Eliot
* Check Resource Center
* Search Forums
* Thinking out of the box (codes) is not only fun, but effective.

Unfortunately my hosting compay does not have telenet.
They are looking into it, but I doubt they will.

How much work is it to go to SQL from Links 2.0?

and how much different is it from Links 2.0.

Thanks
John

Please read the Topics in the Discussion Forum and the LINKS SQL Forum that discuss this issue.

Yet since you do not have shell access, I doubt that your hosting company offers MySQL for database table storage.

Regards,

------------------
Eliot Lee....
Former Handle: Eliot
* Check Resource Center
* Search Forums
* Thinking out of the box (codes) is not only fun, but effective.

Question: My Links installation just began doing the same thing his is (I've got about 1150 links), and I also don't have telnet access. Do you guys think that building via a CRON event would have the same results as building via telnet? Build-Staggered isn't an option for me because it breaks the multicat mod.

And as nice as LinksSQL would be, that $450 price tag is a little steep for a hobby site

[This message has been edited by BrianH (edited April 13, 2000).]

I have temporally fixed the problem.

Go into nph-build.cgi

Under
sub build_staggered {


I change the $limit build to a 2

Change my $limit = $in{'limit'} | | 2;


And then use an staggard build (auto)

See if that works.

Question who is hosting your site?

Thanks John

What is setting build limit to 2 going to change? I'm reluctant to try this right away because just as suddenly as it stopped working, it started again. It built correctly last time, so I'd rather not tempt fate

BTW, I'm hosted with Netmegs.

What it will do in the staggard build auto is
will only build two categories at a time.

So the server does not get over loaded.

When I first changed it I changed it to 5 which worked for a while.

Now I had to change it to 2.

Just keep in in mind if you run in to problems again.

Good Luck.