[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [libtool-2.2.2] testsuite on NFS mount on AIX
From: |
Michael Haubenwallner |
Subject: |
Re: [libtool-2.2.2] testsuite on NFS mount on AIX |
Date: |
Mon, 21 Apr 2008 09:28:59 +0200 |
On Sat, 2008-04-19 at 18:40 +0200, Ralf Wildenhues wrote:
> Hello Michael,
>
> * Michael Haubenwallner wrote on Fri, Apr 18, 2008 at 04:59:43PM CEST:
> >
> > when doing the libtool testsuite in some NFS mounted directory on AIX,
> > the output is full of lines looking like:
> > rm: cannot remove directory
> > `/nfsmount/libtool-2.2.2/tests/testsuite.dir/25/broken/lib': File exists
> >
> > Although it does not cause any additional test to fail, it's still ugly.
>
> Yep.
>
> > This is because AIX keeps shared libraries in use for some time even if
> > there are no more programs using it.
>
> Yep, I knew that.
>
> > But this only applies to shared libraries having read (execute?)
> > permission for 'other'.
>
> Ha! I wasn't aware of that. Thank you!
>
> I've confirmed on AIX 5.3 that read permissions are what counts, but it
> shouldn't hurt removing the others as well.
>
> > So adding an 'umask 0007' (or 0077) early in testsuite.at can help here.
>
> I'd like to avoid giving more permissions if the user set, say, umask
> 077 before. Thus let's just remove those for others. I've applied the
> patch below and put you in THANKS.
Thank you!
> +case $host_os in
> +aix*) umask o-rwx ;;
As I was not aware of symbolics with umask yet, and being paranoid, I've
tried that: Unfortunately, it depends on the shell if umask with
symbolics works: It works with bash as well as AIX' /bin/ksh, while it
does not work with AIX' /bin/sh, but without any failure notice - it
just sets umask to 0:
$ /bin/sh
sh$ umask
0007
sh$ umask o-rwx; umask
0000
sh$ umask 007; umask
0007
sh$ umask junk; umask
0000
sh$
So we want to use the numeric umask here...
Thanks!
/haubi/