./private permissions ?

While trying to expand my knowledge of the command line and exploring how all the
hidden files and directories are set up, I had the bright idea, to just create a couple of temporary aliases of a couple of them and have actually since then, deleted them.
I don't detect any harm that has been done, but I get the following, bizarre lines when I do permissions repairs with Disk Utility.
DU first changes it one way and in the same session, changes it back.
Can I correct this some way ? or have I created some trouble ?
As far as any additional info or changes, I recently installed Xcode 2.5 (for Tiger), but, I don't think that should have any bearing on it.
I tried repairs with the CD booted, and ran Applejack, thus-far.
Any ideas ? thanks
TTab
Repairing permissions for “WD728”
Determining correct file permissions.
Group differs on ./Private, should be 80, group is 0
Permissions differ on ./Private, should be drwxrwxr-x , they are drwxr-xr-x
Owner and group corrected on ./Private
Permissions corrected on ./Private
Group differs on ./private, should be 0, group is 80
Permissions differ on ./private, should be drwxr-xr-x , they are drwxrwxr-x
Owner and group corrected on ./private
Permissions corrected on ./private
Permissions repair complete
The privileges have been verified or repaired on the selected volume

Wow, I didn't notice that one was Uppercase and the other Lowercase.
Thanks, for pointing that out.
I have to remember to look more closely at filenames...
Anyway, I entered those 2 commands, as suggested, and both yield:
tcsh: pkgutil: Command not found.
BTW, Some additional info:
With "EasyFind" I found a private (lowercase) at "." (root level of hard drive-right?)
and......
a Private (uppercase) at ".Developer"
not sure if this is pertinent, or not.
as well as 2 more (upper) and 2 more (lower) dir's relating to open transport prefs.
Yet, even though they are actually two different Dir's (which I now see),
Disk Utility still repeats the same process every time and the fixes don't seem to stick,
Ya know what I mean ?
thanks for your thoughts.

Similar Messages

Finder/private permissions owned by system or me?

Finder/private permissions owned by system or me?

It's supposed to be owned by the system. There is very little in it that you should modify or delete unless instructed to do so.
(67648)

Verify Permissions Results don't stick

I'm tracing another problem and decided to check "Verify permissions" again, having done it a couple days ago.
What I am seeing, whether or not I log in as my Admin account or as root, is that no matter that Repair permissions finishes, when I Verify Permissions immediately thereafter, the same errors exist. Here's a copy of the results:
Verify permissions for “Macintosh HD”
Determining correct file permissions.
Group differs on ./Private, should be 80, group is 0
Permissions differ on ./Private, should be drwxrwxr-x , they are drwxr-xr-x
Permissions differ on ./private/etc/xinetd.d, should be drwxr-xr-x , they are -rwxr-xr-x
Permissions verification complete
The privileges have been verified or repaired on the selected volume
Repairing permissions for “Macintosh HD”
Determining correct file permissions.
Group differs on ./Private, should be 80, group is 0
Permissions differ on ./Private, should be drwxrwxr-x , they are drwxr-xr-x
Owner and group corrected on ./Private
Permissions corrected on ./Private
Permissions differ on ./private/etc/xinetd.d, should be drwxr-xr-x , they are -rwxr-xr-x
Owner and group corrected on ./private/etc/xinetd.d
Permissions corrected on ./private/etc/xinetd.d
Group differs on ./private, should be 0, group is 80
Permissions differ on ./private, should be drwxr-xr-x , they are drwxrwxr-x
Owner and group corrected on ./private
Permissions corrected on ./private
Permissions repair complete
The privileges have been verified or repaired on the selected volume
-------------------------------------------------------------------------------

well, ok ... hen is it not an issue that despite permissions being listed as fixed, that they appear, once again, to be the same errors?
I mean, if it's insignificant, then I'll not worry about "why" it does that ... and move on in trying to fix the original problem ... of which you are familiar anyway.
thanks Ray.

Repair Permissions: uh oh

Determining correct file permissions.
Group differs on ./Private, should be 80, group is 0
Permissions differ on ./Private, should be drwxrwxr-x , they are drwxr-xr-x
Owner and group corrected on ./Private
Permissions corrected on ./Private
Group differs on ./private, should be 0, group is 80
Permissions differ on ./private, should be drwxr-xr-x , they are drwxrwxr-x
Owner and group corrected on ./private
Permissions corrected on ./private

I have the exact same problem
Repairing permissions for “Mirror HD”
Determining correct file permissions.
Group differs on ./Private, should be 80, group is 0
Permissions differ on ./Private, should be drwxrwxr-x , they are drwxr-xr-x
Owner and group corrected on ./Private
Permissions corrected on ./Private
Group differs on ./private, should be 0, group is 80
Permissions differ on ./private, should be drwxr-xr-x , they are drwxrwxr-x
Owner and group corrected on ./private
Permissions corrected on ./private
I can run 'Repair Permissions' over & over again and still get the same results

Xcode ; Private - private ??

