Read jhs_default.ijs and you will see that it recommends copying to your private copy of jhs.ijs and making your changes there. This has a very good chance of being immune to subsequent updates from jsoftware.
On Sun, Jan 6, 2013 at 5:22 PM, greg heil <[email protected]> wrote: > Bill > > Thanks, knowing it was a J problem eliminated most paths. i was able > to find, and then change with great success, BIND with jfif: > > .../j64-701/addons/ide/jhs/config/jhs_default.ijs > > But i do wonder if there is anyway to make config changes that are > proofed against updates from, eg, ISI? i must thank Henry for pointing > out profilex, which i have used - but this has a rather limited scope. > > greg > ~krsnadas.org > > -- > > from: bill lam <[email protected]> > to: [email protected] > date: 6 January 2013 02:46 > subject: Re: [Jgeneral] LAN client/server for JHS > > You should edit the file ~config/jhs.ijs to set BIND to 'any' because > localhost (127.0.0.1) is always a loop-back of the computer. And add > password as recommended. > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
