| 1 |
On Mon, Nov 15, 2010 at 2:47 PM, kashani <kashani-list@××××××××.net> wrote: |
| 2 |
|
| 3 |
> On 11/15/2010 8:37 AM, Kevin O'Gorman wrote: |
| 4 |
> |
| 5 |
>> Color me stupid. It was stopped. It started when I told it to in |
| 6 |
>> /etc/init.d. |
| 7 |
>> Now I have to wonder what stopped it. Judging from the mail that got |
| 8 |
>> through all of a sudden, I guess it stopped |
| 9 |
>> about 2 weeks ago. I'll have to watch this... |
| 10 |
>> |
| 11 |
> |
| 12 |
> IIRC updates of the Postfix package that could in result in data |
| 13 |
> loss of queued mail will shutdown Postfix before preceding. Looks like |
| 14 |
> Postfix 2.7.1 hit on Nov 4 and 2.6.7 has been in the system since June. I'd |
| 15 |
> bet you ran the update, Postfix shutdown for safety, and you missed the |
| 16 |
> screen output about restarting it. |
| 17 |
> |
| 18 |
> kashani |
| 19 |
> |
| 20 |
> That's probably right. Emerges that take days have trained me to not to |
| 21 |
watch them happen. I read the latest elog of all packages once a month, |
| 22 |
some send me mail; but if Postfix shut down before delivery, I would not get |
| 23 |
it at all. I use elogviewer once a month, so I'll probably see it in a |
| 24 |
couple of weeks. |
| 25 |
|
| 26 |
It's nice to know what happened. Not much mail actually goes through this |
| 27 |
system, so while this has |
| 28 |
been something of a puzzle, no major harm was done. It's nice to have the |
| 29 |
explanation. |
| 30 |
|
| 31 |
Thanks. |
| 32 |
|
| 33 |
++ kevin |
| 34 |
|
| 35 |
|
| 36 |
-- |
| 37 |
Kevin O'Gorman, PhD |
Archives