filepro menus and Ctrl-S - maybe Anzio setting?

[Kenneth Brody]

On 12/9/2010 8:11 PM, Bruce Easton wrote:
> I wanted to see this first-hand, so I loaded demo of latest Anzio Lite onto
> this vista partition, accepting, I think all the defaults, and saying
> yes to
> older SCO mode question.  Very easy install.  And filepro's dpromenu came
> up in color beautifully.   Found one of the 19-option menus that had
> been adjusted to less than 19 lines and put it back to 19 lines.
>
> Sure enough, works OK from prompt or from option G on dpromenu,
> but from a calling menu - as George said, 'LOCK' appears at lower
> right and you have to key Alt-U to be able to navigate/select anything.
>
> (fp 5.0.14 by the way)
>
> Then things got really interesting.  I took a look around and found that
> some of the filepro executables (including dmakemenu, runmenu) did
> not get the SUID bit set correctly from the setperms prog.  So I

Well, runmenu isn't supposed to have the setuid bit on.

> referenced another Linux box, did an "ls -l|grep rws" standing in fp and
> lib to help refresh my memory and proceeded to fix these perms.
> Well that did not help.
[...]
> Then I looked at the perms on the problem menu file itself. It was 777.
> I thought that it didn't need and probably should have that - it was
> already owned by filepro, so I changed it to 600.  Boom.  It no
> longer had a problem!  So for kicks, I changed the perms on the
> newly ported menu to 777 and walla - Anzio started turning the lock
> on on that menu.  (And by the way - this all as far as I can tell happens
> on menus with 19 items, but i'm suspicious that maybe this is the only
> obvious side-effect and that these ctrl chars in all menus are not

Which makes even less sense than before.  The only difference that 
permissions on menu files will make to runmenu is whether or not it can be 
read.  There should be absolutely no difference to runmenu between the 644 
that it should be and the 777 you changed it to.

> being treated properly - I mean we know these files are all supposed
> to have one of those chars at the top right?)

What do you mean "one of those chars"?  The top-right of the screen will be 
the "menu version" string that you set in dmakemenu.  The value stored in 
the first byte of the menu file is never shown by filePro.

[...]
> I also re-saved the problem menu once it had 'correct' perms, but
> it did not change its size which is still different than the other
> one that looks and behaves the same way under the same
> circumstances, but has a different size.

What sizes are you seeing for menus?  They should all be 4719.

[...]
> Anyway, that's what I tried - maybe this will ring a bell with
> someone.  So, as it stands, if the perms of menu files (not the
> scripts) are 600, then they are OK.

No, they're not.  They should be 644, or else only root and filePro can use 
them.  (Unless, that is, you set the setuid bit in runmenu, which is also 
wrong.)

Run setperms.

[...]

-- 
Kenneth Brody