Hi Lonnie,

I add the PERSISTLOG parameter to /mnt/kd/rc.conf.d/user.conf and now it works.
Does it mean, that mnt/kd/rc.conf is ignored as soon as there is a file 
/mnt/kd/rc.conf.d/user.conf and so I have to add each parameter not available 
from the web gui here in user.conf to make it work?

Best regards

Stefan Ulm
Technical Department | Research & Development
stefan....@divus.eu

      
      


DIVUS Headquarters Pillhof 51 . I-39057 Eppan (Südtirol) . Tel. +39 0471 633 
662 . Fax. +39 0471 631 829
www.divus.eu . Privacy: http://www.divus.eu/media/DivusPrivacy.pdf


-----Ursprüngliche Nachricht-----
Von: Lonnie Abelbeck [mailto:li...@lonnie.abelbeck.com] 
Gesendet: Donnerstag, 17. November 2016 14:12
An: AstLinux Users Mailing List <astlinux-users@lists.sourceforge.net>
Betreff: Re: [Astlinux-users] permanent save log files

Stefan,

> Found the cause oft he problem.
> The file to edit is /stat/etc/rc.conf
> 
> Modified the parameter there it works.

Never edit the /stat/etc/rc.conf file.

If you need to set a rc.conf variable (not set by the web interface), edit 
/mnt/kd/rc.conf.d/user.conf instead (which also can be edited via "Advanced 
Configuration: { Edit User Variables }" in the Network tab).

> # show-union
...
> /oldroot/mnt/asturw/etc/rc


I can't think of a reason to ever edit /etc/rc, except for experimental 
development work.  See what you changed with the command:
--
diff -u /oldroot/mnt/asturo/etc/rc /oldroot/mnt/asturw/etc/rc
--
This compares the read-only base firmware image to your local overlay file 
system for the file /etc/rc .

If there are no differences (file got accidentally touched) or changes you no 
longer want, restore /etc/rc to the default by:
--
rm /oldroot/mnt/asturw/etc/rc
--

If you need to perform actions at startup, add executable scripts 
/mnt/kd/rc.elocal or /mnt/kd/rc.local to perform startup actions, the only 
difference is rc.elocal occurs earlier than rc.local in the startup sequence 
(after network is up).


In summary, if you need to edit a file to make a change in AstLinux, the first 
thing to ask yourself is "what /mnt/kd/ file should I edit".

One of the great benefits of AstLinux is an upgradable firmware image, while it 
is possible to edit system files, that can cause future issues as you will have 
a 'stale' version of that file forever more.

Lonnie



On Nov 17, 2016, at 4:13 AM, Stefan Ulm <s....@divus.biz> wrote:

> Found the cause oft he problem.
> The file to edit is /stat/etc/rc.conf
> 
> Modified the parameter there it works.
> 
> 
> Best regards
> 
> Stefan Ulm
> Technical Department | Research & Development stefan....@divus.eu


------------------------------------------------------------------------------
_______________________________________________
Astlinux-users mailing list
Astlinux-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/astlinux-users

Donations to support AstLinux are graciously accepted via PayPal to 
pay...@krisk.org.

------------------------------------------------------------------------------
_______________________________________________
Astlinux-users mailing list
Astlinux-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/astlinux-users

Donations to support AstLinux are graciously accepted via PayPal to 
pay...@krisk.org.

Reply via email to