I recently installed Xcode 2.5 and as far as I can tell I installed the correct version for my system - situation here, which is Tiger 10.4.11 and am using it on a G4 Dual MDD.
I have since been experiencing this strange phenomenon when repairing permissions using Disk Utility, as listed below here; (note the "P" / "p" in private's)
Repairing permissions for “WD160TIGER”
Determining correct file permissions.
Group differs on ./Private, should be 80, group is 0
Permissions differ on ./Private, should be drwxrwxr-x , they are drwxr-xr-x
Owner and group corrected on ./Private
Permissions corrected on ./Private
Group differs on ./private, should be 0, group is 80
Permissions differ on ./private, should be drwxr-xr-x , they are drwxrwxr-x
Owner and group corrected on ./private
Permissions corrected on ./private
Permissions repair complete
The privileges have been verified or repaired on the selected volume
I used "EasyFind" and was able to discover precisely which folders they are.
"Private" (with the uppercase P) is a new one in my Developers folder, and "private" (lowercase p) is at the root level of my startup drive.This appears to be normal.
Whenever I use Disk Utility now, and repair permissions, I get the same results. It says it repairs things but, it never really does.
Note; It does not seem to be a problem but does seem a little unusual.
Question ?
Is this a normal occurrence ?
or should I try to fix it ?
Thanks for any insights.
TTab

I recently installed Xcode 2.5 and as far as I can tell I installed the correct version for my system - situation here, which is Tiger 10.4.11 and am using it on a G4 Dual MDD.
I have since been experiencing this strange phenomenon when repairing permissions using Disk Utility, as listed below here; (note the "P" / "p" in private's)
Repairing permissions for “WD160TIGER”
Determining correct file permissions.
Group differs on ./Private, should be 80, group is 0
Permissions differ on ./Private, should be drwxrwxr-x , they are drwxr-xr-x
Owner and group corrected on ./Private
Permissions corrected on ./Private
Group differs on ./private, should be 0, group is 80
Permissions differ on ./private, should be drwxr-xr-x , they are drwxrwxr-x
Owner and group corrected on ./private
Permissions corrected on ./private
Permissions repair complete
The privileges have been verified or repaired on the selected volume
I used "EasyFind" and was able to discover precisely which folders they are.
"Private" (with the uppercase P) is a new one in my Developers folder, and "private" (lowercase p) is at the root level of my startup drive.This appears to be normal.
Whenever I use Disk Utility now, and repair permissions, I get the same results. It says it repairs things but, it never really does.
Note; It does not seem to be a problem but does seem a little unusual.
Question ?
Is this a normal occurrence ?
or should I try to fix it ?
Thanks for any insights.
TTab

How to apply Qos in the precedence of cache server

m in an isp and iwant to apply the QOS to enhance my network internet performance
actually i have two requests , i will start with showing brief topology about my network and start asking the questions .
here is the topology below :
from the topology above , my access is only on R1 which is BGP internet gateway router and R2 is my ISP router.
1- i want to apply Qos on R1 so that a subnet of 32 ips to have gurantee bandwidth of 30M .
assume the subnet is 10.20.30.0/27 that need to be bw gurantee .
2- i want the download traffic by idman or ftp on my Router R1 dont exceed 50 % of my total bw .
i mean that i have 450M bandwith from my isp , & sometimes we have a slow in browsing , so i want to enhance the browsing quality because its more important that downloading files from internet.
here is my two requests above , i dont know how it will work with the precedence of the cache server .
anyway , i will paste my config of router and i will replace my puplic ips with xxx for privacy .
7200Gateway#sh run
Building configuration...
Current configuration : 10149 bytes
upgrade fpd auto
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
service password-encryption
hostname 7200Gateway
boot-start-marker
boot-end-marker
logging message-counter syslog
logging buffered 50000
enable secret xxxxxxxxxxxxxx
no aaa new-model
ip source-route
ip wccp 80 redirect-list CACHE80
ip wccp 90 redirect-list CACHE90
ip cef
no ip domain lookup
ip accounting-threshold 4294967295
login block-for 180 attempts 3 within 60
login quiet-mode access-class telnet
login on-failure log
login on-success log
no ipv6 cef
multilink bundle-name authenticated
username xxxxxx password xxxxx
archive
log config
hidekeys
interface GigabitEthernet0/1
description LAN
bandwidth 230000
ip address 10.160.150.2 255.255.255.0
ip wccp 80 redirect in
ip policy route-map CACHE-REDIRECT
load-interval 30
duplex auto
speed auto
media-type rj45
negotiation auto
interface FastEthernet0/2
no ip address
shutdown
duplex auto
speed auto
interface GigabitEthernet0/2
description Cache
bandwidth 150000
ip address x.x.x.x 255.255.255.248
ip wccp redirect exclude in
load-interval 30
duplex auto
speed 1000
media-type rj45
negotiation auto
interface GigabitEthernet0/3
description Internet
bandwidth 230000
ip address x.x.x.x 255.255.255.252
ip wccp 90 redirect in
load-interval 30
duplex full
speed 1000
media-type sfp
negotiation auto
router bgp zzzzzzz
no synchronization
bgp log-neighbor-changes
network xxxx mask xxxxx
network xxxx mask xxxx
network xxxx mask xxxxx
network xxxx mask xxxx
network xxxx mask xxxxx
network xxxx mask xxxx
redistribute connected
redistribute static
neighbor zzzzzzzz remote-as zzzzzzz
neighbor zzzzzzz password zzzzzzz
neighbor zzzzzz route-map Pipo out
no auto-summary
ip forward-protocol nd
ip route 0.0.0.0 0.0.0.0 xxxxxxxxxxx
ip route xxxxxxxx 255.255.0.0 xxxxxxxxxx
ip route xxxxxxxx 255.255.0.0 xxxxxxxxxx
ip route xxxxxxxx 255.255.0.0 xxxxxxxxxx
ip route xxxxxxxx 255.255.0.0 xxxxxxxxxx
ip route xxxxxxxx 255.255.0.0 xxxxxxxxxx
ip route xxxxxxxx 255.255.0.0 xxxxxxxxxx
ip route xxxxxxxx 255.255.0.0 xxxxxxxxxx
no ip http server
no ip http secure-server
ip flow-top-talkers
top 200
sort-by bytes
cache-timeout 5000
ip access-list extended bb
permit ip xxxx.xxxx.xx.0 0.0.1.255 any
ip access-list extended CACHE80
permit tcp xxxxxxx any eq www
ip access-list extended CACHE90
permit tcp any xxxxx.0 0.0.0.255
ip access-list extended pipo
permit ip xxxxx xxxxxxx any
permit ip xxxxx xxxxxxx any
ip access-list extended private
permit tcp 172.16.0.0 0.0.255.255 any eq www
permit ip 10.20.30.0 0.0.0.255 any
ip access-list extended telnet
permit ip xxxxxx xxxxxxx.255.255 any log
permit ip xxxx xxxxx 0.0.0.255 any log
ip prefix-list bb seq 5 permit xxxxx
ip prefix-list bbseq 10 permit xxxxxx
logging history size 500
no cdp run
route-map pipo permit 10
match ip address prefix-list pipo1
route-map pipo permit 20
match ip address prefix-list newsubnet
set metric 500
set origin incomplete
set as-path prepend xxxxxxxxx
route-map permit 10
match ip address prefix-list bibo
route-map CACHE-REDIRECT permit 10
match ip address private
set ip next-hop 1vvvvvv
route-map CACHE-REDIRECT permit 20
match ip address bibo e1
set ip next-hop vvvvvv
route-map CACHE-REDIRECT permit 30
match ip address pipo
set ip next-hop vvvvvvvvvv
route-map CACHE-REDIRECT permit 100
snmp-server community xxxxxx RO
control-plane
dial-peer cor custom
line con 0
password xxxxxxxx
logging synchronous
login
stopbits 1
line aux 0
stopbits 1
line vty 0 4
exec-timeout 60 0
password xxxxxxxxxxxxxxxxx
logging synchronous
login local
end

Hi Vinay,
Please check the program. I have used the replace statement but it is not working.
IF NOT v_sap_bom_rec IS INITIAL.
Spliting the records at '~' delimiter
    SPLIT v_sap_bom_rec AT c_del INTO wa_bom_file-model_name
                                       wa_bom_file-product_code
                                       wa_bom_file-description
                                       wa_bom_file-product_type
                                       wa_bom_file-mfg_part_num
                                       wa_bom_file-mfg_part_desc.
    REPLACE cl_abap_char_utilities=>horizontal_tab IN wa_bom_file-mfg_part_desc WITH space .
    wa_bom_file-status = c_status.
    APPEND wa_bom_file TO i_bom_file.
But it is not working.
Please help me..
Thanks
Neelima

Memory leak in WLS6.1 sp3 on Solaris?

We are running WLS 6.1 sp3 on Solaris 8 using Sun's 1.3.1 JVM with BEA's
JDriver to connect to Oracle (8.1.7). We have set the JVM to a maximum heap
of 512M (-Xms256m -Xmx512m).
The issue is that we are now seeing (via pmap) the resident memory growing
to ~1GB. Yet, the WLS management console is reporting memory usage of ~200M.
So, if we are to believe WLS, then the JVM (or some native library) is
chewing up the extra memory.
Having examined the results of "pmap -x <pid>", I see the heap (and some
anon) mem/file are quite large.
Address Kbytes Resident Shared Private Permissions Mapped File
00026000 418912 416096 - 416096 read/write/exec [ heap ]
D8C00000 524288 447928 - 447928 read/write/exec [ anon ]
total Kb 1083832 981136 37960 943176
Questions:
- Are there any known memory leaks with 6.1 sp3 on Solaris?
- Should it be possible for pmap's value of "heap" to grow larger than the
"Xms" setting? We have observed this recently, but the numbers above don't
reflect this.
- Any idea what the "anon" is or how to determine what it is?
- Do you know of any tools that might help me determine what is using that
memory or what is in it?
Any suggestions will be greatly appreciated...
Thanks in advance,
Erik

If you set -Xmx512m then the java heap will grow no larger than 512MB.
WLS is reporting the size of the java heap. (It is a java program after
all and doesn't know a lot about what native code might be doing.)
My first thought is try running with Oracle's thin (type-4) driver.
Since this is java code, it will use the java heap. If the memory usage
drastically changes, then you can point the finger at the jDriver.
Are you using any other native code / libraries?
-- Rob
Erik Westland wrote:
We are running WLS 6.1 sp3 on Solaris 8 using Sun's 1.3.1 JVM with BEA's
JDriver to connect to Oracle (8.1.7). We have set the JVM to a maximum
heap
of 512M (-Xms256m -Xmx512m).
The issue is that we are now seeing (via pmap) the resident memory growing
to ~1GB. Yet, the WLS management console is reporting memory usage of
~200M.
So, if we are to believe WLS, then the JVM (or some native library) is
chewing up the extra memory.
Having examined the results of "pmap -x ", I see the heap (and some
anon) mem/file are quite large.
Address Kbytes Resident Shared Private Permissions Mapped File
00026000 418912 416096 - 416096 read/write/exec [ heap ]
D8C00000 524288 447928 - 447928 read/write/exec [ anon ]
total Kb 1083832 981136 37960 943176
Questions:
- Are there any known memory leaks with 6.1 sp3 on Solaris?
- Should it be possible for pmap's value of "heap" to grow larger than the
"Xms" setting? We have observed this recently, but the numbers above don't
reflect this.
- Any idea what the "anon" is or how to determine what it is?
- Do you know of any tools that might help me determine what is using that
memory or what is in it?
Any suggestions will be greatly appreciated...
Thanks in advance,
Erik

Pmap and shared libraries

I'm trying to subtract the "shared" mappings from the output that pmap
produces and show memory usage per process and a separate shared
memory usage for the system.
Pmap shows shared library mappings like this ...
Address Kbytes Resident Shared Private Permissions Mapped File
FF080000 656 616 600 16 read/exec libc.so.1
FF132000 32 32 - 32 read/write/exec libc.so.1
It looks like all processes that have access to libc.so have
the same mapping. It was my understanding that the Shared and Private allocations (at least in the read/exec mapping) were a fixed
characteristic of the particular shared library.
Where is the 40 Kbytes that are not currently used? Virtual, swapped
out?, but would it be Shared or Private?

No, not all processes mapping a shared library have the same
shared/private .text section allocations.
The shared libraries are tuned for maximum sharing, that is they
are compiled as position independant code so most of the .text
section (program code) can be mapped without changes into each
process, at whatever virtual address is appropriate for each
process. All the code that needs to be adapted for a certain
virtual address is concentrated at one place in the .text section
(procedure linkage table, global offset table, ...). This part
of the shared library cannot be shared between processes and is
typically what you see as the "private" part of the .text section
in the pmap -x output. The non sharable .text section part is
just the procedure linkage table, global offset table, ... and
thus is ~ the same size for each process.
By using mprotect on the .text section or by setting breakpoints
into the .text section (to name two exceptions) you are able to
make changes to more parts of the shared .text sections, so that
you get more 'private' pages in a processes' address space. Here's
an example with breakpoints:
<pre>
4% adb /bin/cat
main:b
:r
breakpoint at:
main: save %sp, -0x190, %sp
printf:b
memmove:b
atoi:b
malloc:b
getenv:b
:c
breakpoint at:
getenv: save %sp, -0x60, %sp
</pre>
Now in another window you can verify with pmap -x that cat's copy of
libc.so with several breakpoints (=changes, private copies) in the
.text section has more private memory allocated:
<pre>
FF280000 656 616 568 48 read/exec libc.so.1
</pre>
While some other processes' copy of libc.so at the same time has:
<pre>
FF180000 656 616 592 24 read/exec libc.so.1
</pre>
The 40Kbytes difference you've observed between the .text sections'
size and the resident size are VM pages not loaded in main memory.
If these VM pages have not been changed, then they can be paged in
from the shared lib's file, else there have been changes to these
pages and they resides on the swap space.

Cisco Newbie

Dear All
I have two small networks running on seperate subnets, we have been given a Cisco C2600 and I am trying to get both networks to work together.
The only problem is our main network has a gateway already inplace that we must use for internet/etc.
The following is the current config file.
version 12.2
service timestamps debug uptime
service timestamps log uptime
service password-encryption
hostname router
ip subnet-zero
no ip domain-lookup
interface FastEthernet0/0
ip address 192.168.0.5 255.255.255.0
duplex auto
speed auto
interface FastEthernet0/1
ip address 193.xxx.xxx.19 255.255.255.0
duplex auto
speed auto
interface Serial0/0
no ip address
shutdown
interface Serial0/1
no ip address
shutdown
ip default-gateway 193.xxx.xxx.1
ip classless
no ip http server
ip pim bidir-enable
route-map f0/1 permit 10
route-map private permit 10
next ip default next-hop 193.xxx.xxx.1
line con 0
line aux 0
line vty 0 4
For network residing on f0/1 we have to use the gateway 193.xxx.xxx.1 this is for all internet traffic and we have no choice but to use this gateway.
If I set both networks to the router set IP's as there natural gateway, we get full connectivity between subnets.
Is there anyway to forward all traffic from interface f0/0 to pass over f0/1 to our primary gateway of 193.xxx.xxx.1
I hope this makes sense as a newbie this is a big adventure for me.

Set all machines on each network to use the router's address on that network, then set a default route to the 193.xxx.xxx.1 gateway like this:
ip route 0.0.0.0 0.0.0.0 193.xxx.xxx.1
This will route all traffic to the main gateway, except that which is destined for either of the two connected networks.
What about packets from a PC on the F0/1 network that should go to the main gatway? Well, the PC will send them to the .19 address, and the router will send them straight back out again to the .1 address. It will also send a "redirect" signal to the PC to say, "any more packets like that one, send them straight to the .1 address without going through me first."
I see one other potential problem with the F0/0 network: its address is 192.168.0.0/24, which is not normall routable on the Internet. I suppose the main gateway is doing address translation. If so, that is OK.
Your main gateway will need a route to send all 192.168.0.0/24 to 193.xxx.xxx.19, otherwise packets from the internet cannot get back to the F0/0 network.
Kevin Dorrell
Luxembourg

JVM takes more RAM than defined in -Xmx param on solaris

Hi all,
We have a problem on production installation of our product on Solaris paltfroms: jvm takes more (much more) RAM than defined in -Xmx param and without any OutOfMemory exceptions. (how itt possible at all ?)
The only JNI call in application is SAP interface connector, but application uses a lot of Runtime.exec() calls.
Is it possible to have such kind of "leaks" in java using JNI or Runtime.exec()?
I will be very appreciate for any tip how to find the root of this problem and how we can fix it ?
//rv
system details:
COMMAND
nohup /system/jre/bin/java -XX:+DisableExplicitGC -XX:NewSize=80m -XX:MaxNewSize=80m -Xms256m -Xmx256m -cp /system/bin/application.jar: applicationstart >/sysem/bin/../log/jvm.log
JAVAVERSION
SRV12345/root # /system/jre/bin/java -fullversion
java full version "1.4.2_08-b03"
OS-VERSION
[root@SRV12345] /->uname -r
5.8
TASKS
[root@SRV12345] /->prstat
PID USERNAME SIZE RSS STATE PRI NICE TIME CPU PROCESS/NLWP
6415 root 964M 913M sleep 29 10 20:33.12 0.3% java/128
Total: 75 processes, 310 lwps, load averages: 0.02, 0.04, 0.08
CPUS
root@SRV12345] /->psrinfo -v
Status of virtual processor 0 as of: 07/27/06 16:33:23
on-line since 05/22/06 11:40:25.
The sparcv9 processor operates at 1320 MHz,
and has a sparcv9 floating point processor.
Status of virtual processor 1 as of: 07/27/06 16:33:23
on-line since 05/22/06 11:40:26.
The sparcv9 processor operates at 1320 MHz,
and has a sparcv9 floating point processor.
HARDWARE
[root@SRV12345] /->prtconf
System Configuration: Sun Microsystems sun4us
Memory size: 4096 Megabytes
System Peripherals (Software Nodes):
MEMORY USAGE - PROCESS
[root@SRV12345] /->pmap -x 6415
6415: /oms/OMSSpooler/system/jre/bin/java -XX:+DisableExplicitGC -XX:NewSize
Address Kbytes Resident Shared Private Permissions Mapped File
00010000 72 72 72 - read/exec java
00030000 16 16 - 16 read/write/exec java
00034000 636528 636456 618112 18344 read/write/exec [ heap ]
DA77A000 8 8 - 8 read/write/exec [ anon ]
DA77E000 16 16 8 8 read/write/exec [ anon ]
DAD7A000 32 32 8 24 read/write/exec [ anon ]
DAE7A000 32 32 8 24 read/write/exec [ anon ]
DB07A000 32 32 8 24 read/write/exec [ anon ]
DB17A000 32 32 8 24 read/write/exec [ anon ]
DB278000 40 40 32 8 read/write/exec [ anon ]
DB67A000 32 32 8 24 read/write/exec [ anon ]
DB97A000 32 32 8 24 read/write/exec [ anon ]
DBA7A000 32 32 24 8 read/write/exec [ anon ]
DBB7A000 32 32 8 24 read/write/exec [ anon ]
DBC7A000 8 8 8 - read/write/exec [ anon ]
DBC7E000 16 16 8 8 read/write/exec [ anon ]
DBD76000 48 48 48 - read/write/exec [ anon ]
DBE7A000 32 32 8 24 read/write/exec [ anon ]
DBF78000 40 40 24 16 read/write/exec [ anon ]
DC07A000 8 8 - 8 read/write/exec [ anon ]
DC07E000 16 16 - 16 read/write/exec [ anon ]
DC17A000 32 32 24 8 read/write/exec [ anon ]
DC27A000 8 8 8 - read/write/exec [ anon ]
DC27E000 16 16 8 8 read/write/exec [ anon ]
DC37A000 8 8 8 - read/write/exec [ anon ]
DC37E000 16 16 8 8 read/write/exec [ anon ]
DC47A000 8 8 8 - read/write/exec [ anon ]
DC47E000 16 16 8 8 read/write/exec [ anon ]
DC778000 16 16 8 8 read/write/exec [ anon ]
DC77E000 16 16 - 16 read/write/exec [ anon ]
DC87A000 8 8 8 - read/write/exec [ anon ]
DC87E000 16 16 8 8 read/write/exec [ anon ]
DC97A000 8 8 8 - read/write/exec [ anon ]
DC97E000 16 16 8 8 read/write/exec [ anon ]
DCA7A000 8 8 8 - read/write/exec [ anon ]
DCA7E000 16 16 8 8 read/write/exec [ anon ]
DCB7A000 8 8 8 - read/write/exec [ anon ]
DCB7E000 16 16 8 8 read/write/exec [ anon ]
DCF7A000 32 32 16 16 read/write/exec [ anon ]
DD07A000 32 32 8 24 read/write/exec [ anon ]
DD17A000 32 32 8 24 read/write/exec [ anon ]
DD278000 40 40 16 24 read/write/exec [ anon ]
DD478000 40 40 40 - read/write/exec [ anon ]
DD67A000 32 32 8 24 read/write/exec [ anon ]
DD778000 40 40 16 24 read/write/exec [ anon ]
DDA7A000 32 32 16 16 read/write/exec [ anon ]
DDB78000 40 40 16 24 read/write/exec [ anon ]
DDC7A000 8 8 - 8 read/write/exec [ anon ]
DDC7E000 16 16 8 8 read/write/exec [ anon ]
DDD78000 40 40 32 8 read/write/exec [ anon ]
DDE78000 40 40 40 - read/write/exec [ anon ]
DE07A000 32 32 8 24 read/write/exec [ anon ]
DE178000 40 40 16 24 read/write/exec [ anon ]
DE276000 48 48 40 8 read/write/exec [ anon ]
DE37A000 32 32 8 24 read/write/exec [ anon ]
DE578000 40 40 16 24 read/write/exec [ anon ]
DE77A000 32 32 16 16 read/write/exec [ anon ]
DE87A000 32 32 32 - read/write/exec [ anon ]
DE97A000 32 32 8 24 read/write/exec [ anon ]
DEA78000 40 40 16 24 read/write/exec [ anon ]
DEB7A000 32 32 16 16 read/write/exec [ anon ]
DEC7A000 32 32 8 24 read/write/exec [ anon ]
DED78000 40 40 40 - read/write/exec [ anon ]
DEE7A000 32 32 8 24 read/write/exec [ anon ]
DEF7A000 32 32 8 24 read/write/exec [ anon ]
DF07A000 32 32 16 16 read/write/exec [ anon ]
DF27A000 32 32 24 8 read/write/exec [ anon ]
DF478000 40 40 40 - read/write/exec [ anon ]
DF578000 40 40 - 40 read/write/exec [ anon ]
DF77A000 32 32 8 24 read/write/exec [ anon ]
DF87A000 32 32 16 16 read/write/exec [ anon ]
DFA78000 40 40 16 24 read/write/exec [ anon ]
DFC7A000 8 8 - 8 read/write/exec [ anon ]
DFC7E000 16 16 - 16 read/write/exec [ anon ]
E0078000 40 40 8 32 read/write/exec [ anon ]
E0278000 40 40 16 24 read/write/exec [ anon ]
E067A000 32 32 24 8 read/write/exec [ anon ]
E077A000 8 8 8 - read/write/exec [ anon ]
E077E000 16 16 8 8 read/write/exec [ anon ]
E0878000 40 40 32 8 read/write/exec [ anon ]
E0978000 40 40 32 8 read/write/exec [ anon ]
E0A78000 40 40 24 16 read/write/exec [ anon ]
E0B78000 40 40 16 24 read/write/exec [ anon ]
E0C78000 40 40 32 8 read/write/exec [ anon ]
E0E7A000 8 8 8 - read/write/exec [ anon ]
E0E7E000 16 16 8 8 read/write/exec [ anon ]
E1076000 48 48 48 - read/write/exec [ anon ]
E117A000 32 32 32 - read/write/exec [ anon ]
E127A000 32 32 24 8 read/write/exec [ anon ]
E137A000 32 32 8 24 read/write/exec [ anon ]
E147A000 32 32 32 - read/write/exec [ anon ]
E1578000 40 40 16 24 read/write/exec [ anon ]
E187A000 8 8 - 8 read/write/exec [ anon ]
E187E000 16 16 - 16 read/write/exec [ anon ]
E1978000 40 40 24 16 read/write/exec [ anon ]
E1A78000 40 40 24 16 read/write/exec [ anon ]
E1B78000 40 40 16 24 read/write/exec [ anon ]
E1C7A000 32 32 16 16 read/write/exec [ anon ]
E1D7A000 32 32 8 24 read/write/exec [ anon ]
E1E78000 40 40 24 16 read/write/exec [ anon ]
E1F78000 40 40 8 32 read/write/exec [ anon ]
E207A000 32 32 32 - read/write/exec [ anon ]
E217A000 8 8 8 - read/write/exec [ anon ]
E217E000 16 16 8 8 read/write/exec [ anon ]
E227A000 32 32 8 24 read/write/exec [ anon ]
E2378000 40 40 16 24 read/write/exec [ anon ]
E247A000 32 32 32 - read/write/exec [ anon ]
E257A000 32 32 16 16 read/write/exec [ anon ]
E267A000 32 32 16 16 read/write/exec [ anon ]
E2878000 40 40 16 24 read/write/exec [ anon ]
E297A000 32 32 16 16 read/write/exec [ anon ]
E2A7A000 32 32 16 16 read/write/exec [ anon ]
E2B7A000 32 32 16 16 read/write/exec [ anon ]
E2C00000 4408 688 688 - read/exec librfccm.so
E305C000 2584 664 624 40 read/write/exec librfccm.so
E32E2000 688 320 312 8 read/write/exec librfccm.so
E3400000 2072 120 120 - read/exec libsapjcorfc.so
E3614000 24 24 24 - read/write/exec libsapjcorfc.so
E36FA000 32 32 8 24 read/write/exec [ anon ]
E38FA000 8 8 - 8 read/write/exec [ anon ]
E38FE000 16 16 - 16 read/write/exec [ anon ]
E39F6000 48 48 - 48 read/write/exec [ anon ]
E3AFA000 32 32 32 - read/write/exec [ anon ]
E3BF8000 40 40 16 24 read/write/exec [ anon ]
E3CFA000 32 32 16 16 read/write/exec [ anon ]
E3DFA000 32 32 32 - read/write/exec [ anon ]
E3EFA000 8 8 - 8 read/write/exec [ anon ]
E3EFE000 16 16 - 16 read/write/exec [ anon ]
E3FF8000 40 40 40 - read/write/exec [ anon ]
E40FA000 8 8 - 8 read/write/exec [ anon ]
E40FE000 16 16 - 16 read/write/exec [ anon ]
E41F6000 48 48 40 8 read/write/exec [ anon ]
E42FA000 32 32 32 - read/write/exec [ anon ]
E43F6000 48 48 - 48 read/write/exec [ anon ]
E44F8000 40 40 - 40 read/write/exec [ anon ]
E45F8000 40 40 32 8 read/write/exec [ anon ]
E46FA000 8 8 - 8 read/write/exec [ anon ]
E46FE000 16 16 - 16 read/write/exec [ anon ]
E47F8000 40 40 16 24 read/write/exec [ anon ]
E48FA000 32 32 24 8 read/write/exec [ anon ]
E49F8000 40 40 16 24 read/write/exec [ anon ]
E4AFA000 8 8 - 8 read/write/exec [ anon ]
E4AFE000 16 16 - 16 read/write/exec [ anon ]
E4BFA000 8 8 - 8 read/write/exec [ anon ]
E4BFE000 16 16 - 16 read/write/exec [ anon ]
E4CF6000 48 48 40 8 read/write/exec [ anon ]
E4DF6000 48 48 - 48 read/write/exec [ anon ]
E4E80000 720 112 112 - read/shared dev:85,6 ino:2414099
E4F80000 1616 16 16 - read/shared dev:85,6 ino:2604124
E5180000 584 24 24 - read/shared dev:85,6 ino:2604127
E5280000 560 32 32 - read/shared dev:85,6 ino:2604145
E5380000 504 16 16 - read/shared dev:85,6 ino:2604133
E5480000 1776 40 40 - read/shared dev:85,6 ino:2604140
E5680000 1120 56 56 - read/shared dev:85,6 ino:2604138
E5800000 277504 277344 268008 9336 read/write/exec [ anon ]
F9900000 752 8 8 - read/shared dev:85,6 ino:899745
F9A80000 8 8 - 8 read/write/exec [ anon ]
F9B7C000 24 24 16 8 read/write/exec [ anon ]
F9C00000 9280 8944 8760 184 read/write/exec [ anon ]
FBC50000 8 8 8 - read/shared dev:85,6 ino:2414079
FBC60000 16 16 16 - read/shared dev:85,6 ino:2414042
FBC70000 24 24 24 - read/shared dev:85,6 ino:2414043
FBC80000 440 32 32 - read/shared dev:85,6 ino:2604129
FBD80000 8 8 - 8 read/write/exec [ anon ]
FBD90000 8 8 - 8 read/write/exec [ anon ]
FBDA0000 56 56 56 - read/exec libnet.so
FBDBC000 16 16 16 - read/write/exec libnet.so
FBDD0000 176 16 16 - read/shared dev:85,6 ino:2604126
FBE80000 8 8 - 8 read/write/exec [ anon ]
FBE90000 128 8 8 - read/shared dev:85,6 ino:2604148
FBEC0000 216 8 8 - read/shared dev:85,6 ino:2604125
FBF7A000 32 32 24 8 read/write/exec [ anon ]
FBF90000 416 8 8 - read/shared dev:85,6 ino:2604128
FC000000 5696 8 8 - read/shared dev:85,6 ino:1450986
FC5A0000 344 40 40 - read/shared dev:85,6 ino:2604131
FC67A000 32 32 24 8 read/write/exec [ anon ]
FC690000 24 24 24 - read/exec libpthread.so.1
FC6A6000 8 8 8 - read/write/exec libpthread.so.1
FC6B0000 304 40 40 - read/shared dev:85,6 ino:2604144
FC780000 8 8 - 8 read/write/exec [ anon ]
FC7A0000 352 24 24 - read/shared dev:85,6 ino:2604147
FC800000 23464 16 16 - read/shared dev:85,6 ino:1451026
FDEF0000 8 8 8 - read/exec libw.so.1
FDF00000 192 24 24 - read/shared dev:85,6 ino:2604142
FDF40000 96 8 8 - read/shared dev:85,6 ino:2604134
FDF60000 240 40 40 - read/shared dev:85,6 ino:2604157
FDFA0000 360 352 352 - read/write/exec [ anon ]
FE000000 4032 2472 2472 - read/exec libjvm.so
FE3F0000 128 128 88 40 read/write/exec libjvm.so
FE410000 56 56 48 8 read/write/exec libjvm.so
FE430000 32 32 32 - read/shared dev:85,6 ino:2604137
FE440000 208 40 40 - read/shared dev:85,6 ino:2604135
FE480000 544 544 328 216 read/write/exec [ anon ]
FE520000 8 8 8 - read/write/exec [ anon ]
FE530000 32 32 32 - read/shared dev:85,6 ino:2604146
FE540000 16 16 16 - read/shared dev:85,6 ino:2604123
FE550000 40 16 16 - read/shared dev:85,6 ino:2604139
FE560000 56 - - - read/shared dev:85,6 ino:899744
FE580000 152 152 152 - read/write/exec [ anon ]
FE610000 112 8 8 - read/shared dev:85,6 ino:899742
FE630000 32 32 24 8 read/write/exec [ anon ]
FE660000 72 - - - read/shared dev:85,6 ino:1450975
FE680000 872 8 8 - read/shared dev:85,6 ino:1450985
FE760000 8 8 8 - read/shared dev:85,6 ino:2604132
FE770000 88 16 16 - read/shared dev:85,6 ino:1450974
FE790000 64 64 64 - read/exec libzip.so
FE7A0000 8 8 8 - read/write/exec libzip.so
FE7B0000 8 8 - 8 read/write/exec [ anon ]
FE7C0000 136 136 136 - read/exec libjava.so
FE7F2000 8 8 8 - read/write/exec libjava.so
FE802000 8 8 8 - read/write/exec [ anon ]
FE904000 8 8 8 - read/write/exec [ anon ]
FEA06000 8 8 8 - read/write/exec [ anon ]
FEB08000 8 8 8 - read/write/exec [ anon ]
FEC0A000 8 8 8 - read/write/exec [ anon ]
FED0C000 8 8 8 - read/write/exec [ anon ]
FEE0A000 8 8 8 - read/write/exec [ anon ]
FEE0E000 8 8 8 - read/write/exec [ anon ]
FEF0C000 8 8 - 8 read/write/exec [ anon ]
FEF10000 8 8 8 - read/write/exec [ anon ]
FF00E000 8 8 8 - read/write/exec [ anon ]
FF020000 88 88 88 - read/exec libverify.so
FF046000 8 8 8 - read/write/exec libverify.so
FF050000 16 16 16 - read/shared dev:85,6 ino:899743
FF060000 40 40 40 - read/exec libhpi.so
FF07A000 8 8 8 - read/write/exec libhpi.so
FF07C000 8 - - - read/write/exec libhpi.so
FF090000 16 16 16 - read/exec libmp.so.2
FF0A4000 8 8 8 - read/write/exec libmp.so.2
FF0B0000 224 104 104 - read/exec libm.so.1
FF0F6000 8 8 8 - read/write/exec libm.so.1
FF100000 576 576 576 - read/exec libnsl.so.1
FF190000 40 40 32 8 read/write/exec libnsl.so.1
FF19A000 24 16 16 - read/write/exec libnsl.so.1
FF1B0000 8 8 8 - read/exec libsched.so.1
FF1C2000 8 8 8 - read/write/exec libsched.so.1
FF1D0000 8 8 - 8 read/write/exec [ anon ]
FF1E0000 40 40 40 - read/exec libsocket.so.1
FF1FA000 8 8 8 - read/write/exec libsocket.so.1
FF200000 688 688 688 - read/exec libc.so.1
FF2BC000 32 32 8 24 read/write/exec libc.so.1
FF2D0000 48 48 48 - read/exec libCrun.so.1
FF2EA000 8 8 8 - read/write/exec libCrun.so.1
FF2EC000 16 8 8 - read/write/exec libCrun.so.1
FF300000 16 16 16 - read/write/shared dev:0,2 ino:7595433
FF314000 8 8 8 - read/write/exec [ anon ]
FF320000 8 8 8 - read/write/exec/shared [ anon ]
FF330000 8 8 - 8 read/write/exec [ anon ]
FF340000 8 8 - 8 read/write/exec libdl.so.1
FF350000 112 112 112 - read/exec libthread.so.1
FF37C000 8 8 - 8 read/write/exec libthread.so.1
FF37E000 48 48 - 48 read/write/exec libthread.so.1
FF390000 8 8 8 - read/exec libc_psr.so.1
FF3A0000 184 184 184 - read/exec ld.so.1
FF3DE000 8 8 - 8 read/write/exec ld.so.1
FF3E0000 8 8 - 8 read/write/exec ld.so.1
FFB70000 24 - - - - [ anon ]
FFBD6000 104 104 96 8 read/write/exec [ stack ]
total Kb 986752 936008 905624 30384

See http://java.sun.com/j2se/1.5/pdf/jdk50_ts_guide.pdf and look into using libumen on Solaris.
-kto

How to make all content in MySites publically available

Hi - we're rolling out My SItes and the customer wants everybody to have read access to everything in every users My SIte.
Can I do this by creating a Full Read Web Application User Policy for Domain users? I mean - will that enable all users to see content even on the private areas of their sky drive (i.e. not in the Shared with Everyone folder or in folders/sites
that they have created and set private permissions on).
Even with that policy applied will users still be able to create private areas if they want to? The idea is that when users leave their content will be easily harvested. If a user does leave and has docs in a secured area of their My Site can a site admin
over ride this and access all areas and take ownership of everything?
Cheers
J

Hi Jonjames,
if you set Full Read on the WebApplication, there will be no possiblity, to create private areas within that webapplication. (it is the same policy, which also Crawling Account is using to access all data in WebApplication).
If user leaves, SP Admin can take ownership ower his data. (SP Admin usually has access to all WebApplications)
Regards
Lubomir

About ACL and default document and folder ACL in the profile

Please let me know if I am wrong or not?
If I have a user6 with a default ACL (folder and document): user6ACL
The home folder directory (home\user6) has user5ACL.
I copied a file into the user6 home folder: The new file is going a have user6ACL, right?,
Now what happened if the user6 copies another file into another directory?, (no the home directory) which ACL is going a take the file?
The default ACL specified in the profile user or the ACL from the parent directory?
I have tested, is taking the acl from the parent folder. And is no using the default document and the default folder ACL specified in the profile.
Thanks very much.

I personally think that this behaviour is expected, or how else would you realize certain folders for collaborative work when every file there is created with e.g. private permissions ?
regards, F. Leeber

Disk Utility error-what does this mean?

Everytime I do repair disk permissions, and I do it almost daily, I get this message:
Repairing permissions for “My Disk"
Determining correct file permissions.
Group differs on ./Private, should be 80, group is 0
Permissions differ on ./Private, should be drwxrwxr-x , they are drwxr-xr-x
Owner and group corrected on ./Private
Permissions corrected on ./Private
Group differs on ./private, should be 0, group is 80
Permissions differ on ./private, should be drwxr-xr-x , they are drwxrwxr-x
Owner and group corrected on ./private
Permissions corrected on ./private
Permissions repair complete
The privileges have been verified or repaired on the selected volume
Has anybody idea what is this?
thank you

Welcome to the Forums Nedd!
It's normal, no worry for us.
Michael Conniff covers some more of it here...
http://discussions.apple.com/thread.jspa?threadID=121755&tstart=0
I get the exact same as you when everything is correct!

Lion Server postfix mail not being delivered to mailboxes. "SMTP restriction `reject_invalid_helo_hostname' after `permit' is ignored" and "connect to private/policy: Connection refused" errors.

All, Im stumped. In fact I have been on the phone with Apple Support and this has been escalated to the top engineers, as I think its got them too..
Anyway, here is my problem..
I'm running an Mac Mini with OS X 10.7.4 Server. I have had mail running on it for 2 months or so, without any issues. The mail was actually migrated from 10.6 in March, and It actually went smoothly. I have 3 domains which all recieve mail and they all work (or did up until 2 weeks ago)..
So the story is this.. I can send mail from my domains, without issue. imap and dovecot must be working.. cause all the stored mail, can be read with the mail IMAP client.. I can even transfer mail messages from one mailbox to another with Mail client. Sending mail is a breeze, it still works and the recipients still recieve their mail. But I noticed I wasnt getting any mail at all from those mailboxes... no mail, no spam, nothing.. which is unusal. I fired up Server admin and checked out the SMTP log, and this is what it showed for every email recieved: (xxxxxx is just me hiding sensitive info)
Jul 21 14:25:20 xxxxxxxx postfix/postscreen[65857]: CONNECT from [17.158.233.225]:41909
Jul 21 14:25:26 xxxxxxxx postfix/postscreen[65857]: PASS OLD [17.158.233.225]:41909
Jul 21 14:25:26 xxxxxxxx postfix/smtpd[65858]: connect from nk11p03mm-asmtp994.mac.com[17.158.233.225]
Jul 21 14:25:26 xxxxxxxx postfix/smtpd[65858]: warning: restriction `reject_invalid_helo_hostname' after `permit' is ignored
Jul 21 14:25:27 xxxxxxxx postfix/smtpd[65858]: warning: connect to private/policy: Connection refused
Jul 21 14:25:27 xxxxxxxx postfix/smtpd[65858]: warning: problem talking to server private/policy: Connection refused
Jul 21 14:25:28 xxxxxxxx postfix/smtpd[65858]: warning: connect to private/policy: Connection refused
Jul 21 14:25:28 xxxxxxxx postfix/smtpd[65858]: warning: problem talking to server private/policy: Connection refused
Jul 21 14:25:28 xxxxxxxx postfix/smtpd[65858]: NOQUEUE: reject: RCPT from nk11p03mm-asmtp994.mac.com[17.158.233.225]: 451 4.3.5 Server configuration problem; from=<[email protected]> to=<[email protected]> proto=ESMTP helo=<nk11p99mm-asmtpout004.mac.com>
Jul 21 14:25:28 azathoth postfix/smtpd[65858]: disconnect from nk11p03mm-asmtp994.mac.com[17.158.233.225]
Ok, now what is odd, is these rejected messages are not even appearing in the mail queue in Server Admin. I have no idea why there are not being delivered
Ive checked my postfix main.cf file and master.cf files they both look ok.. Ive even replaced them with the main.cf.defualt.10.7 and master.cf.default.10.7 files and to no avail... same problem..
So in summary
I can send mail out
IMAP is working on the client end (thus dovecot is) exsisting stored emails can be accessed, read, moved unread etc..
mail is coming into the sever, but its being rejected. there is NO rejection email sent back to the sender.
mail is recieved by postfix, but cyrus isnt doing anything with it.. I have no idea where it goes...
Could anyone shed light on this...
my main.cf file:
# Global Postfix configuration file. This file lists only a subset
# of all 300+ parameters. See the postconf(5) manual page for a
# complete list.
# The general format of each line is: parameter = value. Lines
# that begin with whitespace continue the previous line. A value can
# contain references to other $names or ${name}s.
# NOTE - CHANGE NO MORE THAN 2-3 PARAMETERS AT A TIME, AND TEST IF
# POSTFIX STILL WORKS AFTER EVERY CHANGE.
# SOFT BOUNCE
# The soft_bounce parameter provides a limited safety net for
# testing. When soft_bounce is enabled, mail will remain queued that
# would otherwise bounce. This parameter disables locally-generated
# bounces, and prevents the SMTP server from rejecting mail permanently
# (by changing 5xx replies into 4xx replies). However, soft_bounce
# is no cure for address rewriting mistakes or mail routing mistakes.
# soft_bounce = no
# LOCAL PATHNAME INFORMATION
# The queue_directory specifies the location of the Postfix queue.
# This is also the root directory of Postfix daemons that run chrooted.
# See the files in examples/chroot-setup for setting up Postfix chroot
# environments on different UNIX systems.
queue_directory = /private/var/spool/postfix
# The command_directory parameter specifies the location of all
# postXXX commands.
command_directory = /usr/sbin
# The daemon_directory parameter specifies the location of all Postfix
# daemon programs (i.e. programs listed in the master.cf file). This
# directory must be owned by root.
daemon_directory = /usr/libexec/postfix
# QUEUE AND PROCESS OWNERSHIP
# The mail_owner parameter specifies the owner of the Postfix queue
# and of most Postfix daemon processes. Specify the name of a user
# account THAT DOES NOT SHARE ITS USER OR GROUP ID WITH OTHER ACCOUNTS
# AND THAT OWNS NO OTHER FILES OR PROCESSES ON THE SYSTEM. In
# particular, don't specify nobody or daemon. PLEASE USE A DEDICATED
# USER.
mail_owner = _postfix
# The default_privs parameter specifies the default rights used by
# the local delivery agent for delivery to external file or command.
# These rights are used in the absence of a recipient user context.
# DO NOT SPECIFY A PRIVILEGED USER OR THE POSTFIX OWNER.
#default_privs = nobody
# INTERNET HOST AND DOMAIN NAMES
# The myhostname parameter specifies the internet hostname of this
# mail system. The default is to use the fully-qualified domain name
# from gethostname(). $myhostname is used as a default value for many
# other configuration parameters.
#myhostname = host.domain.tld
#myhostname = virtual.domain.tld
# The mydomain parameter specifies the local internet domain name.
# The default is to use $myhostname minus the first component.
# $mydomain is used as a default value for many other configuration
# parameters.
#mydomain = domain.tld
# SENDING MAIL
# The myorigin parameter specifies the domain that locally-posted
# mail appears to come from. The default is to append $myhostname,
# which is fine for small sites. If you run a domain with multiple
# machines, you should (1) change this to $mydomain and (2) set up
# a domain-wide alias database that aliases each user to
# [email protected].
# For the sake of consistency between sender and recipient addresses,
# myorigin also specifies the default domain name that is appended
# to recipient addresses that have no @domain part.
#myorigin = $myhostname
#myorigin = $mydomain
# RECEIVING MAIL
# The inet_interfaces parameter specifies the network interface
# addresses that this mail system receives mail on. By default,
azathoth:postfix root#
azathoth:postfix root# less main.cf
azathoth:postfix root# more main.cf
# Global Postfix configuration file. This file lists only a subset
# of all 300+ parameters. See the postconf(5) manual page for a
# complete list.
# The general format of each line is: parameter = value. Lines
# that begin with whitespace continue the previous line. A value can
# contain references to other $names or ${name}s.
# NOTE - CHANGE NO MORE THAN 2-3 PARAMETERS AT A TIME, AND TEST IF
# POSTFIX STILL WORKS AFTER EVERY CHANGE.
# SOFT BOUNCE
# The soft_bounce parameter provides a limited safety net for
# testing. When soft_bounce is enabled, mail will remain queued that
# would otherwise bounce. This parameter disables locally-generated
# bounces, and prevents the SMTP server from rejecting mail permanently
# (by changing 5xx replies into 4xx replies). However, soft_bounce
# is no cure for address rewriting mistakes or mail routing mistakes.
# soft_bounce = no
# LOCAL PATHNAME INFORMATION
# The queue_directory specifies the location of the Postfix queue.
# This is also the root directory of Postfix daemons that run chrooted.
# See the files in examples/chroot-setup for setting up Postfix chroot
# environments on different UNIX systems.
queue_directory = /private/var/spool/postfix
# The command_directory parameter specifies the location of all
# postXXX commands.
command_directory = /usr/sbin
# The daemon_directory parameter specifies the location of all Postfix
# daemon programs (i.e. programs listed in the master.cf file). This
# directory must be owned by root.
daemon_directory = /usr/libexec/postfix
# QUEUE AND PROCESS OWNERSHIP
# The mail_owner parameter specifies the owner of the Postfix queue
# and of most Postfix daemon processes. Specify the name of a user
# account THAT DOES NOT SHARE ITS USER OR GROUP ID WITH OTHER ACCOUNTS
# AND THAT OWNS NO OTHER FILES OR PROCESSES ON THE SYSTEM. In
# particular, don't specify nobody or daemon. PLEASE USE A DEDICATED
# USER.
mail_owner = _postfix
# The default_privs parameter specifies the default rights used by
# the local delivery agent for delivery to external file or command.
# These rights are used in the absence of a recipient user context.
# DO NOT SPECIFY A PRIVILEGED USER OR THE POSTFIX OWNER.
#default_privs = nobody
# INTERNET HOST AND DOMAIN NAMES
# The myhostname parameter specifies the internet hostname of this
# mail system. The default is to use the fully-qualified domain name
# from gethostname(). $myhostname is used as a default value for many
# other configuration parameters.
#myhostname = host.domain.tld
#myhostname = virtual.domain.tld
# The mydomain parameter specifies the local internet domain name.
# The default is to use $myhostname minus the first component.
# $mydomain is used as a default value for many other configuration
# parameters.
#mydomain = domain.tld
# SENDING MAIL
# The myorigin parameter specifies the domain that locally-posted
# mail appears to come from. The default is to append $myhostname,
# which is fine for small sites. If you run a domain with multiple
# machines, you should (1) change this to $mydomain and (2) set up
# a domain-wide alias database that aliases each user to
# [email protected].
# For the sake of consistency between sender and recipient addresses,
# myorigin also specifies the default domain name that is appended
# to recipient addresses that have no @domain part.
#myorigin = $myhostname
#myorigin = $mydomain
# RECEIVING MAIL
# The inet_interfaces parameter specifies the network interface
# addresses that this mail system receives mail on. By default,
# the software claims all active interfaces on the machine. The
# parameter also controls delivery of mail to user@[ip.address].
# See also the proxy_interfaces parameter, for network addresses that
# are forwarded to us via a proxy or network address translator.
# Note: you need to stop/start Postfix when this parameter changes.
#inet_interfaces = all
#inet_interfaces = $myhostname
#inet_interfaces = $myhostname, localhost
# The proxy_interfaces parameter specifies the network interface
# addresses that this mail system receives mail on by way of a
# proxy or network address translation unit. This setting extends
# the address list specified with the inet_interfaces parameter.
# You must specify your proxy/NAT addresses when your system is a
# backup MX host for other domains, otherwise mail delivery loops
# will happen when the primary MX host is down.
#proxy_interfaces =
#proxy_interfaces = 1.2.3.4
# The mydestination parameter specifies the list of domains that this
# machine considers itself the final destination for.
# These domains are routed to the delivery agent specified with the
# local_transport parameter setting. By default, that is the UNIX
# compatible delivery agent that lookups all recipients in /etc/passwd
# and /etc/aliases or their equivalent.
# The default is $myhostname + localhost.$mydomain. On a mail domain
# gateway, you should also include $mydomain.
# Do not specify the names of virtual domains - those domains are
# specified elsewhere (see VIRTUAL_README).
# Do not specify the names of domains that this machine is backup MX
# host for. Specify those names via the relay_domains settings for
# the SMTP server, or use permit_mx_backup if you are lazy (see
# STANDARD_CONFIGURATION_README).
# The local machine is always the final destination for mail addressed
# to user@[the.net.work.address] of an interface that the mail system
# receives mail on (see the inet_interfaces parameter).
# Specify a list of host or domain names, /file/name or type:table
# patterns, separated by commas and/or whitespace. A /file/name
# pattern is replaced by its contents; a type:table is matched when
# a name matches a lookup key (the right-hand side is ignored).
# Continue long lines by starting the next line with whitespace.
# See also below, section "REJECTING MAIL FOR UNKNOWN LOCAL USERS".
#mydestination = $myhostname, localhost.$mydomain, localhost
#mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain
#mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain,
#       mail.$mydomain, www.$mydomain, ftp.$mydomain
# REJECTING MAIL FOR UNKNOWN LOCAL USERS
# The local_recipient_maps parameter specifies optional lookup tables
# with all names or addresses of users that are local with respect
# to $mydestination, $inet_interfaces or $proxy_interfaces.
# If this parameter is defined, then the SMTP server will reject
# mail for unknown local users. This parameter is defined by default.
# To turn off local recipient checking in the SMTP server, specify
# local_recipient_maps = (i.e. empty).
# The default setting assumes that you use the default Postfix local
# delivery agent for local delivery. You need to update the
# local_recipient_maps setting if:
# - You define $mydestination domain recipients in files other than
#   /etc/passwd, /etc/aliases, or the $virtual_alias_maps files.
#   For example, you define $mydestination domain recipients in
#   the $virtual_mailbox_maps files.
# - You redefine the local delivery agent in master.cf.
# - You redefine the "local_transport" setting in main.cf.
# - You use the "luser_relay", "mailbox_transport", or "fallback_transport"
#   feature of the Postfix local delivery agent (see local(8)).
# Details are described in the LOCAL_RECIPIENT_README file.
# Beware: if the Postfix SMTP server runs chrooted, you probably have
# to access the passwd file via the proxymap service, in order to
# overcome chroot restrictions. The alternative, having a copy of
# the system passwd file in the chroot jail is just not practical.
# The right-hand side of the lookup tables is conveniently ignored.
# In the left-hand side, specify a bare username, an @domain.tld
# wild-card, or specify a [email protected] address.
#local_recipient_maps = unix:passwd.byname $alias_maps
#local_recipient_maps = proxy:unix:passwd.byname $alias_maps
#local_recipient_maps =
# The unknown_local_recipient_reject_code specifies the SMTP server
# response code when a recipient domain matches $mydestination or
# ${proxy,inet}_interfaces, while $local_recipient_maps is non-empty
# and the recipient address or address local-part is not found.
# The default setting is 550 (reject mail) but it is safer to start
# with 450 (try again later) until you are certain that your
# local_recipient_maps settings are OK.
unknown_local_recipient_reject_code = 550
# TRUST AND RELAY CONTROL
# The mynetworks parameter specifies the list of "trusted" SMTP
# clients that have more privileges than "strangers".
# In particular, "trusted" SMTP clients are allowed to relay mail
# through Postfix. See the smtpd_recipient_restrictions parameter
# in postconf(5).
# You can specify the list of "trusted" network addresses by hand
# or you can let Postfix do it for you (which is the default).
# By default (mynetworks_style = subnet), Postfix "trusts" SMTP
# clients in the same IP subnetworks as the local machine.
# On Linux, this does works correctly only with interfaces specified
# with the "ifconfig" command.
# Specify "mynetworks_style = class" when Postfix should "trust" SMTP
# clients in the same IP class A/B/C networks as the local machine.
# Don't do this with a dialup site - it would cause Postfix to "trust"
# your entire provider's network. Instead, specify an explicit
# mynetworks list by hand, as described below.
# Specify "mynetworks_style = host" when Postfix should "trust"
# only the local machine.
#mynetworks_style = class
#mynetworks_style = subnet
#mynetworks_style = host
# Alternatively, you can specify the mynetworks list by hand, in
# which case Postfix ignores the mynetworks_style setting.
# Specify an explicit list of network/netmask patterns, where the
# mask specifies the number of bits in the network part of a host
# address.
# You can also specify the absolute pathname of a pattern file instead
# of listing the patterns here. Specify type:table for table-based lookups
# (the value on the table right-hand side is not used).
#mynetworks = 168.100.189.0/28, 127.0.0.0/8
#mynetworks = $config_directory/mynetworks
#mynetworks = hash:/etc/postfix/network_table
# The relay_domains parameter restricts what destinations this system will
# relay mail to. See the smtpd_recipient_restrictions description in
# postconf(5) for detailed information.
# By default, Postfix relays mail
# - from "trusted" clients (IP address matches $mynetworks) to any destination,
# - from "untrusted" clients to destinations that match $relay_domains or
#   subdomains thereof, except addresses with sender-specified routing.
# The default relay_domains value is $mydestination.
# In addition to the above, the Postfix SMTP server by default accepts mail
# that Postfix is final destination for:
# - destinations that match $inet_interfaces or $proxy_interfaces,
# - destinations that match $mydestination
# - destinations that match $virtual_alias_domains,
# - destinations that match $virtual_mailbox_domains.
# These destinations do not need to be listed in $relay_domains.
# Specify a list of hosts or domains, /file/name patterns or type:name
# lookup tables, separated by commas and/or whitespace. Continue
# long lines by starting the next line with whitespace. A file name
# is replaced by its contents; a type:name table is matched when a
# (parent) domain appears as lookup key.
# NOTE: Postfix will not automatically forward mail for domains that
# list this system as their primary or backup MX host. See the
# permit_mx_backup restriction description in postconf(5).
#relay_domains = $mydestination
# INTERNET OR INTRANET
# The relayhost parameter specifies the default host to send mail to
# when no entry is matched in the optional transport(5) table. When
# no relayhost is given, mail is routed directly to the destination.
# On an intranet, specify the organizational domain name. If your
# internal DNS uses no MX records, specify the name of the intranet
# gateway host instead.
# In the case of SMTP, specify a domain, host, host:port, [host]:port,
# [address] or [address]:port; the form [host] turns off MX lookups.
# If you're connected via UUCP, see also the default_transport parameter.
#relayhost = $mydomain
#relayhost = [gateway.my.domain]
#relayhost = [mailserver.isp.tld]
#relayhost = uucphost
#relayhost = [an.ip.add.ress]
# REJECTING UNKNOWN RELAY USERS
# The relay_recipient_maps parameter specifies optional lookup tables
# with all addresses in the domains that match $relay_domains.
# If this parameter is defined, then the SMTP server will reject
# mail for unknown relay users. This feature is off by default.
# The right-hand side of the lookup tables is conveniently ignored.
# In the left-hand side, specify an @domain.tld wild-card, or specify
# a [email protected] address.
#relay_recipient_maps = hash:/etc/postfix/relay_recipients
# INPUT RATE CONTROL
# The in_flow_delay configuration parameter implements mail input
# flow control. This feature is turned on by default, although it
# still needs further development (it's disabled on SCO UNIX due
# to an SCO bug).
# A Postfix process will pause for $in_flow_delay seconds before
# accepting a new message, when the message arrival rate exceeds the
# message delivery rate. With the default 100 SMTP server process
# limit, this limits the mail inflow to 100 messages a second more
# than the number of messages delivered per second.
# Specify 0 to disable the feature. Valid delays are 0..10.
#in_flow_delay = 1s
# ADDRESS REWRITING
# The ADDRESS_REWRITING_README document gives information about
# address masquerading or other forms of address rewriting including
# username->Firstname.Lastname mapping.
# ADDRESS REDIRECTION (VIRTUAL DOMAIN)
# The VIRTUAL_README document gives information about the many forms
# of domain hosting that Postfix supports.
# "USER HAS MOVED" BOUNCE MESSAGES
# See the discussion in the ADDRESS_REWRITING_README document.
# TRANSPORT MAP
# See the discussion in the ADDRESS_REWRITING_README document.
# ALIAS DATABASE
# The alias_maps parameter specifies the list of alias databases used
# by the local delivery agent. The default list is system dependent.
# On systems with NIS, the default is to search the local alias
# database, then the NIS alias database. See aliases(5) for syntax
# details.
# If you change the alias database, run "postalias /etc/aliases" (or
# wherever your system stores the mail alias file), or simply run
# "newaliases" to build the necessary DBM or DB file.
# It will take a minute or so before changes become visible. Use
# "postfix reload" to eliminate the delay.
#alias_maps = dbm:/etc/aliases
#alias_maps = hash:/etc/aliases
#alias_maps = hash:/etc/aliases, nis:mail.aliases
#alias_maps = netinfo:/aliases
# The alias_database parameter specifies the alias database(s) that
# are built with "newaliases" or "sendmail -bi". This is a separate
# configuration parameter, because alias_maps (see above) may specify
# tables that are not necessarily all under control by Postfix.
#alias_database = dbm:/etc/aliases
#alias_database = dbm:/etc/mail/aliases
#alias_database = hash:/etc/aliases
#alias_database = hash:/etc/aliases, hash:/opt/majordomo/aliases
# ADDRESS EXTENSIONS (e.g., user+foo)
# The recipient_delimiter parameter specifies the separator between
# user names and address extensions (user+foo). See canonical(5),
# local(8), relocated(5) and virtual(5

Ok 1st one. The warning restriction message relates to this line in main.cf:
smtpd_helo_restrictions = permit_sasl_authenticated permit_mynetworks check_helo_access hash:/etc/postfix/helo_access reject_non_fqdn_hostname reject_invalid_hostname permit reject_invalid_helo_hostname
The last reject occurs after the single word "permit" and is ignored.
However, that's not the problem.
I'm not exactly sure what's happening, but this might be a clue.
It would appear that either postfix is not being able to create the socket for private/policy or it's somehow created with the wrong permissions. You might need to ramp up the debug level to get a better idea.
You could check if it's being created by "netstat -a | grep private/policy" in terminal.
My guess is that it's not being created because there is no setup statement in your master.cf file, but I don't understand why postfix would be looking for it if it isn't set up. Private/policy I think relates to grey listing. Maybe gives you a hint.

Repaing Permissions = Group Differ on "private/etc/cups", should be 0, grou

Repaing Permissions = Group Differ on "private/etc/cups", should be 0, groups is 26.
It says this everytime, even when it was brand new...
What does this mean? Whay doesn't it go away after repairing?

This error message has been occurring since Mac OS X 10.5.4 I believe, it's not harmful in any way to the operation of your Mac, so I wouldn't worry about it. I'm sure Apple will have this fixed in a future update.

./private permissions ?

Similar Messages

Maybe you are looking for