Forum Replies Created

Viewing 15 posts - 16 through 30 (of 50 total)
  • Author
    Posts
  • in reply to: Making the most of Cached Images #373928
    hetjan
    Participant

    Can’t you just create one build-train with your base needs and use the output file as a cache in another build-train?

    in reply to: Machine specific updates #373876
    hetjan
    Participant

    So the Base updates are updates that require reboot? Some updates like the 10.5.x combo updater installs, then reboots and runs a some install scripts [plus another reboot?]. Does InstaDMG have to worry about that?

    in reply to: Machine specific updates #373874
    hetjan
    Participant

    I would guess that your firmware assumption is wrong. To my knowledge the SMC and EFI firmware can’t be modified without a normal firmware update.

    On a similar note: I don’t quite get why InstaDMG splits updates into BaseUpdates and CustomPKG. Does it matter what goes where?

    in reply to: Odd Logins from InstaDMG / Leopard Image #373871
    hetjan
    Participant

    [QUOTE][u]Quote by: vogtstev[/u][p]Hmmm. So I’m thinking it’s not really augmenting since i haven’t ever set that up, but definitely using some form of the magic triangle. I’ve been trying to think of ways to get this fixed and so far this is what I have:

    1. Prevent the “augmentation” – no idea how I can do this aside from removing machine from directory services which means I would loose all management. I would like this to work.
    2. Asked OpenLDAP admins to change the UID’s of the few in the 500 UID range. They said they were worried about this causing problems. What would this cause?
    3. Have to change UID’s on all my clients. This is the most work, but maybe what I’ll have to do. The only problem is that I believe leopard will create UID’s again starting in the 500 range. Is there a way to tell it to start at 550 or 601 or something?

    Thanks again for any ideas!
    [/p][/QUOTE]

    2. Changing the UIDs is trivial. You will get privilege errors if the user is logged in somewhere until you chown the files. Until then ls -al will show the old UID or even the matching local username (with that UID) as the owner (depending on where you look at the files from).

    3. Don’t do this. Best practices are there for a reason. Like larkost said the problem is being caused by the admins creating LDAP users in the wrong UID space.

    in reply to: Restoring iPod w/o admin user and pass #373861
    hetjan
    Participant

    Isn’t that the whole point of the /etc/authorization mechanism, a place to elevate privileges for specific programs?

    in reply to: Restoring iPod w/o admin user and pass #373812
    hetjan
    Participant

    Is there a better forum to discuss /etc/authorization?

    hetjan
    Participant

    Have you tried cleaning their caches?

    in reply to: amavisd fails to start up #366581
    hetjan
    Participant

    the perl package Net::Server was the culprit. After removing it (by copying /System/Library/Perl and /Library/Perl verbatim from another server and restarting the problem went away.

    The Net::Server package was installed as per instructions found in https://www.afp548.com/article.php?story=20051127235810230 – this article should be updated!

    in reply to: amavisd fails to start up #366579
    hetjan
    Participant

    This is what the amavis.log says on the highest verbosity level:

    Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1653]: loaded base policy bank
    Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1653]: lookup_ip_acl: key=”127.0.0.1″ matches “127.0.0.1”, result=1
    Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1653]: prolong_timer after new request – timer reset: remaining time = 300 s
    Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1653]: process_request: suggested_protocol=”” on TCP
    Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1653]: (01653-01) SMTP> 220 [127.0.0.1] ESMTP amavisd-new service ready
    Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1653]: (01653-01) idle_proc, 4: was busy, 17.9 ms, total idle 0.000 s, busy 0.018 s
    Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1653]: (01653-01) idle_proc, 5: was idle, 1.9 ms, total idle 0.002 s, busy 0.018 s
    Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1653]: (01653-01) prolong_timer after reading SMTP command: remaining time = 300 s
    Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1653]: (01653-01) SMTP< EHLO mail.multimedia.is\r\n Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1653]: (01653-01) ESMTP> 250-[127.0.0.1]
    Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1653]: (01653-01) ESMTP> 250-PIPELINING
    Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1653]: (01653-01) ESMTP> 250-SIZE
    Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1653]: (01653-01) ESMTP> 250-8BITMIME
    Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1653]: (01653-01) ESMTP> 250-ENHANCEDSTATUSCODES
    Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1653]: (01653-01) ESMTP> 250 XFORWARD NAME ADDR PROTO HELO
    Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1653]: (01653-01) idle_proc, 6: was busy, 3.2 ms, total idle 0.002 s, busy 0.021 s
    Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1653]: (01653-01) idle_proc, 5: was idle, 1.0 ms, total idle 0.003 s, busy 0.021 s
    Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1653]: (01653-01) prolong_timer after reading SMTP command: remaining time = 300 s
    Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1653]: (01653-01) ESMTP< XFORWARD NAME=localhost ADDR=127.0.0.1\r\n Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1653]: (01653-01) ESMTP> 250 2.5.0 Ok
    Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1653]: (01653-01) idle_proc, 6: was busy, 1.7 ms, total idle 0.003 s, busy 0.023 s
    Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1653]: (01653-01) idle_proc, 5: was idle, 0.3 ms, total idle 0.003 s, busy 0.023 s
    Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1653]: (01653-01) prolong_timer after reading SMTP command: remaining time = 300 s
    Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1653]: (01653-01) ESMTP< XFORWARD PROTO=SMTP HELO=multimedia.is\r\n Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1653]: (01653-01) ESMTP> 250 2.5.0 Ok
    Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1653]: (01653-01) idle_proc, 6: was busy, 1.3 ms, total idle 0.003 s, busy 0.024 s
    Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1653]: (01653-01) idle_proc, 5: was idle, 0.3 ms, total idle 0.004 s, busy 0.024 s
    Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1653]: (01653-01) prolong_timer after reading SMTP command: remaining time = 300 s
    Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1653]: (01653-01) ESMTP< MAIL FROM: SIZE=354\r\n
    Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1653]: (01653-01) prolong_timer after MAIL FROM received – timer reset: remaining time = 300 s
    Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1653]: (01653-01) prepare_tempdir: creating directory /var/amavis/amavis-20060707T194328-01653
    Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1653]: (01653-01) prepare_tempdir: creating file /var/amavis/amavis-20060707T194328-01653/email.txt
    Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1653]: (01653-01) lookup (debug_sender) => undef, “[email protected]” does not match
    Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1653]: (01653-01) ESMTP> 250 2.1.0 Sender [email protected] OK
    Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1653]: (01653-01) idle_proc, 6: was busy, 8.2 ms, total idle 0.004 s, busy 0.032 s
    Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1653]: (01653-01) idle_proc, 5: was idle, 0.3 ms, total idle 0.004 s, busy 0.032 s
    Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1653]: (01653-01) prolong_timer after reading SMTP command: remaining time = 300 s
    Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1653]: (01653-01) ESMTP< RCPT TO:\r\n
    Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1653]: (01653-01) ESMTP> 250 2.1.5 Recipient [email protected] OK
    Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1653]: (01653-01) idle_proc, 6: was busy, 1.6 ms, total idle 0.004 s, busy 0.034 s
    Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1653]: (01653-01) idle_proc, 5: was idle, 0.3 ms, total idle 0.004 s, busy 0.034 s
    Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1653]: (01653-01) prolong_timer after reading SMTP command: remaining time = 300 s
    Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1653]: (01653-01) ESMTP< DATA\r\n Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1653]: (01653-01) prolong_timer after DATA received - timer reset: remaining time = 300 s Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1653]: (01653-01) ESMTP::10024 /var/amavis/amavis-20060707T194328-01653: -> Received: SIZE=354 from mail.multimedia.is ([127.0.0.1]) by localhost (bhs-24.fsnet.is [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 01653-01 for ; Fri, 7 Jul 2006 19:43:28 +0000 (GMT)
    Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1653]: (01653-01) ESMTP> 354 End data with .
    Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1653]: (01653-01) ESMTP< .\r\n Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1653]: (01653-01) body hash: b60e32d84acd9cb884a852ba68762f64 Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1653]: (01653-01) Original mail size: 354; quota set to: 177000 bytes Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1653]: (01653-01) Checking: [127.0.0.1] ->
    Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1653]: (01653-01) query_keys: [email protected], adam@, multimedia.is, .multimedia.is, .is, .
    Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1653]: (01653-01) lookup_hash([email protected]), no matches
    Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1653]: (01653-01) lookup (bypass_virus_checks) => undef, “[email protected]” does not match
    Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1653]: (01653-01) query_keys: [email protected], adam@, multimedia.is, .multimedia.is, .is, .
    Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1653]: (01653-01) lookup_hash([email protected]), no matches
    Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1653]: (01653-01) lookup (bypass_banned_checks) => undef, “[email protected]” does not match
    Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1653]: (01653-01) Extracting mime components
    Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1653]: (01653-01) Issued a new file name: p001
    Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1653]: (01653-01) Charging 10 bytes to remaining quota 177000 (out of 177000, (0%)) – by mime_decode
    Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1653]: (01653-01) p001 1 Content-Type: text/plain, size: 10 B, name:
    Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1653]: (01653-01) prolong_timer after mime_decode-1: remaining time = 300 s
    Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1653]: (01653-01) decode_parts: level=1, #parts=1 : p001
    Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1681]: (01653-01) run_command: child process [1681]: Can’t close main::stdin: Bad file descriptor at /usr/bin/amavisd line 1589.\n
    Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1681]: (01653-01) child_finish_hook: invoking DESTROY methods
    Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1681]: (01653-01) Amavis::In::SMTP::DESTROY called
    Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1681]: (01653-01) SMTP shutdown: tempdir is being removed: /var/amavis/amavis-20060707T194328-01653
    Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1681]: (01653-01) rmdir_recursively: /var/amavis/amavis-20060707T194328-01653, excl=
    Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1681]: (01653-01) rmdir_recursively: /var/amavis/amavis-20060707T194328-01653/parts, excl=0
    Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1681]: (01653-01) ESMTP> 421 4.3.2 Service shutting down, closing channel
    Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1681]: (01653-01) at the END handler: invoking DESTROY methods
    Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1653]: (01653-01) run_command: [1681] /usr/bin/file p001 &1
    Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1653]: (01653-01) TROUBLE in check_mail: mime_decode-1 FAILED: parsing file(1) results – missing last 1 results at (eval 40) line 150.
    Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1653]: (01653-01) sending SMTP response: “451 4.5.0 Error in processing, id=01653-01, mime_decode-1 FAILED: parsing file(1) results – missing last 1 results at (eval 40) line 150.”
    Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1653]: (01653-01) timer stopped after DATA end
    Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1653]: (01653-01) PRESERVING EVIDENCE in /var/amavis/amavis-20060707T194328-01653
    Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1653]: (01653-01) TIMING [total 288 ms] – SMTP EHLO: 21 (7%), SMTP pre-MAIL: 7 (3%), mkdir tempdir: 2 (1%), create email.txt: 2 (1%), SMTP pre-DATA-flush: 10 (3%), SMTP DATA: 2 (1%), body_hash: 2 (1%), mkdir parts: 3 (1%), mime_decode: 34 (12%), rundown: 204 (71%)
    Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1653]: (01653-01) ESMTP> 451 4.5.0 Error in processing, id=01653-01, mime_decode-1 FAILED: parsing file(1) results – missing last 1 results at (eval 40) line 150.
    Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1653]: (01653-01) idle_proc, 6: was busy, 252.1 ms, total idle 0.004 s, busy 0.286 s
    Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1653]: (01653-01) idle_proc, 5: was idle, 0.7 ms, total idle 0.005 s, busy 0.286 s
    Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1653]: (01653-01) prolong_timer after reading SMTP command: remaining time = 0 s
    Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1653]: (01653-01) ESMTP< QUIT\r\n Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1653]: (01653-01) ESMTP> 221 2.0.0 [127.0.0.1] amavisd-new closing transmission channel
    Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1653]: (01653-01) TROUBLE in process_request: Error writing a SMTP response to the socket: Broken pipe at (eval 36) line 760.
    Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1653]: (01653-01) Requesting process rundown after fatal error
    Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1653]: (01653-01) post_process_request_hook: timer stopped
    Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1653]: (01653-01) idle_proc, bye: was busy, 5.5 ms, total idle 0.005 s, busy 0.291 s
    Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1653]: (01653-01) load: 98 %, total idle 0.005 s, busy 0.291 s
    Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1653]: (01653-01) child_finish_hook: invoking DESTROY methods
    Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1653]: (01653-01) Amavis::In::SMTP::DESTROY called
    Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1653]: (01653-01) ESMTP> 421 4.3.2 Service shutting down, closing channel
    Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1653]: (01653-01) SMTP shutdown: Error writing a SMTP response to the socket: Bad file descriptor at (eval 36) line 760.\n
    Jul 7 19:43:28 bhs-24.fsnet.is /usr/bin/amavisd[1653]: (01653-01) at the END handler: invoking DESTROY methods
    Jul 7 19:43:30 bhs-24.fsnet.is /usr/bin/amavisd[1684]: BerkeleyDB not available, using memory-based local cache

    Any ideas?

    in reply to: amavisd fails to start up #366560
    hetjan
    Participant

    I have the same problem–amavis not working–except I’ve found that just turning off spam and virus scanning “fixes” it…which is NO GOOD

    Edit: I didn’t see a disabled key in the .plist file.

    Whenever spam and virus scanning is enbled I get this in /var/log/mail.log
    Jul 6 02:48:07 bhs-24 postfix/smtp[21857]: A335D6AE6F: to=, relay=127.0.0.1[127.0.0.1], delay=12, status=deferred (host 127.0.0.1[127.0.0.1] said: 421 4.3.2 Service shutting down, closing channel (in reply to end of DATA command))

    in reply to: Duplicate file on server deletes orig, corrupts copy #366151
    hetjan
    Participant

    I have a very similar problem on 10.4.6 server and 10.4.6 client

    in reply to: Need Help Setting up an XServer #362753
    hetjan
    Participant

    If you want to do content control you need an application such as squid to do that. I don’t know if Cisco routers can do that, but I’m guessing it’s possible (but its way out of my league so you’ll need someone else to help you with that). My feeling (or religion) is that you should always use hardware boxes to provide network access and refrain as much as possible on relying on multi-role servers such as your XServe to do that for you.

    Other than that your XServe should be able to do what you describe. Assuming you’ll use the Cisco router (which provided it can do content-filtering is an excellent choice) you just need to follow a few simple steps which are detailed in the manuals, but basically boil down to this:

    Turn open directory on and set it to be a directory master

    Go to a client computer, open “directory access”, enter the ip of the server into the address field, the rest should be automatic provided that you have 10.4.

    Open Workgroup manager and connect to the server and create a directory on a HD that has plenty of space (RAID or such) and set it to house network home directories.

    Create a user (username, password) and set the homedirectory to the new record in the list (afp://myserver/MySharepoint f.x.).

    Now your users should be able to log in.

    A.

    in reply to: Need Help Setting up an XServer #362736
    hetjan
    Participant

    I don’t know any tutorials, but I think I can help you get started.

    First I need to know the server’s role. Is it supposed to serve home directories to mac clients on the network. Will it do Web externally? Give me all the information you can and we’ll start from there.

    in reply to: AppleFileServer hogging CPU #362288
    hetjan
    Participant

    lookupd is also taking 40+% CPU time

    in reply to: Aliases #360627
    hetjan
    Participant

    Maybe I should have worded the question like this:
    How does the Aliases tab in the Web part of Server Admin work?

Viewing 15 posts - 16 through 30 (of 50 total)