[Anonymous]

i got it to work before i got your post, pretty much exactly the same way… but i never added the line to etc/hostconfig – do i need that? it works without it and i guess it’s a stupid question 🙂

[Anonymous]

Thanks. Unfortunately, that didn’t seem to help. I am still getting the same error when I start Apache.

[Anonymous]

Yes.

However, I since determined that the server cert was corrupt in the httpd directory so I re-copied it with a good one from my certs directory. It still doesn’t work but now I’m getting the ASN1 header too long error which was mentioned in another post. Unfortunately, I cannot find a link to the 10.3 ssl article you referred to for removing the pass phrase.

[Anonymous]

Never mind. I figured it out. Even though the addresses are static they must be included in a DHCP defined range.

[Anonymous]

I would also make a backup copy of your main.cf in case you have to make a change and then at least you can refresh your memory and not have to redo the spam config all ove again.

–Kevin

[quote:3619b46a32=”MacTroll”]The problem is not stopping and starting the mail system, you can still do that with Server Admin. Instead the issue is making any changes to your config in ServerAdmin. So set it up once, then add the spam controls, then don’t touch the configuration in Server Admin unless you plan on redoing the spam controls.

Joel[/quote:3619b46a32]

[Anonymous]

Try this:
Create a directory in /Library/StartupItems – name it Amavis
Make sure permissions are correct.
Inside the Amavis directory, create a file: Amavis
Insert this into Amavis file:

#!/bin/sh

. /etc/rc.common

StartService ()
{
if [ “${Amavis:=-NO-}” = “-YES-” ]; then
ConsoleMessage “Starting Amavis”
su clamav -c amavisd
freshclam -d -c 2 -l /var/log/clam-update.log
fi
}

StopService ()
{
ConsoleMessage “Stopping Amavis”
}

RunService “$1”

Inside the Amavis directory, create a file: StartupParameters.plist
Insert this into StartupParameters.plist:

{
Description = “Whatever You Want It To Say”;
Provides = (“Amavis”);
Requires = (“Resolver”);
Preference = “None”;
Messages =
{
start = “Starting Amavis”;
stop = “Stopping Amavis”;
};
}

Ceate a line in /etc/hostconfg and add this to the bottom:

Amavis=-YES-

Hope this does it.

[Anonymous]

Check your /etc/hostconfig file.

[Anonymous]

Create a directory in /Library/StartupItems – name it Amavis
Make sure permissions are correct.
Inside the Amavis directory, create a file: Amavis
Insert this into Amavis file:

#!/bin/sh

. /etc/rc.common

StartService ()
{
if [ “${Amavis:=-NO-}” = “-YES-” ]; then
ConsoleMessage “Starting Amavis”
su clamav -c amavisd
freshclam -d -c 2 -l /var/log/clam-update.log
fi
}

StopService ()
{
ConsoleMessage “Stopping Amavis”
}

RunService “$1”

Inside the Amavis directory, create a file: StartupParameters.plist
Insert this into StartupParameters.plist:

{
Description = “Whatever You Want It To Say”;
Provides = (“Amavis”);
Requires = (“Resolver”);
Preference = “None”;
Messages =
{
start = “Starting Amavis”;
stop = “Stopping Amavis”;
};
}

Ceate a line in /etc/hostconfg and add this to the bottom:

Amavis=-YES-

Hope this does it.

[Anonymous]

Hve you tried ImageMagick?

http://www.entropy.ch/software/macosx/#imagemagick

[Anonymous]

I have the same problem and I didn’t d/l any airport software upgrade lately.

In fact this was the first time I tried VaporSec and I tried my OSX login password (yes I do have admin privs), then I tried a blank password, nothing.

I am now not so sure that VaporSec actually asks for the OSX login password. The dialog is rather ambiguous and we should be suspicious of downloaded AppleScript utils which ask us for the system’s admin password, don’t you think so? I’d say this should always be done through OSX’s standard dialog for this purpose.

rgds
benjk[color=black:4f3cbbb0bb][/color:4f3cbbb0bb]

[Anonymous]

yo can type in a window terminal:
diskutil -repairPermissions

[Anonymous]

I send you via e-mail some screen of my configuration. Not step-by-step, but I hope that this will help you.
Kind regards

[Anonymous]

Hi everybody, I am in the situation where My KDC is not running, but I cannot start over and reinstall the server. So I am trying to follow the instructions to rebuilt Kerberos in Panther server 10.3.

I have followed the instructions in Joel’s articles and Anub’s message. But in the end, after getting no error, when I try to start the KDC, but typing ‘sudo krb5kdc’, I get “krb5kdc: cannot initialize realm WO.COM – see log file for details”

and the log file says “localhost krb5kdc[738]: Cannot find/read stored master key – while fetching master key K/M for realm WO.COM”

Is there any step I missed?

Anub, when you said in your message, that after you deleted the KDC files, you killed the daemons, which daemons are you refering too?

Thank you all very much. This is a great site.

Nick

[Anonymous]

Hi again Chris,

Just a follow up. The biggest problem (in my mind at least) is that you have to somehow have the live and up to date data available to both the primary and secondary server.

Apple is on it’s way to releasing a solution for this. Check out: http://www.apple.com/pr/library/2004/apr/18xsan.html

[Anonymous]

Marc Lehmann, the author of the perl Convert::UUlib module has just released a new version of that module that solves the problem.

[Author]

Posts