--- "Michael D. Schleif" <[EMAIL PROTECTED]> wrote:
>
> John Desmond wrote:
> >
......
> (One of
> > the commands buried in the scripts has a
> 'preserve'
> > option which I think is supposed to keep this from
> > happening but it didn't seem to work)
> >
.......
> > independently? Or can someone point out how to set
> up
> > symlinks during the boot-up?
>
> Here's how I do it; but, bear in mind, this involves
> re-building
> weblet.lrp and ramlog.lrp. I rebuild many LRP's and
> also rebuild the CD
> image so nothing is on my floppy, except those files
> required to boot
> (e.g., contents of bootdisk.bin.)
>
I'm a little embarrassed to admit that the only linux
system I have is the LRP. I administer the box and CM
my builds from a Windoze station.
>
> 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.
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.
> I work on a full install Debian system; so, I have
> no idea how to do
> this on your Dachstein system; but, making these
> changes to your
> firewall and lrcfg/backup should also work.
>
> Next, un-tar ramlog.lrp (or, ramdisk.lrp should also
> work) into a
> temporary directory. I'm not clear what to do if
> /var/log is *not* on
> its own ramdisk.
>
> cd <temp>/var/log
> rm sh-httpd.log (it's probably *not* there)
> >sh-httpd.log
> chown 50:4 sh-httpd.log
> chmod 640 *
This looks like the opposite of what I was doing. I
had the file in /var/sh-log and the link in /var/log.
>
> At this point, rebuild ramlog.lrp from this tree.
>
> 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.
>
> 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.
> --
>
> Best Regards,
>
> mds
Thanks.
-John
__________________________________________________
Do You Yahoo!?
Make a great connection at Yahoo! Personals.
http://personals.yahoo.com
_______________________________________________
Leaf-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user
