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

[jack b. <by...@gm...>]

 Hi Vincent,
blush!,
mea culpa
all the logs for the 'missing' root logs show up
when i look in that
$bu_log_dir setting in roots~/.burc file.
[root@bootp ~]# cd /var/log/bu
[root@bootp bu]# pwd
/var/log/bu
[root@bootp bu]# ls -l
total 524
-rw-r----- 1 root root  69379 Sep  1 13:52 log.060901
-rw-r----- 1 root root    346 Sep  2 07:19 log.060902
-rw-r----- 1 root root    331 Sep  2 10:44 log.060902-1
-rw-r----- 1 root root    342 Sep  2 14:22 log.060902-2
-rw-r----- 1 root root 435826 Sep  2 14:36 log.060902-3
-rw-r----- 1 root root    295 Sep  3 07:49 log.060903
-rw-r----- 1 root root    317 Sep  3 15:29 log.060903-1
[root@bootp bu]#

that was my entire problem re the logs
I had naively assumed that since
bu was installed by user byers
then all the logs would appear under byers/pkg...

so it seems bu is working perfectly for me
both as user byers and as root


this system is a fresh install of fedora core 5,
no old 2.8 bu on it

when i run bu as root
i just use  'bu ...'
not the full path

thanks for your prompt replies
Jack





On 9/3/06, Vincent Stemen <bu...@hi...> wrote:
>
> Hi Jack.
>
> On Sun, Sep 03, 2006 at 08:17:04AM -0700, jack byers wrote:
> > Hi Vincent,
> > thanks much for your response
> >
> > i tried rebooting, no change
> > still see log file if doing the bu from user byers
> > and dont see the log file from user root
> >
> > I may not have been clear enough in first msg,
> > it is not that i see a log file on first bu
> > and none on 2nd bu
> > but consistently
> > -log file appears if run as byers
> > -log file  does not  appear if run as root
>
> I have never seen bu do this.  Are you sure you are looking in the right
> place for the log files?  Double check the $bu_log_dir setting in roots
> ~/.burc file.  Do you get any errors when you run bu?  It writes the
> logs by appending with simple redirect with append ">> $Log" in the
> script and all preceding directories are always made if they do not
> already exist.  If there were any problems writing to it you should get
> error messages.
>
> I am still suspicious of some other strange underlying system problem
> though because of those permission errors you got from _strip_ during
> installation.  You should not have gotten any such error after
> successfully installing the files there.
>
> Do you have any other machines you can install and test bu on?  That
> would confirm bu works and that you don't have a corrupt copy or
> anything.
>
> A long directory listing of the log directory of multiple bu runs in the
> same day should look something like this (from my machine).
>
> $ ll /var/log/bu/
> -rw-r-----  1 vince  wheel  -    539 Sep  3 03:20 log.060903
> -rw-r-----  1 vince  wheel  -    359 Sep  3 03:22 log.060903-1
> -rw-r-----  1 vince  wheel  -    569 Sep  3 03:22 log.060903-2
> -rw-r-----  1 vince  wheel  -    876 Sep  3 16:09 log.060903-3
>
> The default log location for a non-root user installation (if you have
> not changed ~/.burc, in the case of user, "byers") would be
>
>     ~/byers/pkg/var/log/bu
>
>
> > in the past i think i installed as root  v 2.8 i think
> >
> > so maybe i should just uninstall
> > and reinstall as root ?
>
> When you have the problem, are you running bu as root but from a user
> installation in byers home directory?  If so, are you specifying the
> whole path to bu (ie ~byers/pkg/bin/bu).  If not, are you sure there is
> not an installation of an old version of bu somewhere in your command
> path?  I did change the rc file format and the default location of the
> log files at one point, so an old version of bu might not be getting the
> location you are expecting for the log files.
>
>
> > Jack
> >
> > p.s.   not sure if I am replying correctly; it seems to be addressed
> > to you only, not the mailinig list
>
>
> Yes it was to me only.  I don't know what mailer you use, but I use mutt
> and it has a list reply option that will reply to a mailing list rather
> than the original author directly.  Perhaps yours has something similar.
>
>
> --
> 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
>