Re: [bu-users] installed as user; bu by root works but no log

[Vincent S. <bu...@hi...>]

On Fri, Sep 01, 2006 at 03:01:45PM -0700, jack byers wrote:
> [byers@bootp bu-3.4-beta]$
> byers@bootp bu]$ pwd
> /home/byers/pkg/var/log/bu
> [byers@bootp bu]$ ls
> log.060901
> [byers@bootp bu]
> only the one log file for my test case running as user byers
> 
> my other test case running as root also worked, but no log file
> 
> running   2.6.17-1.2174_FC5
> 
> near end of install a couple of error msgs:
> 
> /home/byers/pkg/libexec/bu/VERSION
> strip: unable to copy file '/home/byers/pkg/libexec/bu/usleep' reason:
> Permission denied
> strip: unable to copy file '/home/byers/pkg/libexec/bu/realpath' reason:
> Permission denied
> /home/byers/pkg/share/doc/bu-3.4-beta/...
> /home/byers/pkg/etc/bu/Include
> /home/byers/pkg/etc/bu/Enclude
> 
> Bu is now installed.
> 
> are those 2 failed  'copy'  related to missing log file?
> 
> do i have to install as root  to get log files from running bu as root?
> 
> thanks for any help, advice
> Jack

Hi Jack.

I tested again as a normal user and did not reproduce your problem.
I first thought you may have a directory that does not have write access
somewhere in the /home/byers/pkg/ tree or something, but it was
apparently able to install the files in the ~/pkg/libexec/bu directory
in order to get far enough to strip them.  The install script will abort
if there are in errors installing the files but it does not check the
return of the strip command because it assumes there are no permission
problems or it would have already aborted.  It is not getting any errors 
installing any of the files before or after the strip command, so the
install script does not detect any problem.

Not being stripped will not affect the functionality of the utilities.

I would say you may have a broken strip utility.  However, that would
not explain your getting one log file and then none after that.
Permission problems would also not explain that.  It sounds like you may
be having a lower level system problem relating to the kernel or file
system, etc.  Considering some of the strange problems we have had in
the past with Linux that were related to memory management, among other
things (part of the reason we changed to BSD several years ago), I am
going to sound like a MicroShafter here.  Try rebooting and see if the
problem goes away.  

I hope this helps.  Let me know how it goes or if you discover the
problem.


-- 
Vincent Stemen
Avoid the VeriSign/Network Solutions domain registration trap!
Read how Network Solutions (NSI) was involved in stealing our domain name.
http://inetaddresses.net/about_NSI.html