Porticron, little tool for automating daily/weekly emerge --sync and email a report

Porticron is a script for automating running emerge --sync (or eix-sync).

It mails a report to root about what files need updating and with eix-sync enabled it also includes the difference between the old and new sync in the report.

A small configuration file (/etc/conf.d/porticron) allows you to set some settings related to it's use.

** Synching **

If /usr/portage is writeable and SYNC="yes" is in the config file, it will try to run emerge --sync.
If eix is installed on the system and EIXSYNC="yes" is in the config file, it will use eix-sync for updateing.

If you share a /usr/portage directory among multiple machines, you can either mount it read only or set SYNC="no" on the clients.

** EMERGE_DEFAULT_OPTS **

The following EMERGE_DEFAULT_OPTS options is detected:
--with-bdeps and --with-bdeps=y
both makes it use --with-bdeps=y as an option.

--reinstall changed-use
If this option is detected (only --reinstall is checked for) it will be used instead of --newuse.

--usepkg
If usepkg is detected it will be used for creating the list of updated packages.

The other options used is : --pretend --changelog --update --deep --quiet

Setting EDO="no" in the config file will disable this behavior and the program will use: --usepkg --newuse

** TimeStamp System **

For people using a shared NFS mounted /usr/portage it has support for a TIMESTAMP system, each client can create a file in /usr/portage/distfiles/timestamp and the machine that performs sync will erase any file in that directory, so you can use it in a cron job to detect when it's time to run the update on the clients.

AttachmentSizeHitsLast download
porticron-0.1-sep-r1.tar.bz21.13 KB1291 week 9 hours ago

porticron 0.2 is in the

porticron 0.2 is in the portage tree, it's had most of my ideas from this version included.

I still have some things that I'm working on with this script, but for the time being, there isn't any significant advantage in using 0.1-sep-r1 over 0.2.

Since it's much easier for everyone to just use the portage tree version, I'm looking at solutions that will use the portage version as is, without having to fork it. Might just be a matter of writing a howto on advanced porticron usage.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Post new comment

The content of this field is kept private and will not be shown publicly.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Allowed HTML tags: <a> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd>
  • Lines and paragraphs break automatically.

More information about formatting options

CAPTCHA
This question is for testing whether you are a human visitor and to prevent automated spam submissions.
Image CAPTCHA
Enter the characters shown in the image.

client = pub-0221006129483283
slot = 3780496060
width = 728
height = 90

Copyright (c) 2007, 2008 Steen Eugen Poulsen

Syndicate content Syndicate content
ignorethis