On Jul 30, 2012, at 6:51 PM, Michael Knill wrote: > To the group > > I am just trying to get my head around rc.conf and rc.conf.d files.
/mnt/kd/rc.conf is always ignored if the directory /mnt/kd/rc.conf.d/ exists. The web interface requires, creates the directory /mnt/kd/rc.conf.d/ . The file /mnt/kd/rc.conf.d/user.conf is the place to put advanced, custom variable definitions. Since the /mnt/kd/rc.conf.d/*.conf files are combined alphabetically, the user.conf gets applied last so it supersedes all others. The /stat/etc/rc.conf file sets the default values (and documentation). For your question, VLANCOS="yes" is required to enable 802.1p CoS on VLAN. (Using shell scripting rules.) The default value of VLANCOS in /stat/etc/rc.conf is unset: #VLANCOS="yes" unset, which is treated by the code the same state as VLANCOS="no" or VLANCOS="" While DHCPRANGE is unset by default in /stat/etc/rc.conf: #DHCPRANGE="100:220" The code will use 100:220 if DHCPRANGE is unset. Lonnie > > My understanding is that the rc.conf.d *.conf files are appended to the > /mnt/kd/rc.conf file in alphabetical order to create the final rc.conf file. > My questions are however: > > 1) Why are some variables not hashed in rc.conf? Don't all values have > defaults e.g. DHCPRANGE="100:220" > 2) When the GUI sets a variable to NULL, does that mean use the default e.g. > does VLANCOS="" mean yes (use the default) or no (not "yes") > > Thanks guys. > Mike ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Astlinux-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to [email protected].
