Actually, look in the man page for chmod (vs. ls) for explanation of that 't'
permission. On a file (which this is, of course) is simply says keep the "text"
portion in memory upon exit. The real question is why are the execute permissions
set for a tar ball?!!
By the way, the "text" is the executable code portion of a binary. Again, a tar
ball has no executable code for the kernel so that perm is really gonna do nothing.
You should just reset the perms to read or read/write to be tidy after creating it
IMHO.
Hope this helps.
-Ron
> snip
> Something interesting:
>
> using the same command to send the output file to itself on gdu also creates the
> funky permissions
>
> [root@gdu1 /tmp]# tar -cvf bhughes@gdu1:/tmp/gdutest.tar
> --rsh-command=/usr/bin/ssh /home/bhughes
>
> yields:
> -rw-r-xr-T 1 bhughes bhughes 7208960 Apr 21 10:38 gdutest.tar
>
> hmmm. any Ideas anyone?
>
> Bret
>
> >
> > | 2. what the heck is T anyway?
> >
> > "T" means "t" but that the underlying "x" bit isn't set. This is described in
> > the manual for "ls", like you might expect.
>
> Thanks info had it but not man where I looked last night.
>
> --
> To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
> as the Subject.
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
