Tuesday, July 17. 2007From the personal Inbox of the exim4 maintainerTrackbacks
Trackback specific URI for this entry
No Trackbacks
Comments
Display comments as
(Linear | Threaded)
I’ve had similar thoughts a few times. I think the one that bugs me the most is when I spend $time researching
and fixing issues only to have my reply back to the reporter be bounced due to spam filtering, mail quota, or
similar.
This is the last time I mentioned it, that I can remember: http://www.debian-administration.org/users/Steve/weblog/163 Comment (1)
For what its worth I think you did a commendable job in trying to help this person and are doing a great job maintaining
Exim. I never once had a problem (which speaks for the quality of your packaging) and I think it to be a waste if you
let yourself get discouraged by two... well, idiots. Of course there will always be the persons who act like this, but
the vast majority is just happy with what you and the other DDs do.
I do not know if it is presumptuous but I would like to thank you on behalf of the silent majority: Thank you! Greetings and do not let stuff like that get to you! Comment (1)
#2
on
2007-07-17 21:31
I always have this problem with users asking for support. Questions usually go along the lines of: I tried to do foo,
and received bar output. To which the only reasonable response is: you need to read bar.
Only rarely is the response to this a request for help in doing what bar says, or a statement that they really don’t understand bar. Some of this may be due to perceived intimidation, however. Comment (1)
#3
on
2007-07-18 00:15
I had this problem enough that I wrote a web page about it and started linking to it in my sig. That helped a lot with
private responses to mailing list or newsgroup postings. It might also help for those readers that actually look at the
package documentation.
Feel free to do anything you wish with the text (link to it, copy it and modify it, whatever). http://www.eyrie.org/~eagle/faqs/questions.html Comment (1)
I usually reply to these mails with the message that I don’t do private consulting and could they please mail the
relevant mailing list (which I point out to them). I usually also say that the mailing list is likely to provide better
and faster support that I could privately, were I willing.
Comment (1)
As a tech support I feel for your problem , but NEWS.Debian.gz is only available to read after upgrading not before.
For many including myself exim4 is a critical package - but it also has a large number of conffiles. I recently upgraded a critical machine to etch and given the nuber of packages involved reading all the NEWS.Debian files would have been a huge drain in time - to try a pick one or two gems out of - instead I relied on the Release Notes as the debian team write great notes. Exim luckily upgraded smoothly but I was a little worried as we have customised or exim config heavily and I recognise the maintainers need to make incompatible changes - but the sheer number of individual conffiles - meant in the end I just keep my old config and decided to fix whatever broke . If the maintainence team could improve the situation by allowing exim to use older configs temporially (leaving the package state as say broken - alhtough actually working) so sysadmin can examine the situation with the system runnign it would help. (Yes it’s a lot to ask but not all of us have dual redundant systems). In future I will probably extract the system backup into a virtual machine partition and upgrade that one first to see what happens. Comment (1)
#6
on
2007-07-19 22:10
> As a tech support I feel for your problem , but NEWS.Debian.gz is only available to read after upgrading not
before.
apt-listchanges will allow you to review NEWS.Debian and Changelog.Debian before the actual upgrade starts. > For many including myself exim4 is a critical package - but it also has a large number of conffiles. Yes, but they all build up to one configuration. > I recently upgraded a critical machine to etch and given the nuber of packages involved reading all the NEWS.Debian files would have been a huge drain in time - to try a pick one or two gems out of - instead I relied on the Release Notes as the debian team write great notes. This might work with most packages, but some will need manual work. > Exim luckily upgraded smoothly but I was a little worried as we have customised or exim config heavily and I recognise the maintainers need to make incompatible changes - but the sheer number of individual conffiles - meant in the end I just keep my old config and decided to fix whatever broke. That is of course our prerogative. > If the maintainence team could improve the situation by allowing exim to use older configs temporially (leaving the package state as say broken - alhtough actually working) so sysadmin can examine the situation with the system runnign it would help. This does not seem possible to me without the packaging system cooperating. > In future I will probably extract the system backup into a virtual machine partition and upgrade that one first to see what happens. I do that for really really critical boxes, yes. Comments (3)
I know it’s frustrating for the package managers when this stuff happens. However, as a user who has only just
discovered that apt-get dist-upgrade breaks my email system too, with no apparent easy route to return to a working
configuration, I am now in a terrible situation. This is a really unpleasant situation for both sides.
The fact that there was a ‘keep your old configuration option’ looked safe to me, but now I have a broken installation and am probably going to spend several hours trying to fix it. We aren’t all technical gurus (at least in the area of managing configurations) and it’s hell on both sides by the look of things. If it had been possible to keep my old exim and my old configuration, that would have been by far the best option for me, but now it’s too late :( Comment (1)
#7
on
2007-09-12 16:08
If you don’t tell us what happened, and how your system was “broken”, noone is going to help you.
Comments (3)
Now that lenny has been released, the issue pops up for stable updaters as well. Updaters not reading the error message.
A fair amount of flamage has resulted from there in the last few days, which I have not approved but deleted instead.
To stop this, comments to this article are now closed. If you find this article via $SEARCHENGINE, please go read the docs, and if you can’t find your way around, ask on the appropriate support media, which are in the docs. Comments (3)
The author does not allow comments to this entry
|
IPv6 CheckVerbunden über IPv4
QuicksearchBlog AdministrationCategoriesComments
about Mon, 2016-04-18 11:05
Ja, kein Single-Signon und reg
elmäßige Passwortwechsel. ggf.
kombiniert mit einem Verbot,
selbst Software zu insta [...]Comments ()
about Tue, 2015-12-08 18:56
Hallo,
das ist aber lange h
er ;-)
Nach meinem - durch
den Kommentar von OhNoo veruns
icherten - Verständnis d [...]Comments (3)
about Tue, 2015-12-08 16:17
Hallo,
vielen Dank für dies
en Beitrag. Ich habe paar klei
ne Fragen, ich hoffe das ist o
kay.
Ich habe 4 Core [...]Comments ()
about Sun, 2014-03-30 15:03
Armer Tiger. :-/ Bin traurig.Comments ()
about Sat, 2014-03-29 15:35
Hallo
Sehr schöne Geschichte,
ich kann bestens nach empfind
en,
wie es dir geht. Auch wen
n mein Kater vor etliche [...]Comments ()
Show tagged entries admintipp
alice alturo ansagen apache artikelreihe auto bahn blog brille datenschutz db debian debian-english deutsche bahn dhl dienstleistung domain durchhilfe e90 einkauf english essen ethernet exim flitterwoche foehr2011 foto fundsache grml grub gsm gui-vs-tui hamburg hardware hausbau hochzeit hosting hp ice internet ip karlsruhe katze katzendiabetes kde kernel kleidung lazyweb linux linuxtag lvm mannheim meta mobilfunk musik nagios netzwerk notebook optiker paris2010 paul pc-hardware pelle persönlich php pki post prisma prozesse rant reallife reise reisebericht reisen rootserver rootserver-test rufnummern rufnummernportierung s-bahn s9y sandra security service spam strato technik telefon tk-anbieter umts umzug2007 usb vortrag webapps windows wireless zkmlf zulmp öpnv Template dropdownTechnoratiTwitter TimelineImpressum |