In most cases, on a dedicated machine, the read-only files will be cached by the file system. You don't necessarily spin up disk every time you read a file.
If it's REALLY an issue, you could mount it as an MFS on startup and rsync over from an /etc/mail/pop.PROTO/ directory. Naturally, you'd rsync it before starting the network processes. But why use a config/user when you can just use one default config for all? I'm also curious why is "sees" an MMDF file, rather than a proper mail spool... Quoting John Rudd ([EMAIL PROTECTED]): > (someone replied to me in private, but I thought the explanation might be > useful to the wider audience ... so, to that user, I'm sorry for technically > violating netiquette by sending this on, but it's being done for a good > reason, I think ... if you don't agree,I'm sorry, and if you say so, I wont > do this again) > > > >option? We get enough pop processes on our server that having config > > >files creates a resource contention problem on the disk where the config > > >file lives, so config files == bad. > > > > [snip]
