| Re: IDL without X11? [message #69574 is a reply to message #69569] |
Sat, 06 February 2010 16:57   |
![Karl[1] is currently offline](theme/default/images/xoffline.png.pagespeed.ic.XRkd1fkXye.png "Karl[1] is currently offline")
Karl[1]
Messages: 79
Registered: October 2005
|
Member |
|
|
On Feb 5, 10:40 pm, TonyL <anthony.legg...@bigpond.com> wrote:
> On Feb 6, 10:54 am, Karl <karl.w.schu...@gmail.com> wrote:
>
>
>
>> On Feb 5, 3:22 pm, nata <bernat.puigdomen...@gmail.com> wrote:
>
>>> Hi Karl,
>
>>> Thank you for your reply. Finally I got something.
>>> Now, I'm able to run the script but only for the root user (I don't
>>> know why). For the other users I got the following message:
>>> Warning: Cannot allocate colormap entry for default background.
>
>>> This is my final script:
>
>>> export DISPLAY=:2
>>> /usr/X11R6/bin/Xvfb :2 -screen 0 1152x900x16 &
>>> /usr/local/itt/idl70/bin/idl -rt=my_script.sav -args A B C
>
>>> nata
>
>>> PS I realized that I just have to define the screen one time (/usr/
>>> X11R6/bin/Xvfb :2 -screen 0 1152x900x16 &).
>>> Then, if the script will be executed each 10 minutes using the 1st and
>>> 3th lines it's enough
>
>> What got rid of the
>
>> X11 connection rejected because of wrong authentication.
>
>> message?
>
>> I would put a sleep for a few seconds after you kick off Xvfb to make
>> sure it gets started before IDL tries to talk to it.
>
>> Also, I'd put a killall Xvfb after IDL runs. There's no good reason
>> to let the server run. If you have to run it as root, you might want
>> to find some other way to kill it, so you don't kill someone else's
>> Xvfb.
>
>> You don't need a screen that large - you could go really tiny in w and
>> h, and 8 bits for d. This is just a dummy server and you'll save some
>> memory.
>
>> The colormap issue is probably caused by the root user and the "other"
>> users having a different set of X default or config files, or
>> something along those lines. The "other" users may have config files
>> in their home dirs that are trying to init a desktop or who knows
>> what. It is just a warning - the IDL client still runs without being
>> root, right? I wouldn't run it as root if I could avoid it.
>
>> It could be that one of these config files is asking for a 32-bit
>> color spec and your server is 16 bpp. You might try starting Xfvb
>> with 32 bpp. Or move all those X-related config files out of the way
>> in your home dir and see if that helps. Check for X-related env vars
>> as well.
>
> I use a cron job running on a Linux system that uses the Z-buffer for
> all graphics. That way you avoid any need to define a graphics device
> that has some kind of 'physical' existence. Z buffer uses system
> memory. Of course you will need to change a few commands with the Z
> buffer compared to a window device. I have use Xvfb before but i found
> it was a hassle if the PC was ever restarted and the Xvfb wasn't auto
> started.
>
> Tony
I think that one constraint on the original problem was not being
unable to modify the IDL code. I got the impression from the OP that
the app wasn't doing any graphics that were needed, but was doing a
call to WIDGET_BASE anyway. The best solution would be to make the
app Really non-graphical with some sort of startup option. But that
is apparently not a possibility here.
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
