Paul Traina schrieb am Freitag, den 02. Oktober 2009:
So upon doing some more research and work, and testing on MY system,
this is, I believe, the correct answer for most installations, and
should not cause any problems for any installations:
I still disagree that this should defined by us.
I
Paul Traina schrieb am Sonntag, den 04. Oktober 2009:
It's perfectly reasonable to put ALL of them under the should
section if amavis needs them running first.
There is no all. Since its perl and its customizable you can't know every
service it uses or is able to use.
Alex
--
To
It's perfectly reasonable to put ALL of them under the should section
if amavis needs them running first.
On Oct 4, 2009, at 3:28 AM, Alexander Wirt formo...@debian.org wrote:
Paul Traina schrieb am Freitag, den 02. Oktober 2009:
So upon doing some more research and work, and testing on MY
On Fri, 02 Oct 2009, Paul Traina wrote:
So upon doing some more research and work, and testing on MY system,
this is, I believe, the correct answer for most installations, and
should not cause any problems for any installations:
### BEGIN INIT INFO
# Provides: amavisd-new
#
I did look at the docs before sending in the fragment. In no place
in the LSB documentation does remote_fs imply that local_fs has
already happened, so technically, having both is a good thing. Many
scripts have both. /usr can technically be remote_fs. I was trying
to change as little
On Sat, 03 Oct 2009, Paul Traina wrote:
I did look at the docs before sending in the fragment. In no place
in the LSB documentation does remote_fs imply that local_fs has
already happened, so technically, having both is a good thing. Many
So, we list both.
Do we need clamav-daemon in
Unfortunately, the new dependency based stuff (depricating sysv-rc)
breaks amavis.
Yes, amavis can depend upon a lot of stuff needing to start, so it
SHOULD start after those things, if they exist and are installed.
The LSB stuff in /etc/init.d/amavisd-new should be tweaked or auto-
On Fri, 02 Oct 2009, Paul Traina wrote:
Yes, amavis can depend upon a lot of stuff needing to start, so it
SHOULD start after those things, if they exist and are installed.
The LSB stuff in /etc/init.d/amavisd-new should be tweaked or auto-
generated to fix this.
The only way we could
So upon doing some more research and work, and testing on MY system,
this is, I believe, the correct answer for most installations, and
should not cause any problems for any installations:
### BEGIN INIT INFO
# Provides: amavisd-new
# Required-Start:$syslog $network $local_fs
9 matches
Mail list logo
