I did manage to figure out that link creates a hard link. And that I should have used
symlink() instead. But how would a hard link be detected
Every file is a link to a location on the filesystem, normally when you create a file, you allocate an entry on the filesystem and create a link. This happens implicitly when creating a file.
So every file has one hard link pointing to it. Additional hard links are just that, hard links, which happen to point to the same file structure inside the filesystem. When all hard links are removed, the file is still there,
but nothing points to it.
HTH
Op ma 17 dec. 2018 om 22:44 schreef Jeffry Killen <jekillen@xxxxxxxxxxx>:
I did manage to figure out that link creates a hard link. And that I should have used
symlink() instead. But how would a hard link be detected?
JK
> On Dec 17, 2018, at 1:27 PM, Jeffry Killen <jekillen@xxxxxxxxxxx> wrote:
>
> Hello:
>
> I am trying to get a feel for the difference
> between is_link and is_file.
>
> So I ran this code: the result is in comment block at the bottom
>
> <?php
> if(link('index.php', 'indexLink') === false)
> {
> print "link failed";
> }
> else
> {
> $_linkRes = 'false';
> $_fileRes = 'false';
> if(is_link('indexLink'))
> {
> $_linkRes = 'true';
> }
> else if(is_file('indexLink'))
> {
> $_fileRes = 'true';
> }
> print 'indexLink: link; '.$_linkRes."<br>";
> print 'indexLink: file; '.$_fileRes;
> }
> /*
> output:
> indexLink: link; false
> indexLink: file; true
> */
> ?>
>
> Why is it returning false for link and true for file?
>
> This is an apache/php v 5.3x installation on Mac Yosemite.
>
> Forgive my ignorance, but I have not worked with links up
> to this point. If I load http://localhost/indexLink I get a ton
> of raw code and some html rendered.
>
> Thank you for time and attention
> JK
