current 1.3.1 testing
Adrian Miranda <[email protected]>
| Newsgroups | gmane.network.up2date.current.devel |
|---|---|
| Message-ID | <[email protected]> |
I'm starting to use current 1.3.1. Since we're in the process of rolling out fairly large numbers of Linux hosts, the features of 1.3.x are a big help. I had some trouble with the docs, but I eventually got it working fine. In particular, I'd suggest expanding the section about generating ssl keys for apache to explain that you'll need to enter a password every time you start it (or need to generate an unencrypted key). Anyway, one thing I noticed is that some stuff seems to want to write to /var/log/httpd/current.log as indicated in the docs, but some other stuff seems to want to write to /var/log/current.log? I'm seeing messages like the following in httpd/error_log: Using log_file /var/log/current.log Is this configurable somewhere? Also, can you continue to use current 1.3.1 in the old stand-alone mode? I assume you can't use both modes at the same time. I understand I still need to run "cadmin create channel" when I add new RPMs. Is there something I should do to prevent current from getting run during that time? Probably I should shut the apache server down? Any suggestions on how I might go about setting up redundant servers? I suppose I could just make sure one host mirrors the other, and move the DNS entry if/when the primary one fails. I'm just curious if there are some nicer solutions that aren't too hairy. Anyway, this is a great tool, thanks! Adrian