Look for obvious signs of trouble in Postfix
Postfix logs all failed and successful deliveries to a logfile. The file is usually called /var/log/maillog or /var/log/mail; the exact pathname is defined in the /etc/syslog.conf file.
A chronological documentation test project, nothing serious, really!
Postfix logs all failed and successful deliveries to a logfile. The file is usually called /var/log/maillog or /var/log/mail; the exact pathname is defined in the /etc/syslog.conf file.
Append one or more “-v” options to selected daemon definitions in /etc/postfix/master.cf and type “postfix reload“. This will cause a lot of activity to be logged to the syslog daemon. For example, to make the Postfix SMTP server process more verbose:
A slick script or method to compile the apps listed in the world file, from an existing system to the new system, all together at once, rather that typing in all of those application names into one giant emerge command. emerge -av $(cat /path/to/oldworld)
So here’s how I parsed to flat files with e-mail addresses (nothing special about it) approved_emails.txt has the following emails in it: email1@email.com email2@email.com check_emails.txt is composed of: email1@email.com email3@email.com email4@email.com My php file that I’m actually running from a command prompt is check_email_addresses.php < ? $approved_emails = file(“approved_emails.txt”); $check_emails = file(“check_emails.txt”); foreach ($check_emails as […]
You can analyze your system’s emerge.log file to find out how long a given package took to compile and also to estimate the time of future compile jobs, or you can use genlop, which is designed for the job.