[daip] Start Up Issue

[Eric Greisen]

Kevin Dimond wrote:
> Sorry for the late reply, here is a copy of the script. I guess I'm 
> confused by the fact aipstv isn't showing up and that it asks for a user 
> ID number which I don't remember setting up. Also, x11 windows open up 
> called AIPS_MSGSRV and AIPS_TEKSRV that won't allow me to enter 
> anything. I haven't been able to apply the other suggestions you made, 
> but I'm thinking it might just be easier to uninstall and re-install 
> AIPS instead of trying to fix installation mistakes.

I think that installation mistkaes may not be so important.  The MSGSRV 
and TEKSRV windows are supposed to appear - but they are OUTPUT windows 
not input.  When a task runs it puts its messages in the MSGSRV window 
so that your main xterm does not get crowded with them.  The TEKSRV is a 
line drawing Tektronix emulation for certain tasks which do that (few 
these days).

Looking at your Start file there are several things going on:

1. Try starting aips with "aips tv=local" - your computer seems not to 
be able to recognize itself by its inet address.  This is not uncommon 
for laptops.  If your machine is the only one that uses this 
installation, perhaps you should have said laptop yes on that 
installation question.  Then you would be called LOCALHOST rather than 
the long messy name you are actually using and LOCALHOST is more readily 
recognized in the gethostbyname service.

2. It appears that FILAIP and POPSGN (probably) did not run at the end 
of the installation.  Say
     RUN FILAIP
     8   2
     RUN POPSGN
     0  POPSDAT  TST
     <cr>
to run these setup tasks.

3. See the aips manager web page:
       http://www.aips.nrao.edu/aipsmgr/
    for the shared memory failure - I attach the text here however

After you follow the instructions below appropriate to your release of 
the Mac operating system, you must re-boot the computer. The control 
file for shared memory is read at boot time only. Note that a re-boot is 
not simply logging the current user out and then back in. You must do a 
full restart.

The default Mac system limits shared memory pages to 4 Mbytes. When XAS 
starts it tells you that it is making a screen x pixels by y pixels. The 
memory you will need is at least 4 x y bytes, but this rounds upward 
rapidly. For the new large screens this is more than 8 Mbytes. On 10.3 
and 10.4 systems, you can change this limit by changing (as root or 
admin) the rc file in /etc, adjusting the kern.sysv.shm* line to

          #Setting the shared memory to something a bit more reasonable.
             sysctl -w kern.sysv.shmmax=10485760
             sysctl -w kern.sysv.shmmin=1
             sysctl -w kern.sysv.shmmni=32
             sysctl -w kern.sysv.shmseg=8
             sysctl -w kern.sysv.shmall=4096


If you are really lucky and have a 30-inch screen (2550 by 1500 pixels) 
then you will have to make the shmmax line even larger

             sysctl -w kern.sysv.shmmax=16777216


Note that these are upper limits, so it does not hurt to set a value 
that might be larger than necessary for your system. The shmmax must be 
an integer multiple of the shmall which must be a power of 2 >= 1024. A 
3190 by 958 screen was found to require the larger value above. I think 
this comes by n times (4096 / 4 bytes/word) has to be > 3190 leading to 
4096 words per row. Then 958 * 4096 * 4 bytes = 15695872 or just a bit 
less than the 16777216.

On the latest "leopard", "snow leopard", "lion", and "mountain lion" (X 
10.5-10.8) systems, /etc/rc is gone and creating it will have no effect. 
You need to create an /etc/sysctl.conf file and put the values in it,

             kern.sysv.shmmax=10485760
             kern.sysv.shmmin=1
             kern.sysv.shmmni=32
             kern.sysv.shmseg=8
             kern.sysv.shmall=4096


You should use the values you had when you were running tiger. Those 
could be in /Previous\ System/etc/rc, assuming you have "Previous 
System". So three different OS upgrades and three different ways to 
adjust the default shared memory. Note: You will need to reboot the 
system for the change in shared memory to take place. You can check if 
the shared memory changes happened by typing "sysctl kern.sysv" in a 
terminal or xterm window. Look for the kern.sysv.shm* values. If the 
values have not changed, make sure you haven't inadvertently left in 
"sysctl -w" in the /etc/sysctl.conf file or mis-typed one of the values. 
If the /etc/sysctl.conf file is not properly formatted, or shmmax is not 
an integer multiple of shmall, the shared memory will not be adjusted 
after the reboot.



Eric Greisen