In message <[EMAIL PROTECTED]>,
David Cantrell <[EMAIL PROTECTED]> writes:
> On Wed, Feb 14, 2001 at 07:02:32PM +, Rob Partington wrote:
> > In message <006801c096a7$c4342370$390010ac@MACH2>,
> > "Mike Chamberlain" <[EMAIL PROTECTED]> writes:
> > > You could catch that by recording which inode
On Wed, Feb 14, 2001 at 07:02:32PM +, Rob Partington wrote:
> In message <006801c096a7$c4342370$390010ac@MACH2>,
> "Mike Chamberlain" <[EMAIL PROTECTED]> writes:
> > You could catch that by recording which inode's you'd already visited
> > in the chain. If it's one you've already seen, then it
In message <006801c096a7$c4342370$390010ac@MACH2>,
"Mike Chamberlain" <[EMAIL PROTECTED]> writes:
> You could catch that by recording which inode's you'd already visited
> in the chain. If it's one you've already seen, then it's a loop.
Where inode == inode/device pair, surely, since inodes are o
>
> If it's a symlink you should be able to readlink it (see
> perlfunc) to get
> the thing that it points at
> (although you'll have to do some file concatenation logic
> based on whether
> it's absolute or relative)
> And then you can test that (and work your way along the symlink chain,
> b
On Wed, Feb 14, 2001 at 04:07:34PM +, David Cantrell wrote:
> -l will tell we whether it's a symlink, but I can't see any way of telling
> what it points to
perldoc -f readlink
.robin.
On Wed, Feb 14, 2001 at 04:07:34PM +, David Cantrell wrote:
> Sorry for not talking about beer or buffy, but I'm stuck and need help.
>
> How can I easily tell whether a directory entry is a symlink to a symlink?
> -l will tell we whether it's a symlink, but I can't see any way of telling
> w
Sorry for not talking about beer or buffy, but I'm stuck and need help.
How can I easily tell whether a directory entry is a symlink to a symlink?
-l will tell we whether it's a symlink, but I can't see any way of telling
what it points to - and more importantly, what it is that it points to.
I