🚀 go-pugleaf

In <1991Jan01.211524.18484@kithrup.COM> sef@kithrup.COM 
  (Sean Eric Fagan) writes:
 >In <SCHULTE.91Jan1200851@sun0.thp.uni-koeln.de> schulte@thp.uni-koeln.de 
 > (Martin Schulte) writes:
 >>>But the big question - which I have reported to the authors - is what is
 >>>the call to remove _really_ supposed to be?  Remove() deletes files.  It
 >>                                              ^^^^^^^^
 >>>doesn't look like that is what is wanted here at all.
 >>
 >>I only took a short look on the sources, why do you think it should remove
 >>files ?
 >
 >kithrup 1> man S remove
 >
 >
 >     REMOVE(S)		       UNIX System V		     REMOVE(S)
 >
 >     Name
 >	  remove - removes filename
 >
 >     Syntax
 >	  #include <stdio.h>
 >	  int remove (filename)
 >	  const	char *filename;
...
 >Seems to me that that pretty much indicates that remove() removes files,
 >don't you think?

It would indicate that if I had that particular function in libc, but since I
don't...  Now take a look at another case:

% man remove
No manual entry for `remove'.

This looks like a System-Vism.  Most systems that I've seen do however have 
unlink(2).  (This is a BSD based system.)

% man unlink

UNLINK(2)               COMMAND REFERENCE               UNLINK(2)


NAME
     unlink - remove directory entry

SYNOPSIS
     unlink(path)
     char *path;

DESCRIPTION
     Unlink removes the entry for the file path from its
     directory.  If this entry was the last link to the file, and
     no process has the file open, then all resources associated
     with the file are reclaimed.  If, however, the file was open
     in any process, the actual resource reclamation is delayed
     until it is closed, even though the directory entry has
     disappeared.
...

	-Jeff
-- 
Jeff Beadles		jeff@onion.pdx.com