I have added an "on stop, undo leave" around most of protop.p which I think will take care of this problem.

A new release is imminent - there is really just one more thing I'd like to squeeze in.

Nice. 🙂

I won't be rushing out that patch 😉

Got it. Fixed in patch 01.

@tom said in PT3.3s: cosmetic bug: splash screen:

I have not been able to reproduce the behavior that you describe.

I seem to have a talent for that.

Another data point for you: I just updated a 3.3r installation to 3.3s.

Saw this line in pt3inst.log:

protop.pf already exists in etc, saving a copy as /opt/protop/etc/protop.pf.04.19

The new protop.pf does contain -inp 16384. So it looks like all is well with pt3upd.sh.

It is ugly and annoying but it should be harmless.

The issue has been fixed in the next release.

@rob-fitzpatrick Yes, that is correct.

Zing!

This is almost always for one of these reasons:

The -tablerangesize or -indexrangesize parameters are not set to cover the active tables & indexes. The ChUI "T" command will show you what values are recommended and create a sample .pf file for you in the ProTop temp directory. Unfortunately you cannot change these values online. A db restart will be needed.

The activity on the tables and indexes does not meet the threshold criteria. You can review the thresholds on the portal "Resource" screen. For development and test environments you probably want very low values. For Production you want higher values -- a chart with 2,000 objects on it will be unusable (that is why we have a minimum activity threshold).

You should also verify that etc/pt3agent*.cfg has the TableActivity and IndexActivity data collectors enabled. If they are missing from ptInitDC then that data is not being sent to the portal.

I think I probably need more visuals. I'm not forming a picture in my head of what you are describing.

Portal v4 has a lot of enhancements to stuff like this. Real Soon Now.

Looks like it dates back to pt3.3n.

It is fixed now.

if ( not _Connect-device matches "*batch*" ) and _connect-batch <> "yes" then tt_Dashboard.con_self = tt_Dashboard.con_self + 1.

So "self" is counted for non-batch self-service connections. It (mostly) equates to local interactive connections.

Somehow I suspect that you are going to suggest that that might be sub-optimal 😉

$PROTOP/etc/NOTES_*.