Thanks all for the help so far. This is the news.

The problem with onbar seems to have been fixed. It turned out to be
that I had TAPEDEV set to /dev/null in the onconfig file. That has
got me very confused as I am not using ontape so why does onbar look
at the TAPEDEV. (I guess some developer somewhere has a good reason
for that - but it doesn't make life any easier).

I am now getting lots of the shmdt: errno 22 messages, so it looks
like that could be a separate problem.

As to the completion codes - I still can't find out what 156 means.
As my alter ego Malc_p pointed out the manual lists 155 and 157 but
not 156. And how are we supposed to find this in the manual. I
looked in the index for error codes, and even completion codes. In
onbar they are RETURN codes - I guess I should have known that as the
error message does say RETURNING but I searched the document for
returning and that didn't find anything. I even looked in the section
marked "Troubleshooting" but that doesn't include analysing the log.

regards

Malcolm

"Malc" <malc_p@btinternet.com> wrote in message news:<c6rlt8$pbq$1@sparta.btinternet.com>...
> "malcolm" <malcolm.weallans@btopenworld.com> wrote in message
> news:3efc1745.0404290751.220b0316@posting.google.c om...
> > I am having fun trying to get onbar to work on IDS 9.40 running on
> > Linux.
> >
> > Whenever I run onbar -b -L I get shmdt: errno = 22, and the
> > bar_act.log indicates that onbar has completed with code 156. Where
> > can I find what these error codes mean?
> >
>
> Have a look at the Backup and restore guide, chapter 11.
> Oh, bugger.
> Code 155 and 157 are listed..... gues which one ain't?
>
> Malc_p