Hi All,
Why so many of the file permissions in a freshly compiled installation so
crazy?
Brief example from lib/ :
-rwsrwsrwt 1 2372 2200 62983 2010-06-11 11:37 activation-1.1.jar
-rwsrwsrwt 1 2372 2200 1514270 2011-02-02 12:37 ant-1.8.1.jar
-rwsrwsrwt 1 2372 2200 12312 2011-02-02 12:37
On 9/06/11 1:30 AM, jcat wrote:
> Hi All,
>
>
>
> Why so many of the file permissions in a freshly compiled installation so
> crazy?
>
> Brief example from lib/ :
>
> -rwsrwsrwt 1 2372 2200 62983 2010-06-11 11:37 activation-1.1.jar
> -rwsrwsrwt 1 2372 2200 1514270 2011-02-02 12:37 ant-1.8.
My umask is pretty normal, 0022 or 0027
The UIDs are because it was compiled on a different system to the one
I've untared it on.
Some things are fine, like the webapps for example.
I can't think how my environment would be doing this to some things
only.
It's certainly strange :)
Cheers,
Just
There was a bug opened on this (NMS-4682). Its fixed on master, but doesn’t
appear to be on the 1.8 branch.
From: jcat [mailto:j...@nysasounds.co.uk]
Sent: Wednesday, June 08, 2011 1:55 PM
To: opennms-devel@lists.sourceforge.net
Subject: Re: [opennms-devel] OpenNMS file default build file permiss
Yeah, but the permissions in the build scripts were 755, and are now
644; that doesn't really explain permissions like 1777 that jcat was seeing.
jcat: definitely strange. Is it like that in the original, before
tarring and extracting somewhere else?
Craig
On 09/06/11 07:41, Roskens, Ronald wro
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 6/8/11 1:17 PM, Craig Miskell wrote:
> Yeah, but the permissions in the build scripts were 755, and are now
> 644; that doesn't really explain permissions like 1777 that jcat was
seeing.
>
> jcat: definitely strange. Is it like that in the original
