Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!samsung!umich!terminator!pisa.ifs.umich.edu!rees
From: rees@pisa.ifs.umich.edu (Jim Rees)
Newsgroups: comp.sys.apollo
Subject: Re: Bug with cp -r and ACLs (long)
Message-ID: <4fae2d9d.1bc5b@pisa.ifs.umich.edu>
Date: 7 Feb 91 23:58:31 GMT
References: <1991Feb3.001547.8838@mentorg.com> <9102061706.aa14313@concour.cs.concordia.ca> <1991Feb7.183550.8329@alchemy.chem.utoronto.ca>
Sender: usenet@terminator.cc.umich.edu (usenet news)
Reply-To: rees@citi.umich.edu (Jim Rees)
Organization: University of Michigan IFS Project
Lines: 15

In article <1991Feb7.183550.8329@alchemy.chem.utoronto.ca>, system@alchemy.chem.utoronto.ca (System Admin (Mike Peterson)) writes:

  Unfortunately I have to agree with this statement - there is however the
  fact that HP/Apollo advertises that any/all environments can be used, where
  there are cases where this is simply not the case. A prime example is
  '/com/sigp', which is needed to kill processes that won't die with 'kill
  -9' (which is the untrappable UNIX kill signal).

Not a good example.  You should never blast a process unless you plan to
shut down your node.  And if you're going to shut down, then you don't need
to blast.

The 'cp -r' problem is just a bug.  And there is a bsd workaround (piped
tar, which is the traditional way to copy a tree in Unix anyway).  Do you
have other examples?