Re: Trouble setting configuration file (IB_CONFIG ignored?)

dave penkler <[email protected]> writes:

> It looks like your setup is still using the default gpib.conf file which
> indeed calls the board by the name  "violet".
> If you run gpib_config with a gpib.conf argument different from the
> --sysconfdir path used in your build (default /usr/local/etc) you must set
> the IB_CONFIG environment variable.
>
> This worked for me:
>
> $ sudo  gpib_config -f /home/dave/gpib/gpib.conf
> $ export IB_CONFIG=/home/dave/gpib/gpib.conf
> $ ibtest
> Do you wish to open a (d)evice or an interface (b)oard?
>         (you probably want to open a device): b
> enter name of interface board (or device) you wish to open: gpib0
> trying to open board named 'gpib0'
> You can:
>         w(a)it for an event
>         write (c)ommand bytes to bus (system controller only)
>         send (d)evice clear (device only)
>         change remote (e)nable line (system controller only)
>         (g)o to standby (release ATN line, system controller only)
>         send (i)nterface clear (system controller only)
>        ... etc
>
> The default file in my setup in /etc also has "violet" as the board name.
> Not sure why it is not working for you.

Thanks for the response Dave.

Unfortunately this is what I tried. Do I possibly need to reload the
kernel module?

The default gpib.conf file (from the template, not the one I select with
IB_CONFIG or gpib_config -f) is read-only on my distribution. Is it ok
that linux-gpib cannot edit this file?

Also, I tried patching linux-gpib to substitute the template
configuration for my own configuration. This achieved the desired
result, but it's not a great solution.

Matt