John Desmond wrote:
>
> --- "Michael D. Schleif" <[EMAIL PROTECTED]> wrote:
> >
> > John Desmond wrote:
[ snip ]
> > First, un-tar weblet.lrp into a temporary directory.
> >
> > cd <temp>/var
> > rm -fr sh-log
> > ln -s /var/log sh-log
> >
> > At this point, rebuild weblet.lrp from this tree.
>
> Actually, I rebuild my .lrp's by setting up the system
> the way I want, hacking the package .list files and
> jiggling the handle. Your basic technique I can do as
> long as I don't have to recompile something :)
>
> I must have a different version... no sh-log directory
> in the package. I think it's dynamic.
Which version are you using? I have v1.1.2.
It can go anywhere you tell it in /etc/sh-httpd.conf -- this is default
in mine:
LOGFILE=/var/sh-log/sh-httpd.log
> Hmmmm. Important question: if I create a symlink and
> use the LRP package backup, will it save the symlink
> or the contents of the linked file? If the former,
> this will work for me.
Yes.
[ snip ]
> > Also, as you surmised, you will need to edit
> > /etc/cron.daily/multicron-d, modifying the call to
> > savelog in the
> > rotatelogs subroutine:
> >
> > savelog -p -c ${lrp_LOGS_DEPTH:-4} $LOG >/dev/null
> >
> > Of course, etc.lrp requires backup/update for these
> > changes to persist.
> >
> > What do you think?
>
> I'm going to have to play with this some more. It
> seems like putting the simlinks into weblet is the
> best bet if they can be backed up.
>
> You know, I just remembered why I dropped this in
> confusion a few weeks back. I was uncertain when the
> ramdisk gets created, and whether it would be there to
> receive files from a package installation during
> bootup. I was guessing that /etc/init.d/ramdisk
> wouldn't be run until after all the packages were read
> in; therefore, no ramdisk when weblet.lrp was read;
> so, no place for my symlinks. I was thinking that
> perhaps empty weblet logs and the links to them should
> be created in one of the bootup scripts like the links
> to 'ln' and 'grep', but that was such a dark forest, I
> wasn't ready to go in it.
I believe that (additional) ramdisks are created *after* root.lrp is
unrolled; but, *before* anything goes into /var/log or /tmp.
> > P.S. Charles, *why* isn't ``savelog -p'' the default
> > in Dachstein-CD? I
> > cannot figure out any reason to force ownership of
> > everything to
> > root:adm, as this current configuration does:
> >
> > savelog -g adm -m 640 -u root -c
> > ${lrp_LOGS_DEPTH:-4} $LOG >/dev/null
>
> I added the -p option back when I was experimenting
> with it and it didn't seem to help.
It works OK in my scenario.
--
Best Regards,
mds
mds resource
888.250.3987
Dare to fix things before they break . . .
Our capacity for understanding is inversely proportional to how much we
think we know. The more I know, the more I know I don't know . . .
_______________________________________________
Leaf-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user
