### QUICKSTART INFO ### == Fetching data for a debuginfofs server == 1) Edit /etc/debuginfofs.conf (if needed) 2) run debuginfofs-mirror REPO [REPO...] - Note: if you're on EL5 and you want rawhide/F11 debuginfo you might need to install a newer python-hashlib. See here: http://skvidal.wordpress.com/2009/02/19/yum-createrepo-hashlib-rhel5centos5-and-sha256sums/ http://http://skvidal.fedorapeople.org/hashlib/ == Running the debuginfofs server == 1) service debuginfofs-server start - You might want to edit /usr/share/debuginfofs/dav-debuginfo.conf to change the number of httpd processes to run, if you're going to have a lot of clients. - If you're running SELinux you'll need to allow httpd to access port 3309. The package %post script handles this, or you can do it yourself: /usr/sbin/semanage port -a -S targeted -t http_port_t -p tcp 3309 ### MAINTENANCE NOTES ### - Packages get added to the repos all the time. You should probably run debuginfofs-mirror (with the same arguments as you did the first time) every day or so. Consider putting it into a cron job. - Subsequent runs of debuginfofs-mirror will not re-download packages that have already been downloaded - it just updates the mtimes of all the files from that package. - Packages also get removed from the repos, but this will *not* cause the debuginfo files to disappear. They'll just start to age. - You can use the debuginfofs-cleanup script to remove files that are older than a certain amount of time. For example, 'debuginfofs-cleanup 7d' will remove all the debuginfo files from any package that hasn't been listed in any of your configured repos for a week. - Be careful, though - if you're *not* running debuginfofs-mirror regularly, the files will start to age, and then debuginfofs-cleanup might just delete them all. Some rough stats about disk usage: - Rawhide for i386 and x86_64: - debuginfo data: 46GB - F10 for i386 and x86_64: - debuginfo data (.debug files): ~100k files, 73GB - sources: ~2.2m files (!), 38GB