Koozali.org: home of the SME Server

Legacy Forums => Experienced User Forum => Topic started by: Black on August 16, 2005, 06:22:57 AM

Title: Is there any Order to the etc/e-smith/templates-custom dir??
Post by: Black on August 16, 2005, 06:22:57 AM
Why are there so many darn directorys??

atalk         dovecot.conf     hosts.allow  mail               openldap      radiusclient  squid         ups
clamd.conf    e-smith          hosts.deny   mime.types         pam.d         rc.d          ssh           xinetd.conf
cron.d        fetchmail        httpd        modprobe.conf      php.ini       resolv.conf   startmail     yum.conf
crontab       flexbackup.conf  identd.masq  Muttrc             pine.conf     samba         statusreport
dhcpc         freshclam.conf   inittab      my.cnf             ppp           securetty     sysconfig
dhcpd.conf    fstab            ippp.conf    nsswitch.conf      pptpd.conf    services      sysctl.conf
diald         ftpusers         logrotate.d  ntp                printcap      shells        syslog.conf
diald.conf    HOSTNAME         lpd.perms    ntp.conf           proftpd.conf  smb.conf      tcprules
diald.filter  hosts            lynx.cfg     oidentd_masq.conf  raddb         smbpasswd     ulogd.conf
...


an within each of those are more and more directorys.

How does one know the order in which they copied the original /etc directory?
Title: Re: Is there any Order to the etc/e-smith/templates-custom d
Post by: gordonr on August 16, 2005, 07:14:55 AM
Quote from: "Black"
Why are there so many darn directorys??


There is one directory per configuration file, and there are a lot of configuration files in the system.

Quote from: "Black"

How does one know the order in which they copied the original /etc directory?


The template fragments in the directories are processed in asciibetical order. Only the configuration files related to the event in question are processed.

In 7.0alpha it's driven by a directory tree in 'templates2expand'. For previous releases, you need to check the  various action scripts in the relevant event directory.