OK, I forgot, that I actually had a user and group named asf (I thought
tar would ignore their non-existance).
But I agree with William, that we should instead use a general purpose
user and group exactly because of the reasons given by him.
If a non-root user extracts the tarball, his
Rainer Jung wrote:
OK, I forgot, that I actually had a user and group named asf (I thought
tar would ignore their non-existance).
All in all I would suggest root:bin to.
I used root:users instead.
Think the users group exists on all *nixes.
Regards,
Mladen.
Mladen Turk wrote:
Rainer Jung wrote:
OK, I forgot, that I actually had a user and group named asf (I
thought tar would ignore their non-existance).
All in all I would suggest root:bin to.
I used root:users instead.
Think the users group exists on all *nixes.
So does bin. users has a
Author: mturk
Date: Mon Apr 2 05:57:24 2007
New Revision: 524777
URL: http://svn.apache.org/viewvc?view=revrev=524777
Log:
Do not try to make the release on the hosts where tar doesn't support cfz.
Modified:
tomcat/connectors/trunk/jk/tools/jkrelease.sh
Modified:
Hi Mladen,
did you delete setting owner and group by accident from the release script?
[EMAIL PROTECTED] schrieb:
# Pack and sign
-tar cvf ${JK_DIST}.tar --owner=${JK_OWNER} --group=${JK_GROUP} ${JK_DIST}
-gzip ${JK_DIST}.tar
+tar cfz ${JK_DIST}.tar.gz ${JK_DIST}
perl
Mladen Turk wrote:
Rainer Jung wrote:
Hi Mladen,
did you delete setting owner and group by accident from the release
script?
No, I did it by purpose. I don't have user or group named asf, so the tar
fails. What would be a purpose of it anyhow, and how would you ensure
that the same user
