Charlie Brady <[EMAIL PROTECTED]> said:
> No. You didn't have to be nasty. You could have dealt with the issues we > raised. My apologizes Charlie and Gordon. Let's deal with the issues raised... > As Daniel pointed out, there will be some files for which '#' > prefixed lines are not treated as comments. So we could then simply 'identify' which files this is an issue with and not comment these files or comment in the files acceptable syntax. > I don't know whether the "proposed standard" was intended to be > automated, or to be a de facto standard applied by the author of each > template fragment. Again, if we identify what files have an issue it could be either way. Automated would take some work on Mitel's end. Maybe you are moving in this direction. Authored would leave the work to the author of course. An identified and posted list of files and their appropriate comments syntax would solve this issue. File | Comment Syntax smb.conf | # ; httpd.conf | # file_to_be_named | no comments permitted The key thing to remember is your customers knowledge. The average Mitel user will not know the grep command exists. An example issue for your clients is they call a software vendor for support. Their database isn't working right. The software vendors determines they have an incorrect setting in smb.conf. The support tells them to set 'strict locking = no'. The client looks at smb.conf and sees the VERY important comment at the top that this is a templated file. (You are not planning on removing this comment are you?) They read through the file and find strict locking set to yes. They see immediately, from the commented fragment title that this is set in the [11strictLocking] fragment. They now know what to change, where it is set and with a little more digging on e- smith.org will figure out how to change a template fragment correctly. One less support call for us. One happy customer feeling good that he/she has solved their database problem and now has an understanding of template fragments. Regards, -- Darrell May DMC NETSOURCED.COM http://netsourced.com http://myEZserver.com -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
