Filters or rules

how can I set up filters to send specific emails to different mailboxes on my device?
Or to delete automatically spam emails from certain domains?
I cannot find any settings so any help gratefully accepted.

Has anyone worked out how to do this yet?

Similar Messages

  • Filters and rules for Data Synchronizer

    Unfortunately or luckily our datasync server is positioned in the internal
    network. The main reason is the archiving solution for groupwise mail which
    uses a special connector on the datasync server to capture all email for
    specific mailboxes. So the entire mailflow can remain in our internal
    network and is not transferd out in the DMZ.
    But for few devices (like iPhone, iPad or smartphones with Android) with active
    sync protocol I want to sync the groupwise email, appointment and contacts
    to that devices.
    My problem, however is that the mobile devices want to use a secure connection on port 443 to get over 2 Bordermanager 3.9 SP2 servers.
    I did́ t find any examples on filters and rules in the documentation to
    do this.
    My idea is to use a nated public ip adress on the outer BM-server and
    acceleration on the inner BM-server.
    Maybe I am wrong and there are or is a better solutions.
    It would be great, if there is anyone who can help me with this problem
    Best regards

    jeep,
    It appears that in the past few days you have not received a response to your
    posting. That concerns us, and has triggered this automated reply.
    Has your problem been resolved? If not, you might try one of the following options:
    - Visit http://support.novell.com and search the knowledgebase and/or check all
    the other self support options and support programs available.
    - You could also try posting your message again. Make sure it is posted in the
    correct newsgroup. (http://forums.novell.com)
    Be sure to read the forum FAQ about what to expect in the way of responses:
    http://forums.novell.com/faq.php
    If this is a reply to a duplicate posting, please ignore and accept our apologies
    and rest assured we will issue a stern reprimand to our posting bot.
    Good luck!
    Your Novell Product Support Forums Team
    http://support.novell.com/forums/

  • Filtering assoc rules using subset method.

    Hello,
    Am trying to filter the association rules using subset method of arules package.
    I have a vector of items that are to be filtered from LHS/RHS.
    Here is the sample code that i have used.
    metalAssoc.mod <-ore.odmAssocRules(~.,NBAssocreqOF,case.id.column="TRANSACTION_VALUE",item.id.column = "PARAM_NAME",
      item.value.column = "PARAM_VALUE_BIN",min.support = 0.05 ,min.confidence = 0.5,max.rule.length = 5)
    rules <- rules(metalAssoc.mod)
    arules <- ore.pull(rules)
    1. Able to filter the rules using below condition.
    arules.subset <- subset(arules, subset= rhs %pin% "Temperature" |  rhs %pin% "Pressure" )
    2. We get a string like  "Temperature";"Pressure" to the function as input.
    Tried forming a vector out of the string and
    arules.subset <- subset(arules, subset= rhs %pin% c( "Temperature", "Pressure")
    This command throws the below error.
    Error in rhs %in% c("Pressure", "Temperature") :
      table contains an unknown item label
    3. Tried forming a string str with valuerhs %pin% "Temperature" |  rhs %pin% "Pressure"
    arules.subset <- subset(arules, subset= str )
    Got the below error
    Error in .translate_index(i, rownames(x), nrow(x)) :
      subscript out of bounds
    Our aim is to filter the rules based on the list of items from RHS/LHS that are passed as a function variable.
    Any help is greatly appreciated.
    Thanks,
    Swathi.

    Swathi,
    If I understand correctly, the following example from the ore.odmAssocRules help file accomplishes what you want using the functions itemsets() along with subset():
    set.seed(7654)
    id <- 1:10
    color <- sample(c("B", "Y", "W", "G"), 10, replace=TRUE)
    shape <- sample(c("tri", "rect", "round"), 10, replace=TRUE)
    state <- sample(c("MA", "CA", "NY"), 10, replace=TRUE)
    data3.ore <- ore.frame(ID=id, COLOR=color, SHAPE=shape, STATE=state)
    ar.mod3 <- ore.odmAssocRules(~., data3.ore, case.id.column = "ID",
             min.support = 0.15, min.confidence = 0.05, max.rule.length = 2)
    rules <- subset(rules(ar.mod3), min.confidence=0.5,
             lhs=list(SHAPE="tri", COLOR="B"), orderby="lift")
    itemsets <- subset(itemsets(ar.mod3), min.support=0.35)
    To view the help file for ore.odmAssocRules, type at the R command prompt:
    ?ore.odmAssocRules
    Sherry

  • Mail doesn't keep junk mail filtering and rules

    I noticed that all over sudden whenever I close mail the rules and junk mail setting in mails prefs are not kept anymore so that
    I have to enable each rule and junk mail filtering whenever I open mail again.
    Used to work fine.
    Any idea / remedy ?

    Open Disk Utility and Repair disk permissions on the First Aid tab.
    Then, Restart and boot into Recovery Mode by holding down cmd-r on restart until you see a gray screen. When the Mac boots, you will be presented with some options. Choose Disk Utility and select your Hard drive volume (Macintosh HD is the default name). Then, on the First Aid tab, click Repair Disk (not permissions).
    If that doesn't help, you could try installing the 10.8.2 combo updater from the Apple Downloads site:
    http://support.apple.com/kb/DL1581

  • Have iphone5 & ipad 3 with Outlook Exchange 2003 emails. Random emails aren't delivered to my IOS devices but appear on my PC. Using no filters or rules. Is there a fix?

    Have iphone5 &amp; ipad 3 with Outlook Exchange 2003 emails. Random emails aren't delivered to my IOS devices but appear on my PC. Emails have no attachments nor am i Using any filters. Is there a fix?

    Does anyone have any input here? The tech team at work just stonewalls me when I tell them I have an iPhone and being able to check my emails was one of the main deciding factors in getting one for me.

  • Junk Mail Filtering - is it me or is it just rubbish?

    Apologies if this has been posted elsewhere, but didn't have the patience to wade through all the threads. Hopefully someone can help...
    Frankly, I think the filtering on Mail (using 3.5 with OSX 10.5.6) is hopeless. Simply put, I've tried configuring it every which way in Preferences but the same issues persist. The main one being that when I configure to "exclude" those in my address book and/or previous recipients list from junk mail filtering ...people in my address book (SPECIFICALLY ME) still end up in the junk mail folder.
    I have 2 accounts: Mail.com (POP3) and Gmail (IMAP) and I use an iPhone for mobile access. And I have a work email. All three are in my address card in Address Book.
    Yet whenever I send myself (or anyone else) an email -- either from work or from my iPhone or even from within Mail -- it still ends up in the junk mail folder.
    I think the problem is that Mail's filtering doesn't look at email addresses. It must look at how the name is set up??? i.e., LAST FIRST or FIRST LAST, etc. and when any of these don't match up it puts it into junk mail folder????
    It just seems rubbish to me. Outlook had much more sophisticated filtering options\rule set up.
    Anyone got any ideas on how to solve this? Thanks.

    Mulder wrote:
    If you have multiple email addresses in your card in Address Book, which messages are going to Junk, and what email address was used?
    All three emails go to junk. My work to either personal address. Gmail to Mail and Mail to Gmail emails all go to junk
    Have you tried setting up the Junk filter so that:
    If any of the following conditions are met:
    *Sender is not in my Address Book*
    *Sender is not in my Previous Recipients*
    Message is Junk Mail
    Perform the following actions:
    *Move message to mailbox: (Junk mailbox On My Mac)*
    Yep. Tried that. Still didn't work. Even tried ticking "not junk" on each of the several tests I've sent myself -- and then re-sent more tests, which still ended up in junk????
    As I said, I've tried virtually every possible configuration of boxes ticked and unticked and nothing...
    My latest setting (using your advanced rules above) were:
    Enable Junk Mail - ticked
    When Junk Mail arrives - 'perform custom actions'
    Msgs Exempt - In address book and previous recipients both ticked. Use my full name unticked
    Trust ISP headers - unticked
    Filter before applying rules - have tried this both ticked and unticked... same result
    Thanks,
    The Smoking Man
    PS - Should add that when others send me email to the Gmail or Mail accounts they properly go to inbox, not junk. It's just when I send myself something (anything, really)...

  • Mail and GMail and Filters?!

    i am realizing i don't understand something. i use mail on my laptop, desktop and iphone using IMAP. i have a GMail and many, many other accounts.
    in order to retain mail but not have it clog up IMAP, i DOWNLOAD this mail by /moving/ it to the ON MY MAC section of my desktop machine. so this mail shows up in FOLDERS under "ON MY MAC". so my understanding is that this mail is no longer on IMAP and instead it is in Mail basically residing on my hard drive somewhere.
    so now i want to /organize/ some of my mail and to /filter/ some incoming mail. so now i am noticing that i have set up some FOLDERS that are listed under the portion of my GMAIL account that shows up UNDER the ON MY MAC area. i mean, it is not /nested/ under this listing but it does show up under this listing along with all my other accounts. under each of these accounts is listed a series of folders which includes in all cases one titled "Mail".
    ALSO, i have a series of FOLDERS that i set up under my GMAIL account that are listed down here with the intention of using these to FILTER incoming mail into my GMail account. the reason i did this is that i am not seeing a way to see this
    i am wondering a couple of things.
    1. am i correct in thinking that the mail that goes into the GMail account is basically a IMAP folder that can be seen on all my devices? and if so, can i set up one of these in ANY of my IMAP accounts simply by creating a folder in this account? if so, is there a good reason to create one of these folders in my GMAIL account as opposed to one of these other accounts? i mean, for some reason at one point i was thinking that it was necessary to create these folders in GMail (or that there was some benefit to doing it this way) but now i am not so sure.
    2. if i set up a FILTER in Mac Mail how does this work? i mean, if i set one up on my desktop machine does Mac Mail need to be on for the filter to take effect? i see one listed on my desktop and it is not listed on my laptop so it must be machine specific.
    3. if i want to start FILTERING Mail can i do this by just using Rules in Mac on my desktop?
    4. anyone out there sent all their Mail to Google and let google handle all of this?
    5. do Mail rules/filters have problems?
    i don't want to spend a ton more time trying to fix something if it is broke but at the same time i don't want to have my inbox as messy as it looks right now.
    THANKS

    Q.1 part 1: Gmail isn't really IMAP, but it can act more or less like it. (One way that Gmail isn't really IMAP is that oneGmail message can have multiple tags, which makes it look like it is in multiple IMAP folders. Another is that every Gmail message is in a special All Mail "folder" in addition to any tag "folder(s)."
    Q.1 part 2: Yes, you should be able to set up folders in any IMAP account.
    Q.1 part 3: One possible reason to use Gmail for this is that Gmail storage quotas are higher than for many other free accounts.
    Related point: Another approach is to spread out your folders among several servers, either to expand the total quota or for functional reasons.
    Q.2: Yes, the Mail application must be running and fetching mail for its filters to be active. Yes, filters are machine-specific, but they can interact. Whichever machine happens to notice a new message in its inbox first will start trying to match the message to its filters. If another machine then notices the same new message in the inbox before the first machine moves it out, it will also try to match the message to its filters. If two filters on different machines try to move the same message, whether to the same folder or different folders, the results are ill-defined. I have observed one message appearing twice after filtering. This is called a "race condition."
    Q.3:  Yes, you can start by defining filters on your desktop machine.
    Related point: Some mail service providers let you run filters on incoming mail before the mail ever hits your inbox. This would eliminate the possibility of a race condition, since none of your clients would ever see those messages in the inbox. A limitation of this feature is that server-based filters are usually limited to moving mail from that server's inbox to another folder on the same server. Gmail and iCloud offer server filters, as do many but not all IMAP-based mail services.
    Q.4: Probably somebody has, but I have not.
    Q.5: Other than the possibility of a race condition as described above, Mail filters (called "rules") have limitations in what you can search for and the complexity of the condition allowed. Some server-based filters are capable of more, some are more restricted.

  • Disabling junk mail filtering for specific domains

    I have a situation where I am getting dozens of messages from individuals all in a specific domain, and all are good messages which I want in my inbox; Mail however thinks they are all junk and moves them to the junk folder. They are NOT brown so I cannot select them and say they are not junk mail, they look like regular email. These are from people I do NOT want in my address book yet they are messages I need to respond to.
    How can I tell the junk mail filter that massages from a given domain should not be filtered? In short, I want just the right-hand-side of the address, the domain component, to be given the OKAY!
    Thanks - Lawrence

    Thanks - I tried the advance tab but could not see how to specify a domain but now I look again I see that there is a way - I think. But Kappy, what you say tells me something I did not know: I thought that filters, rules, et al, were applied when a message is in the inbox - but I have this wrong I think. If I read your reply rightly - the message is examined for junk filters, rules, et al, BEFORE it gets assigned to ANY mailbox! Am I right? This is how your suggestion would work. So I can have an initial rule that simple uses a list of approved domains - and sticks anything from such a domain into the inbox where no more filtering or rule analysis will take place. And the more I think about this, the more it makes sense.
    Thanks - Lawrence

  • LVM Volumes not available after update

    Hi All!
    I haven't updated my system for about two months and today I updated it. Now I have the problem that I cannot boot properly. I have my root partition in an LVM volume and on boot I get the message
    ERROR: device 'UUID=xxx' not found. Skipping fs
    ERROR: Unable to find root device 'UUID=xxx'
    After that I land in the recovery shell. After some research I found, that "lvm lvdisplay" showed that my volumes where not available and I had to reenable them with "lvm vgchange -a y".
    Issuing any lvm command also produced the following warning:
    WARNING: lvmetad is running but disabled. Restart lvmetad before enabling it!
    Anyway, after issuing the commands and exiting the recovery shell, the system booted again. However, I would prefer being able to boot without manual actions.
    Thanks in advance!
    Further information:
    vgdisplay
    --- Volume group ---
    VG Name ArchLVM
    System ID
    Format lvm2
    Metadata Areas 1
    Metadata Sequence No 3
    VG Access read/write
    VG Status resizable
    MAX LV 0
    Cur LV 2
    Open LV 1
    Max PV 0
    Cur PV 1
    Act PV 1
    VG Size 232.69 GiB
    PE Size 4.00 MiB
    Total PE 59568
    Alloc PE / Size 59568 / 232.69 GiB
    Free PE / Size 0 / 0
    VG UUID SoB3M1-v1fD-1abI-PNJ3-6IOn-FfdI-0RoLK5
    lvdisplay (LV Status was 'not available' right after booting)
    --- Logical volume ---
    LV Path /dev/ArchLVM/Swap
    LV Name Swap
    VG Name ArchLVM
    LV UUID XRYBrz-LojR-k6SD-XIxV-wHnY-f3VG-giKL6V
    LV Write Access read/write
    LV Creation host, time archiso, 2014-05-16 14:43:06 +0200
    LV Status available
    # open 0
    LV Size 8.00 GiB
    Current LE 2048
    Segments 1
    Allocation inherit
    Read ahead sectors auto
    - currently set to 256
    Block device 254:0
    --- Logical volume ---
    LV Path /dev/ArchLVM/Root
    LV Name Root
    VG Name ArchLVM
    LV UUID lpjDl4-Jqzu-ZWkq-Uphc-IaOo-6Rzd-cIh5yv
    LV Write Access read/write
    LV Creation host, time archiso, 2014-05-16 14:43:27 +0200
    LV Status available
    # open 1
    LV Size 224.69 GiB
    Current LE 57520
    Segments 1
    Allocation inherit
    Read ahead sectors auto
    - currently set to 256
    Block device 254:1
    /etc/fstab
    # /etc/fstab: static file system information
    # <file system> <dir> <type> <options> <dump> <pass>
    # /dev/mapper/ArchLVM-Root
    UUID=2db82d1a-47a4-4e30-a819-143e8fb75199 / ext4 rw,relatime,data=ordered 0 1
    #/dev/mapper/ArchLVM-Root / ext4 rw,relatime,data=ordered 0 1
    # /dev/sda1
    UUID=72691888-a781-4cdd-a98e-2613d87925d0 /boot ext2 rw,relatime 0 2
    /etc/mkinitcpio.conf
    # vim:set ft=sh
    # MODULES
    # The following modules are loaded before any boot hooks are
    # run. Advanced users may wish to specify all system modules
    # in this array. For instance:
    # MODULES="piix ide_disk reiserfs"
    MODULES=""
    # BINARIES
    # This setting includes any additional binaries a given user may
    # wish into the CPIO image. This is run last, so it may be used to
    # override the actual binaries included by a given hook
    # BINARIES are dependency parsed, so you may safely ignore libraries
    BINARIES=""
    # FILES
    # This setting is similar to BINARIES above, however, files are added
    # as-is and are not parsed in any way. This is useful for config files.
    FILES=""
    # HOOKS
    # This is the most important setting in this file. The HOOKS control the
    # modules and scripts added to the image, and what happens at boot time.
    # Order is important, and it is recommended that you do not change the
    # order in which HOOKS are added. Run 'mkinitcpio -H <hook name>' for
    # help on a given hook.
    # 'base' is _required_ unless you know precisely what you are doing.
    # 'udev' is _required_ in order to automatically load modules
    # 'filesystems' is _required_ unless you specify your fs modules in MODULES
    # Examples:
    ## This setup specifies all modules in the MODULES setting above.
    ## No raid, lvm2, or encrypted root is needed.
    # HOOKS="base"
    ## This setup will autodetect all modules for your system and should
    ## work as a sane default
    # HOOKS="base udev autodetect block filesystems"
    ## This setup will generate a 'full' image which supports most systems.
    ## No autodetection is done.
    # HOOKS="base udev block filesystems"
    ## This setup assembles a pata mdadm array with an encrypted root FS.
    ## Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
    # HOOKS="base udev block mdadm encrypt filesystems"
    ## This setup loads an lvm2 volume group on a usb device.
    # HOOKS="base udev block lvm2 filesystems"
    ## NOTE: If you have /usr on a separate partition, you MUST include the
    # usr, fsck and shutdown hooks.
    HOOKS="base udev autodetect modconf block lvm2 filesystems keyboard fsck"
    # COMPRESSION
    # Use this to compress the initramfs image. By default, gzip compression
    # is used. Use 'cat' to create an uncompressed image.
    #COMPRESSION="gzip"
    #COMPRESSION="bzip2"
    #COMPRESSION="lzma"
    #COMPRESSION="xz"
    #COMPRESSION="lzop"
    #COMPRESSION="lz4"
    # COMPRESSION_OPTIONS
    # Additional options for the compressor
    #COMPRESSION_OPTIONS=""
    /boot/grub/grub.cfg
    # DO NOT EDIT THIS FILE
    # It is automatically generated by grub-mkconfig using templates
    # from /etc/grub.d and settings from /etc/default/grub
    ### BEGIN /etc/grub.d/00_header ###
    insmod part_gpt
    insmod part_msdos
    if [ -s $prefix/grubenv ]; then
    load_env
    fi
    if [ "${next_entry}" ] ; then
    set default="${next_entry}"
    set next_entry=
    save_env next_entry
    set boot_once=true
    else
    set default="0"
    fi
    if [ x"${feature_menuentry_id}" = xy ]; then
    menuentry_id_option="--id"
    else
    menuentry_id_option=""
    fi
    export menuentry_id_option
    if [ "${prev_saved_entry}" ]; then
    set saved_entry="${prev_saved_entry}"
    save_env saved_entry
    set prev_saved_entry=
    save_env prev_saved_entry
    set boot_once=true
    fi
    function savedefault {
    if [ -z "${boot_once}" ]; then
    saved_entry="${chosen}"
    save_env saved_entry
    fi
    function load_video {
    if [ x$feature_all_video_module = xy ]; then
    insmod all_video
    else
    insmod efi_gop
    insmod efi_uga
    insmod ieee1275_fb
    insmod vbe
    insmod vga
    insmod video_bochs
    insmod video_cirrus
    fi
    if [ x$feature_default_font_path = xy ] ; then
    font=unicode
    else
    insmod part_msdos
    insmod lvm
    insmod ext2
    set root='lvmid/SoB3M1-v1fD-1abI-PNJ3-6IOn-FfdI-0RoLK5/lpjDl4-Jqzu-ZWkq-Uphc-IaOo-6Rzd-cIh5yv'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint='lvmid/SoB3M1-v1fD-1abI-PNJ3-6IOn-FfdI-0RoLK5/lpjDl4-Jqzu-ZWkq-Uphc-IaOo-6Rzd-cIh5yv' 2db82d1a-47a4-4e30-a819-143e8fb75199
    else
    search --no-floppy --fs-uuid --set=root 2db82d1a-47a4-4e30-a819-143e8fb75199
    fi
    font="/usr/share/grub/unicode.pf2"
    fi
    if loadfont $font ; then
    set gfxmode=auto
    load_video
    insmod gfxterm
    fi
    terminal_input console
    terminal_output gfxterm
    if [ x$feature_timeout_style = xy ] ; then
    set timeout_style=menu
    set timeout=5
    # Fallback normal timeout code in case the timeout_style feature is
    # unavailable.
    else
    set timeout=5
    fi
    ### END /etc/grub.d/00_header ###
    ### BEGIN /etc/grub.d/10_linux ###
    menuentry 'Arch Linux' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-2db82d1a-47a4-4e30-a819-143e8fb75199' {
    load_video
    set gfxpayload=keep
    insmod gzio
    insmod part_msdos
    insmod ext2
    set root='hd0,msdos1'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 72691888-a781-4cdd-a98e-2613d87925d0
    else
    search --no-floppy --fs-uuid --set=root 72691888-a781-4cdd-a98e-2613d87925d0
    fi
    echo 'Loading Linux linux ...'
    linux /vmlinuz-linux root=UUID=2db82d1a-47a4-4e30-a819-143e8fb75199 rw quiet
    echo 'Loading initial ramdisk ...'
    initrd /initramfs-linux.img
    submenu 'Advanced options for Arch Linux' $menuentry_id_option 'gnulinux-advanced-2db82d1a-47a4-4e30-a819-143e8fb75199' {
    menuentry 'Arch Linux, with Linux linux' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-linux-advanced-2db82d1a-47a4-4e30-a819-143e8fb75199' {
    load_video
    set gfxpayload=keep
    insmod gzio
    insmod part_msdos
    insmod ext2
    set root='hd0,msdos1'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 72691888-a781-4cdd-a98e-2613d87925d0
    else
    search --no-floppy --fs-uuid --set=root 72691888-a781-4cdd-a98e-2613d87925d0
    fi
    echo 'Loading Linux linux ...'
    linux /vmlinuz-linux root=UUID=2db82d1a-47a4-4e30-a819-143e8fb75199 rw quiet
    echo 'Loading initial ramdisk ...'
    initrd /initramfs-linux.img
    menuentry 'Arch Linux, with Linux linux (fallback initramfs)' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-linux-fallback-2db82d1a-47a4-4e30-a819-143e8fb75199' {
    load_video
    set gfxpayload=keep
    insmod gzio
    insmod part_msdos
    insmod ext2
    set root='hd0,msdos1'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 72691888-a781-4cdd-a98e-2613d87925d0
    else
    search --no-floppy --fs-uuid --set=root 72691888-a781-4cdd-a98e-2613d87925d0
    fi
    echo 'Loading Linux linux ...'
    linux /vmlinuz-linux root=UUID=2db82d1a-47a4-4e30-a819-143e8fb75199 rw quiet
    echo 'Loading initial ramdisk ...'
    initrd /initramfs-linux-fallback.img
    ### END /etc/grub.d/10_linux ###
    ### BEGIN /etc/grub.d/20_linux_xen ###
    ### END /etc/grub.d/20_linux_xen ###
    ### BEGIN /etc/grub.d/30_os-prober ###
    ### END /etc/grub.d/30_os-prober ###
    ### BEGIN /etc/grub.d/40_custom ###
    # This file provides an easy way to add custom menu entries. Simply type the
    # menu entries you want to add after this comment. Be careful not to change
    # the 'exec tail' line above.
    ### END /etc/grub.d/40_custom ###
    ### BEGIN /etc/grub.d/41_custom ###
    if [ -f ${config_directory}/custom.cfg ]; then
    source ${config_directory}/custom.cfg
    elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then
    source $prefix/custom.cfg;
    fi
    ### END /etc/grub.d/41_custom ###
    ### BEGIN /etc/grub.d/60_memtest86+ ###
    ### END /etc/grub.d/60_memtest86+ ###
    Last edited by Kirodema (2014-07-16 07:31:34)

    use_lvmetad = 0
    lvm2-lvmetad is not enabled or running on my system. Shall I activate it?
    # This is an example configuration file for the LVM2 system.
    # It contains the default settings that would be used if there was no
    # /etc/lvm/lvm.conf file.
    # Refer to 'man lvm.conf' for further information including the file layout.
    # To put this file in a different directory and override /etc/lvm set
    # the environment variable LVM_SYSTEM_DIR before running the tools.
    # N.B. Take care that each setting only appears once if uncommenting
    # example settings in this file.
    # This section allows you to set the way the configuration settings are handled.
    config {
    # If enabled, any LVM2 configuration mismatch is reported.
    # This implies checking that the configuration key is understood
    # by LVM2 and that the value of the key is of a proper type.
    # If disabled, any configuration mismatch is ignored and default
    # value is used instead without any warning (a message about the
    # configuration key not being found is issued in verbose mode only).
    checks = 1
    # If enabled, any configuration mismatch aborts the LVM2 process.
    abort_on_errors = 0
    # Directory where LVM looks for configuration profiles.
    profile_dir = "/etc/lvm/profile"
    # This section allows you to configure which block devices should
    # be used by the LVM system.
    devices {
    # Where do you want your volume groups to appear ?
    dir = "/dev"
    # An array of directories that contain the device nodes you wish
    # to use with LVM2.
    scan = [ "/dev" ]
    # If set, the cache of block device nodes with all associated symlinks
    # will be constructed out of the existing udev database content.
    # This avoids using and opening any inapplicable non-block devices or
    # subdirectories found in the device directory. This setting is applied
    # to udev-managed device directory only, other directories will be scanned
    # fully. LVM2 needs to be compiled with udev support for this setting to
    # take effect. N.B. Any device node or symlink not managed by udev in
    # udev directory will be ignored with this setting on.
    obtain_device_list_from_udev = 1
    # If several entries in the scanned directories correspond to the
    # same block device and the tools need to display a name for device,
    # all the pathnames are matched against each item in the following
    # list of regular expressions in turn and the first match is used.
    preferred_names = [ ]
    # Try to avoid using undescriptive /dev/dm-N names, if present.
    # preferred_names = [ "^/dev/mpath/", "^/dev/mapper/mpath", "^/dev/[hs]d" ]
    # A filter that tells LVM2 to only use a restricted set of devices.
    # The filter consists of an array of regular expressions. These
    # expressions can be delimited by a character of your choice, and
    # prefixed with either an 'a' (for accept) or 'r' (for reject).
    # The first expression found to match a device name determines if
    # the device will be accepted or rejected (ignored). Devices that
    # don't match any patterns are accepted.
    # Be careful if there there are symbolic links or multiple filesystem
    # entries for the same device as each name is checked separately against
    # the list of patterns. The effect is that if the first pattern in the
    # list to match a name is an 'a' pattern for any of the names, the device
    # is accepted; otherwise if the first pattern in the list to match a name
    # is an 'r' pattern for any of the names it is rejected; otherwise it is
    # accepted.
    # Don't have more than one filter line active at once: only one gets used.
    # Run vgscan after you change this parameter to ensure that
    # the cache file gets regenerated (see below).
    # If it doesn't do what you expect, check the output of 'vgscan -vvvv'.
    # If lvmetad is used, then see "A note about device filtering while
    # lvmetad is used" comment that is attached to global/use_lvmetad setting.
    # By default we accept every block device:
    filter = [ "a/.*/" ]
    # Exclude the cdrom drive
    # filter = [ "r|/dev/cdrom|" ]
    # When testing I like to work with just loopback devices:
    # filter = [ "a/loop/", "r/.*/" ]
    # Or maybe all loops and ide drives except hdc:
    # filter =[ "a|loop|", "r|/dev/hdc|", "a|/dev/ide|", "r|.*|" ]
    # Use anchors if you want to be really specific
    # filter = [ "a|^/dev/hda8$|", "r/.*/" ]
    # Since "filter" is often overridden from command line, it is not suitable
    # for system-wide device filtering (udev rules, lvmetad). To hide devices
    # from LVM-specific udev processing and/or from lvmetad, you need to set
    # global_filter. The syntax is the same as for normal "filter"
    # above. Devices that fail the global_filter are not even opened by LVM.
    # global_filter = []
    # The results of the filtering are cached on disk to avoid
    # rescanning dud devices (which can take a very long time).
    # By default this cache is stored in the /etc/lvm/cache directory
    # in a file called '.cache'.
    # It is safe to delete the contents: the tools regenerate it.
    # (The old setting 'cache' is still respected if neither of
    # these new ones is present.)
    # N.B. If obtain_device_list_from_udev is set to 1 the list of
    # devices is instead obtained from udev and any existing .cache
    # file is removed.
    cache_dir = "/etc/lvm/cache"
    cache_file_prefix = ""
    # You can turn off writing this cache file by setting this to 0.
    write_cache_state = 1
    # Advanced settings.
    # List of pairs of additional acceptable block device types found
    # in /proc/devices with maximum (non-zero) number of partitions.
    # types = [ "fd", 16 ]
    # If sysfs is mounted (2.6 kernels) restrict device scanning to
    # the block devices it believes are valid.
    # 1 enables; 0 disables.
    sysfs_scan = 1
    # By default, LVM2 will ignore devices used as component paths
    # of device-mapper multipath devices.
    # 1 enables; 0 disables.
    multipath_component_detection = 1
    # By default, LVM2 will ignore devices used as components of
    # software RAID (md) devices by looking for md superblocks.
    # 1 enables; 0 disables.
    md_component_detection = 1
    # By default, if a PV is placed directly upon an md device, LVM2
    # will align its data blocks with the md device's stripe-width.
    # 1 enables; 0 disables.
    md_chunk_alignment = 1
    # Default alignment of the start of a data area in MB. If set to 0,
    # a value of 64KB will be used. Set to 1 for 1MiB, 2 for 2MiB, etc.
    # default_data_alignment = 1
    # By default, the start of a PV's data area will be a multiple of
    # the 'minimum_io_size' or 'optimal_io_size' exposed in sysfs.
    # - minimum_io_size - the smallest request the device can perform
    # w/o incurring a read-modify-write penalty (e.g. MD's chunk size)
    # - optimal_io_size - the device's preferred unit of receiving I/O
    # (e.g. MD's stripe width)
    # minimum_io_size is used if optimal_io_size is undefined (0).
    # If md_chunk_alignment is enabled, that detects the optimal_io_size.
    # This setting takes precedence over md_chunk_alignment.
    # 1 enables; 0 disables.
    data_alignment_detection = 1
    # Alignment (in KB) of start of data area when creating a new PV.
    # md_chunk_alignment and data_alignment_detection are disabled if set.
    # Set to 0 for the default alignment (see: data_alignment_default)
    # or page size, if larger.
    data_alignment = 0
    # By default, the start of the PV's aligned data area will be shifted by
    # the 'alignment_offset' exposed in sysfs. This offset is often 0 but
    # may be non-zero; e.g.: certain 4KB sector drives that compensate for
    # windows partitioning will have an alignment_offset of 3584 bytes
    # (sector 7 is the lowest aligned logical block, the 4KB sectors start
    # at LBA -1, and consequently sector 63 is aligned on a 4KB boundary).
    # But note that pvcreate --dataalignmentoffset will skip this detection.
    # 1 enables; 0 disables.
    data_alignment_offset_detection = 1
    # If, while scanning the system for PVs, LVM2 encounters a device-mapper
    # device that has its I/O suspended, it waits for it to become accessible.
    # Set this to 1 to skip such devices. This should only be needed
    # in recovery situations.
    ignore_suspended_devices = 0
    # ignore_lvm_mirrors: Introduced in version 2.02.104
    # This setting determines whether logical volumes of "mirror" segment
    # type are scanned for LVM labels. This affects the ability of
    # mirrors to be used as physical volumes. If 'ignore_lvm_mirrors'
    # is set to '1', it becomes impossible to create volume groups on top
    # of mirror logical volumes - i.e. to stack volume groups on mirrors.
    # Allowing mirror logical volumes to be scanned (setting the value to '0')
    # can potentially cause LVM processes and I/O to the mirror to become
    # blocked. This is due to the way that the "mirror" segment type handles
    # failures. In order for the hang to manifest itself, an LVM command must
    # be run just after a failure and before the automatic LVM repair process
    # takes place OR there must be failures in multiple mirrors in the same
    # volume group at the same time with write failures occurring moments
    # before a scan of the mirror's labels.
    # Note that these scanning limitations do not apply to the LVM RAID
    # types, like "raid1". The RAID segment types handle failures in a
    # different way and are not subject to possible process or I/O blocking.
    # It is encouraged that users set 'ignore_lvm_mirrors' to 1 if they
    # are using the "mirror" segment type. Users that require volume group
    # stacking on mirrored logical volumes should consider using the "raid1"
    # segment type. The "raid1" segment type is not available for
    # active/active clustered volume groups.
    # Set to 1 to disallow stacking and thereby avoid a possible deadlock.
    ignore_lvm_mirrors = 1
    # During each LVM operation errors received from each device are counted.
    # If the counter of a particular device exceeds the limit set here, no
    # further I/O is sent to that device for the remainder of the respective
    # operation. Setting the parameter to 0 disables the counters altogether.
    disable_after_error_count = 0
    # Allow use of pvcreate --uuid without requiring --restorefile.
    require_restorefile_with_uuid = 1
    # Minimum size (in KB) of block devices which can be used as PVs.
    # In a clustered environment all nodes must use the same value.
    # Any value smaller than 512KB is ignored.
    # Ignore devices smaller than 2MB such as floppy drives.
    pv_min_size = 2048
    # The original built-in setting was 512 up to and including version 2.02.84.
    # pv_min_size = 512
    # Issue discards to a logical volumes's underlying physical volume(s) when
    # the logical volume is no longer using the physical volumes' space (e.g.
    # lvremove, lvreduce, etc). Discards inform the storage that a region is
    # no longer in use. Storage that supports discards advertise the protocol
    # specific way discards should be issued by the kernel (TRIM, UNMAP, or
    # WRITE SAME with UNMAP bit set). Not all storage will support or benefit
    # from discards but SSDs and thinly provisioned LUNs generally do. If set
    # to 1, discards will only be issued if both the storage and kernel provide
    # support.
    # 1 enables; 0 disables.
    issue_discards = 0
    # This section allows you to configure the way in which LVM selects
    # free space for its Logical Volumes.
    allocation {
    # When searching for free space to extend an LV, the "cling"
    # allocation policy will choose space on the same PVs as the last
    # segment of the existing LV. If there is insufficient space and a
    # list of tags is defined here, it will check whether any of them are
    # attached to the PVs concerned and then seek to match those PV tags
    # between existing extents and new extents.
    # Use the special tag "@*" as a wildcard to match any PV tag.
    # Example: LVs are mirrored between two sites within a single VG.
    # PVs are tagged with either @site1 or @site2 to indicate where
    # they are situated.
    # cling_tag_list = [ "@site1", "@site2" ]
    # cling_tag_list = [ "@*" ]
    # Changes made in version 2.02.85 extended the reach of the 'cling'
    # policies to detect more situations where data can be grouped
    # onto the same disks. Set this to 0 to revert to the previous
    # algorithm.
    maximise_cling = 1
    # Whether to use blkid library instead of native LVM2 code to detect
    # any existing signatures while creating new Physical Volumes and
    # Logical Volumes. LVM2 needs to be compiled with blkid wiping support
    # for this setting to take effect.
    # LVM2 native detection code is currently able to recognize these signatures:
    # - MD device signature
    # - swap signature
    # - LUKS signature
    # To see the list of signatures recognized by blkid, check the output
    # of 'blkid -k' command. The blkid can recognize more signatures than
    # LVM2 native detection code, but due to this higher number of signatures
    # to be recognized, it can take more time to complete the signature scan.
    use_blkid_wiping = 1
    # Set to 1 to wipe any signatures found on newly-created Logical Volumes
    # automatically in addition to zeroing of the first KB on the LV
    # (controlled by the -Z/--zero y option).
    # The command line option -W/--wipesignatures takes precedence over this
    # setting.
    # The default is to wipe signatures when zeroing.
    wipe_signatures_when_zeroing_new_lvs = 1
    # Set to 1 to guarantee that mirror logs will always be placed on
    # different PVs from the mirror images. This was the default
    # until version 2.02.85.
    mirror_logs_require_separate_pvs = 0
    # Set to 1 to guarantee that cache_pool metadata will always be
    # placed on different PVs from the cache_pool data.
    cache_pool_metadata_require_separate_pvs = 0
    # Specify the minimal chunk size (in kiB) for cache pool volumes.
    # Using a chunk_size that is too large can result in wasteful use of
    # the cache, where small reads and writes can cause large sections of
    # an LV to be mapped into the cache. However, choosing a chunk_size
    # that is too small can result in more overhead trying to manage the
    # numerous chunks that become mapped into the cache. The former is
    # more of a problem than the latter in most cases, so we default to
    # a value that is on the smaller end of the spectrum. Supported values
    # range from 32(kiB) to 1048576 in multiples of 32.
    # cache_pool_chunk_size = 64
    # Set to 1 to guarantee that thin pool metadata will always
    # be placed on different PVs from the pool data.
    thin_pool_metadata_require_separate_pvs = 0
    # Specify chunk size calculation policy for thin pool volumes.
    # Possible options are:
    # "generic" - if thin_pool_chunk_size is defined, use it.
    # Otherwise, calculate the chunk size based on
    # estimation and device hints exposed in sysfs:
    # the minimum_io_size. The chunk size is always
    # at least 64KiB.
    # "performance" - if thin_pool_chunk_size is defined, use it.
    # Otherwise, calculate the chunk size for
    # performance based on device hints exposed in
    # sysfs: the optimal_io_size. The chunk size is
    # always at least 512KiB.
    # thin_pool_chunk_size_policy = "generic"
    # Specify the minimal chunk size (in KB) for thin pool volumes.
    # Use of the larger chunk size may improve performance for plain
    # thin volumes, however using them for snapshot volumes is less efficient,
    # as it consumes more space and takes extra time for copying.
    # When unset, lvm tries to estimate chunk size starting from 64KB
    # Supported values are in range from 64 to 1048576.
    # thin_pool_chunk_size = 64
    # Specify discards behaviour of the thin pool volume.
    # Select one of "ignore", "nopassdown", "passdown"
    # thin_pool_discards = "passdown"
    # Set to 0, to disable zeroing of thin pool data chunks before their
    # first use.
    # N.B. zeroing larger thin pool chunk size degrades performance.
    # thin_pool_zero = 1
    # This section that allows you to configure the nature of the
    # information that LVM2 reports.
    log {
    # Controls the messages sent to stdout or stderr.
    # There are three levels of verbosity, 3 being the most verbose.
    verbose = 0
    # Set to 1 to suppress all non-essential messages from stdout.
    # This has the same effect as -qq.
    # When this is set, the following commands still produce output:
    # dumpconfig, lvdisplay, lvmdiskscan, lvs, pvck, pvdisplay,
    # pvs, version, vgcfgrestore -l, vgdisplay, vgs.
    # Non-essential messages are shifted from log level 4 to log level 5
    # for syslog and lvm2_log_fn purposes.
    # Any 'yes' or 'no' questions not overridden by other arguments
    # are suppressed and default to 'no'.
    silent = 0
    # Should we send log messages through syslog?
    # 1 is yes; 0 is no.
    syslog = 1
    # Should we log error and debug messages to a file?
    # By default there is no log file.
    #file = "/var/log/lvm2.log"
    # Should we overwrite the log file each time the program is run?
    # By default we append.
    overwrite = 0
    # What level of log messages should we send to the log file and/or syslog?
    # There are 6 syslog-like log levels currently in use - 2 to 7 inclusive.
    # 7 is the most verbose (LOG_DEBUG).
    level = 0
    # Format of output messages
    # Whether or not (1 or 0) to indent messages according to their severity
    indent = 1
    # Whether or not (1 or 0) to display the command name on each line output
    command_names = 0
    # A prefix to use before the message text (but after the command name,
    # if selected). Default is two spaces, so you can see/grep the severity
    # of each message.
    prefix = " "
    # To make the messages look similar to the original LVM tools use:
    # indent = 0
    # command_names = 1
    # prefix = " -- "
    # Set this if you want log messages during activation.
    # Don't use this in low memory situations (can deadlock).
    # activation = 0
    # Some debugging messages are assigned to a class and only appear
    # in debug output if the class is listed here.
    # Classes currently available:
    # memory, devices, activation, allocation, lvmetad, metadata, cache,
    # locking
    # Use "all" to see everything.
    debug_classes = [ "memory", "devices", "activation", "allocation",
    "lvmetad", "metadata", "cache", "locking" ]
    # Configuration of metadata backups and archiving. In LVM2 when we
    # talk about a 'backup' we mean making a copy of the metadata for the
    # *current* system. The 'archive' contains old metadata configurations.
    # Backups are stored in a human readable text format.
    backup {
    # Should we maintain a backup of the current metadata configuration ?
    # Use 1 for Yes; 0 for No.
    # Think very hard before turning this off!
    backup = 1
    # Where shall we keep it ?
    # Remember to back up this directory regularly!
    backup_dir = "/etc/lvm/backup"
    # Should we maintain an archive of old metadata configurations.
    # Use 1 for Yes; 0 for No.
    # On by default. Think very hard before turning this off.
    archive = 1
    # Where should archived files go ?
    # Remember to back up this directory regularly!
    archive_dir = "/etc/lvm/archive"
    # What is the minimum number of archive files you wish to keep ?
    retain_min = 10
    # What is the minimum time you wish to keep an archive file for ?
    retain_days = 30
    # Settings for the running LVM2 in shell (readline) mode.
    shell {
    # Number of lines of history to store in ~/.lvm_history
    history_size = 100
    # Miscellaneous global LVM2 settings
    global {
    # The file creation mask for any files and directories created.
    # Interpreted as octal if the first digit is zero.
    umask = 077
    # Allow other users to read the files
    #umask = 022
    # Enabling test mode means that no changes to the on disk metadata
    # will be made. Equivalent to having the -t option on every
    # command. Defaults to off.
    test = 0
    # Default value for --units argument
    units = "h"
    # Since version 2.02.54, the tools distinguish between powers of
    # 1024 bytes (e.g. KiB, MiB, GiB) and powers of 1000 bytes (e.g.
    # KB, MB, GB).
    # If you have scripts that depend on the old behaviour, set this to 0
    # temporarily until you update them.
    si_unit_consistency = 1
    # Whether or not to display unit suffix for sizes. This setting has
    # no effect if the units are in human-readable form (global/units="h")
    # in which case the suffix is always displayed.
    suffix = 1
    # Whether or not to communicate with the kernel device-mapper.
    # Set to 0 if you want to use the tools to manipulate LVM metadata
    # without activating any logical volumes.
    # If the device-mapper kernel driver is not present in your kernel
    # setting this to 0 should suppress the error messages.
    activation = 1
    # If we can't communicate with device-mapper, should we try running
    # the LVM1 tools?
    # This option only applies to 2.4 kernels and is provided to help you
    # switch between device-mapper kernels and LVM1 kernels.
    # The LVM1 tools need to be installed with .lvm1 suffices
    # e.g. vgscan.lvm1 and they will stop working after you start using
    # the new lvm2 on-disk metadata format.
    # The default value is set when the tools are built.
    # fallback_to_lvm1 = 0
    # The default metadata format that commands should use - "lvm1" or "lvm2".
    # The command line override is -M1 or -M2.
    # Defaults to "lvm2".
    # format = "lvm2"
    # Location of proc filesystem
    proc = "/proc"
    # Type of locking to use. Defaults to local file-based locking (1).
    # Turn locking off by setting to 0 (dangerous: risks metadata corruption
    # if LVM2 commands get run concurrently).
    # Type 2 uses the external shared library locking_library.
    # Type 3 uses built-in clustered locking.
    # Type 4 uses read-only locking which forbids any operations that might
    # change metadata.
    # N.B. Don't use lvmetad with locking type 3 as lvmetad is not yet
    # supported in clustered environment. If use_lvmetad=1 and locking_type=3
    # is set at the same time, LVM always issues a warning message about this
    # and then it automatically disables lvmetad use.
    locking_type = 1
    # Set to 0 to fail when a lock request cannot be satisfied immediately.
    wait_for_locks = 1
    # If using external locking (type 2) and initialisation fails,
    # with this set to 1 an attempt will be made to use the built-in
    # clustered locking.
    # If you are using a customised locking_library you should set this to 0.
    fallback_to_clustered_locking = 1
    # If an attempt to initialise type 2 or type 3 locking failed, perhaps
    # because cluster components such as clvmd are not running, with this set
    # to 1 an attempt will be made to use local file-based locking (type 1).
    # If this succeeds, only commands against local volume groups will proceed.
    # Volume Groups marked as clustered will be ignored.
    fallback_to_local_locking = 1
    # Local non-LV directory that holds file-based locks while commands are
    # in progress. A directory like /tmp that may get wiped on reboot is OK.
    locking_dir = "/run/lock/lvm"
    # Whenever there are competing read-only and read-write access requests for
    # a volume group's metadata, instead of always granting the read-only
    # requests immediately, delay them to allow the read-write requests to be
    # serviced. Without this setting, write access may be stalled by a high
    # volume of read-only requests.
    # NB. This option only affects locking_type = 1 viz. local file-based
    # locking.
    prioritise_write_locks = 1
    # Other entries can go here to allow you to load shared libraries
    # e.g. if support for LVM1 metadata was compiled as a shared library use
    # format_libraries = "liblvm2format1.so"
    # Full pathnames can be given.
    # Search this directory first for shared libraries.
    # library_dir = "/lib"
    # The external locking library to load if locking_type is set to 2.
    # locking_library = "liblvm2clusterlock.so"
    # Treat any internal errors as fatal errors, aborting the process that
    # encountered the internal error. Please only enable for debugging.
    abort_on_internal_errors = 0
    # Check whether CRC is matching when parsed VG is used multiple times.
    # This is useful to catch unexpected internal cached volume group
    # structure modification. Please only enable for debugging.
    detect_internal_vg_cache_corruption = 0
    # If set to 1, no operations that change on-disk metadata will be permitted.
    # Additionally, read-only commands that encounter metadata in need of repair
    # will still be allowed to proceed exactly as if the repair had been
    # performed (except for the unchanged vg_seqno).
    # Inappropriate use could mess up your system, so seek advice first!
    metadata_read_only = 0
    # 'mirror_segtype_default' defines which segtype will be used when the
    # shorthand '-m' option is used for mirroring. The possible options are:
    # "mirror" - The original RAID1 implementation provided by LVM2/DM. It is
    # characterized by a flexible log solution (core, disk, mirrored)
    # and by the necessity to block I/O while reconfiguring in the
    # event of a failure.
    # There is an inherent race in the dmeventd failure handling
    # logic with snapshots of devices using this type of RAID1 that
    # in the worst case could cause a deadlock.
    # Ref: https://bugzilla.redhat.com/show_bug.cgi?id=817130#c10
    # "raid1" - This implementation leverages MD's RAID1 personality through
    # device-mapper. It is characterized by a lack of log options.
    # (A log is always allocated for every device and they are placed
    # on the same device as the image - no separate devices are
    # required.) This mirror implementation does not require I/O
    # to be blocked in the kernel in the event of a failure.
    # This mirror implementation is not cluster-aware and cannot be
    # used in a shared (active/active) fashion in a cluster.
    # Specify the '--type <mirror|raid1>' option to override this default
    # setting.
    mirror_segtype_default = "raid1"
    # 'raid10_segtype_default' determines the segment types used by default
    # when the '--stripes/-i' and '--mirrors/-m' arguments are both specified
    # during the creation of a logical volume.
    # Possible settings include:
    # "raid10" - This implementation leverages MD's RAID10 personality through
    # device-mapper.
    # "mirror" - LVM will layer the 'mirror' and 'stripe' segment types. It
    # will do this by creating a mirror on top of striped sub-LVs;
    # effectively creating a RAID 0+1 array. This is suboptimal
    # in terms of providing redundancy and performance. Changing to
    # this setting is not advised.
    # Specify the '--type <raid10|mirror>' option to override this default
    # setting.
    raid10_segtype_default = "raid10"
    # The default format for displaying LV names in lvdisplay was changed
    # in version 2.02.89 to show the LV name and path separately.
    # Previously this was always shown as /dev/vgname/lvname even when that
    # was never a valid path in the /dev filesystem.
    # Set to 1 to reinstate the previous format.
    # lvdisplay_shows_full_device_path = 0
    # Whether to use (trust) a running instance of lvmetad. If this is set to
    # 0, all commands fall back to the usual scanning mechanisms. When set to 1
    # *and* when lvmetad is running (automatically instantiated by making use of
    # systemd's socket-based service activation or run as an initscripts service
    # or run manually), the volume group metadata and PV state flags are obtained
    # from the lvmetad instance and no scanning is done by the individual
    # commands. In a setup with lvmetad, lvmetad udev rules *must* be set up for
    # LVM to work correctly. Without proper udev rules, all changes in block
    # device configuration will be *ignored* until a manual 'pvscan --cache'
    # is performed. These rules are installed by default.
    # If lvmetad has been running while use_lvmetad was 0, it MUST be stopped
    # before changing use_lvmetad to 1 and started again afterwards.
    # If using lvmetad, the volume activation is also switched to automatic
    # event-based mode. In this mode, the volumes are activated based on
    # incoming udev events that automatically inform lvmetad about new PVs
    # that appear in the system. Once the VG is complete (all the PVs are
    # present), it is auto-activated. The activation/auto_activation_volume_list
    # setting controls which volumes are auto-activated (all by default).
    # A note about device filtering while lvmetad is used:
    # When lvmetad is updated (either automatically based on udev events
    # or directly by pvscan --cache <device> call), the devices/filter
    # is ignored and all devices are scanned by default. The lvmetad always
    # keeps unfiltered information which is then provided to LVM commands
    # and then each LVM command does the filtering based on devices/filter
    # setting itself.
    # To prevent scanning devices completely, even when using lvmetad,
    # the devices/global_filter must be used.
    # N.B. Don't use lvmetad with locking type 3 as lvmetad is not yet
    # supported in clustered environment. If use_lvmetad=1 and locking_type=3
    # is set at the same time, LVM always issues a warning message about this
    # and then it automatically disables lvmetad use.
    use_lvmetad = 0
    # Full path of the utility called to check that a thin metadata device
    # is in a state that allows it to be used.
    # Each time a thin pool needs to be activated or after it is deactivated
    # this utility is executed. The activation will only proceed if the utility
    # has an exit status of 0.
    # Set to "" to skip this check. (Not recommended.)
    # The thin tools are available as part of the device-mapper-persistent-data
    # package from https://github.com/jthornber/thin-provisioning-tools.
    # thin_check_executable = "/usr/bin/thin_check"
    # Array of string options passed with thin_check command. By default,
    # option "-q" is for quiet output.
    # With thin_check version 2.1 or newer you can add "--ignore-non-fatal-errors"
    # to let it pass through ignorable errors and fix them later.
    # thin_check_options = [ "-q" ]
    # Full path of the utility called to repair a thin metadata device
    # is in a state that allows it to be used.
    # Each time a thin pool needs repair this utility is executed.
    # See thin_check_executable how to obtain binaries.
    # thin_repair_executable = "/usr/bin/thin_repair"
    # Array of extra string options passed with thin_repair command.
    # thin_repair_options = [ "" ]
    # Full path of the utility called to dump thin metadata content.
    # See thin_check_executable how to obtain binaries.
    # thin_dump_executable = "/usr/bin/thin_dump"
    # If set, given features are not used by thin driver.
    # This can be helpful not just for testing, but i.e. allows to avoid
    # using problematic implementation of some thin feature.
    # Features:
    # block_size
    # discards
    # discards_non_power_2
    # external_origin
    # metadata_resize
    # external_origin_extend
    # thin_disabled_features = [ "discards", "block_size" ]
    activation {
    # Set to 1 to perform internal checks on the operations issued to
    # libdevmapper. Useful for debugging problems with activation.
    # Some of the checks may be expensive, so it's best to use this
    # only when there seems to be a problem.
    checks = 0
    # Set to 0 to disable udev synchronisation (if compiled into the binaries).
    # Processes will not wait for notification from udev.
    # They will continue irrespective of any possible udev processing
    # in the background. You should only use this if udev is not running
    # or has rules that ignore the devices LVM2 creates.
    # The command line argument --nodevsync takes precedence over this setting.
    # If set to 1 when udev is not running, and there are LVM2 processes
    # waiting for udev, run 'dmsetup udevcomplete_all' manually to wake them up.
    udev_sync = 1
    # Set to 0 to disable the udev rules installed by LVM2 (if built with
    # --enable-udev_rules). LVM2 will then manage the /dev nodes and symlinks
    # for active logical volumes directly itself.
    # N.B. Manual intervention may be required if this setting is changed
    # while any logical volumes are active.
    udev_rules = 1
    # Set to 1 for LVM2 to verify operations performed by udev. This turns on
    # additional checks (and if necessary, repairs) on entries in the device
    # directory after udev has completed processing its events.
    # Useful for diagnosing problems with LVM2/udev interactions.
    verify_udev_operations = 0
    # If set to 1 and if deactivation of an LV fails, perhaps because
    # a process run from a quick udev rule temporarily opened the device,
    # retry the operation for a few seconds before failing.
    retry_deactivation = 1
    # How to fill in missing stripes if activating an incomplete volume.
    # Using "error" will make inaccessible parts of the device return
    # I/O errors on access. You can instead use a device path, in which
    # case, that device will be used to in place of missing stripes.
    # But note that using anything other than "error" with mirrored
    # or snapshotted volumes is likely to result in data corruption.
    missing_stripe_filler = "error"
    # The linear target is an optimised version of the striped target
    # that only handles a single stripe. Set this to 0 to disable this
    # optimisation and always use the striped target.
    use_linear_target = 1
    # How much stack (in KB) to reserve for use while devices suspended
    # Prior to version 2.02.89 this used to be set to 256KB
    reserved_stack = 64
    # How much memory (in KB) to reserve for use while devices suspended
    reserved_memory = 8192
    # Nice value used while devices suspended
    process_priority = -18
    # If volume_list is defined, each LV is only activated if there is a
    # match against the list.
    # "vgname" and "vgname/lvname" are matched exactly.
    # "@tag" matches any tag set in the LV or VG.
    # "@*" matches if any tag defined on the host is also set in the LV or VG
    # If any host tags exist but volume_list is not defined, a default
    # single-entry list containing "@*" is assumed.
    # volume_list = [ "vg1", "vg2/lvol1", "@tag1", "@*" ]
    # If auto_activation_volume_list is defined, each LV that is to be
    # activated with the autoactivation option (--activate ay/-a ay) is
    # first checked against the list. There are two scenarios in which
    # the autoactivation option is used:
    # - automatic activation of volumes based on incoming PVs. If all the
    # PVs making up a VG are present in the system, the autoactivation
    # is triggered. This requires lvmetad (global/use_lvmetad=1) and udev
    # to be running. In this case, "pvscan --cache -aay" is called
    # automatically without any user intervention while processing
    # udev events. Please, make sure you define auto_activation_volume_list
    # properly so only the volumes you want and expect are autoactivated.
    # - direct activation on command line with the autoactivation option.
    # In this case, the user calls "vgchange --activate ay/-a ay" or
    # "lvchange --activate ay/-a ay" directly.
    # By default, the auto_activation_volume_list is not defined and all
    # volumes will be activated either automatically or by using --activate ay/-a ay.
    # N.B. The "activation/volume_list" is still honoured in all cases so even
    # if the VG/LV passes the auto_activation_volume_list, it still needs to
    # pass the volume_list for it to be activated in the end.
    # If auto_activation_volume_list is defined but empty, no volumes will be
    # activated automatically and --activate ay/-a ay will do nothing.
    # auto_activation_volume_list = []
    # If auto_activation_volume_list is defined and it's not empty, only matching
    # volumes will be activated either automatically or by using --activate ay/-a ay.
    # "vgname" and "vgname/lvname" are matched exactly.
    # "@tag" matches any tag set in the LV or VG.
    # "@*" matches if any tag defined on the host is also set in the LV or VG
    # auto_activation_volume_list = [ "vg1", "vg2/lvol1", "@tag1", "@*" ]
    # If read_only_volume_list is defined, each LV that is to be activated
    # is checked against the list, and if it matches, it as activated
    # in read-only mode. (This overrides '--permission rw' stored in the
    # metadata.)
    # "vgname" and "vgname/lvname" are matched exactly.
    # "@tag" matches any tag set in the LV or VG.
    # "@*" matches if any tag defined on the host is also set in the LV or VG
    # read_only_volume_list = [ "vg1", "vg2/lvol1", "@tag1", "@*" ]
    # Each LV can have an 'activation skip' flag stored persistently against it.
    # During activation, this flag is used to decide whether such an LV is skipped.
    # The 'activation skip' flag can be set during LV creation and by default it
    # is automatically set for thin snapshot LVs. The 'auto_set_activation_skip'
    # enables or disables this automatic setting of the flag while LVs are created.
    # auto_set_activation_skip = 1
    # For RAID or 'mirror' segment types, 'raid_region_size' is the
    # size (in KiB) of each:
    # - synchronization operation when initializing
    # - each copy operation when performing a 'pvmove' (using 'mirror' segtype)
    # This setting has replaced 'mirror_region_size' since version 2.02.99
    raid_region_size = 512
    # Setting to use when there is no readahead value stored in the metadata.
    # "none" - Disable readahead.
    # "auto" - Use default value chosen by kernel.
    readahead = "auto"
    # 'raid_fault_policy' defines how a device failure in a RAID logical
    # volume is handled. This includes logical volumes that have the following
    # segment types: raid1, raid4, raid5*, and raid6*.
    # In the event of a failure, the following policies will determine what
    # actions are performed during the automated response to failures (when
    # dmeventd is monitoring the RAID logical volume) and when 'lvconvert' is
    # called manually with the options '--repair' and '--use-policies'.
    # "warn" - Use the system log to warn the user that a device in the RAID
    # logical volume has failed. It is left to the user to run
    # 'lvconvert --repair' manually to remove or replace the failed
    # device. As long as the number of failed devices does not
    # exceed the redundancy of the logical volume (1 device for
    # raid4/5, 2 for raid6, etc) the logical volume will remain
    # usable.
    # "allocate" - Attempt to use any extra physical volumes in the volume
    # group as spares and replace faulty devices.
    raid_fault_policy = "warn"
    # 'mirror_image_fault_policy' and 'mirror_log_fault_policy' define
    # how a device failure affecting a mirror (of "mirror" segment type) is
    # handled. A mirror is composed of mirror images (copies) and a log.
    # A disk log ensures that a mirror does not need to be re-synced
    # (all copies made the same) every time a machine reboots or crashes.
    # In the event of a failure, the specified policy will be used to determine
    # what happens. This applies to automatic repairs (when the mirror is being
    # monitored by dmeventd) and to manual lvconvert --repair when
    # --use-policies is given.
    # "remove" - Simply remove the faulty device and run without it. If
    # the log device fails, the mirror would convert to using
    # an in-memory log. This means the mirror will not
    # remember its sync status across crashes/reboots and
    # the entire mirror will be re-synced. If a
    # mirror image fails, the mirror will convert to a
    # non-mirrored device if there is only one remaining good
    # copy.
    # "allocate" - Remove the faulty device and try to allocate space on
    # a new device to be a replacement for the failed device.
    # Using this policy for the log is fast and maintains the
    # ability to remember sync state through crashes/reboots.
    # Using this policy for a mirror device is slow, as it
    # requires the mirror to resynchronize the devices, but it
    # will preserve the mirror characteristic of the device.
    # This policy acts like "remove" if no suitable device and
    # space can be allocated for the replacement.
    # "allocate_anywhere" - Not yet implemented. Useful to place the log device
    # temporarily on same physical volume as one of the mirror
    # images. This policy is not recommended for mirror devices
    # since it would break the redundant nature of the mirror. This
    # policy acts like "remove" if no suitable device and space can
    # be allocated for the replacement.
    mirror_log_fault_policy = "allocate"
    mirror_image_fault_policy = "remove"
    # 'snapshot_autoextend_threshold' and 'snapshot_autoextend_percent' define
    # how to handle automatic snapshot extension. The former defines when the
    # snapshot should be extended: when its space usage exceeds this many
    # percent. The latter defines how much extra space should be allocated for
    # the snapshot, in percent of its current size.
    # For example, if you set snapshot_autoextend_threshold to 70 and
    # snapshot_autoextend_percent to 20, whenever a snapshot exceeds 70% usage,
    # it will be extended by another 20%. For a 1G snapshot, using up 700M will
    # trigger a resize to 1.2G. When the usage exceeds 840M, the snapshot will
    # be extended to 1.44G, and so on.
    # Setting snapshot_autoextend_threshold to 100 disables automatic
    # extensions. The minimum value is 50 (A setting below 50 will be treated
    # as 50).
    snapshot_autoextend_threshold = 100
    snapshot_autoextend_percent = 20
    # 'thin_pool_autoextend_threshold' and 'thin_pool_autoextend_percent' define
    # how to handle automatic pool extension. The former defines when the
    # pool should be extended: when its space usage exceeds this many
    # percent. The latter defines how much extra space should be allocated for
    # the pool, in percent of its current size.
    # For example, if you set thin_pool_autoextend_threshold to 70 and
    # thin_pool_autoextend_percent to 20, whenever a pool exceeds 70% usage,
    # it will be extended by another 20%. For a 1G pool, using up 700M will
    # trigger a resize to 1.2G. When the usage exceeds 840M, the pool will
    # be extended to 1.44G, and so on.
    # Setting thin_pool_autoextend_threshold to 100 disables automatic
    # extensions. The minimum value is 50 (A setting below 50 will be treated
    # as 50).
    thin_pool_autoextend_threshold = 100
    thin_pool_autoextend_percent = 20
    # While activating devices, I/O to devices being (re)configured is
    # suspended, and as a precaution against deadlocks, LVM2 needs to pin
    # any memory it is using so it is not paged out. Groups of pages that
    # are known not to be accessed during activation need not be pinned
    # into memory. Each string listed in this setting is compared against
    # each line in /proc/self/maps, and the pages corresponding to any
    # lines that match are not pinned. On some systems locale-archive was
    # found to make up over 80% of the memory used by the process.
    # mlock_filter = [ "locale/locale-archive", "gconv/gconv-modules.cache" ]
    # Set to 1 to revert to the default behaviour prior to version 2.02.62
    # which used mlockall() to pin the whole process's memory while activating
    # devices.
    use_mlockall = 0
    # Monitoring is enabled by default when activating logical volumes.
    # Set to 0 to disable monitoring or use the --ignoremonitoring option.
    monitoring = 1
    # When pvmove or lvconvert must wait for the kernel to finish
    # synchronising or merging data, they check and report progress
    # at intervals of this number of seconds. The default is 15 seconds.
    # If this is set to 0 and there is only one thing to wait for, there
    # are no progress reports, but the process is awoken immediately the
    # operation is complete.
    polling_interval = 15
    # Report settings.
    # report {
    # Align columns on report output.
    # aligned=1
    # When buffered reporting is used, the report's content is appended
    # incrementally to include each object being reported until the report
    # is flushed to output which normally happens at the end of command
    # execution. Otherwise, if buffering is not used, each object is
    # reported as soon as its processing is finished.
    # buffered=1
    # Show headings for columns on report.
    # headings=1
    # A separator to use on report after each field.
    # separator=" "
    # Use a field name prefix for each field reported.
    # prefixes=0
    # Quote field values when using field name prefixes.
    # quoted=1
    # Output each column as a row. If set, this also implies report/prefixes=1.
    # colums_as_rows=0
    # Comma separated list of columns to sort by when reporting 'lvm devtypes' command.
    # See 'lvm devtypes -o help' for the list of possible fields.
    # devtypes_sort="devtype_name"
    # Comma separated list of columns to report for 'lvm devtypes' command.
    # See 'lvm devtypes -o help' for the list of possible fields.
    # devtypes_cols="devtype_name,devtype_max_partitions,devtype_description"
    # Comma separated list of columns to report for 'lvm devtypes' command in verbose mode.
    # See 'lvm devtypes -o help' for the list of possible fields.
    # devtypes_cols_verbose="devtype_name,devtype_max_partitions,devtype_description"
    # Comma separated list of columns to sort by when reporting 'lvs' command.
    # See 'lvs -o help' for the list of possible fields.
    # lvs_sort="vg_name,lv_name"
    # Comma separated list of columns to report for 'lvs' command.
    # See 'lvs -o help' for the list of possible fields.
    # lvs_cols="lv_name,vg_name,lv_attr,lv_size,pool_lv,origin,data_percent,move_pv,mirror_log,copy_percent,convert_lv"
    # Comma separated list of columns to report for 'lvs' command in verbose mode.
    # See 'lvs -o help' for the list of possible fields.
    # lvs_cols_verbose="lv_name,vg_name,seg_count,lv_attr,lv_size,lv_major,lv_minor,lv_kernel_major,lv_kernel_minor,pool_lv,origin,data_percent,metadata_percent,move_pv,copy_percent,mirror_log,convert
    # Comma separated list of columns to sort by when reporting 'vgs' command.
    # See 'vgs -o help' for the list of possible fields.
    # vgs_sort="vg_name"
    # Comma separated list of columns to report for 'vgs' command.
    # See 'vgs -o help' for the list of possible fields.
    # vgs_cols="vg_name,pv_count,lv_count,snap_count,vg_attr,vg_size,vg_free"
    # Comma separated list of columns to report for 'vgs' command in verbose mode.
    # See 'vgs -o help' for the list of possible fields.
    # vgs_cols_verbose="vg_name,vg_attr,vg_extent_size,pv_count,lv_count,snap_count,vg_size,vg_free,vg_uuid,vg_profile"
    # Comma separated list of columns to sort by when reporting 'pvs' command.
    # See 'pvs -o help' for the list of possible fields.
    # pvs_sort="pv_name"
    # Comma separated list of columns to report for 'pvs' command.
    # See 'pvs -o help' for the list of possible fields.
    # pvs_cols="pv_name,vg_name,pv_fmt,pv_attr,pv_size,pv_free"
    # Comma separated list of columns to report for 'pvs' command in verbose mode.
    # See 'pvs -o help' for the list of possible fields.
    # pvs_cols_verbose="pv_name,vg_name,pv_fmt,pv_attr,pv_size,pv_free,dev_size,pv_uuid"
    # Comma separated list of columns to sort by when reporting 'lvs --segments' command.
    # See 'lvs --segments -o help' for the list of possible fields.
    # segs_sort="vg_name,lv_name,seg_start"
    # Comma separated list of columns to report for 'lvs --segments' command.
    # See 'lvs --segments -o help' for the list of possible fields.
    # segs_cols="lv_name,vg_name,lv_attr,stripes,segtype,seg_size"
    # Comma separated list of columns to report for 'lvs --segments' command in verbose mode.
    # See 'lvs --segments -o help' for the list of possible fields.
    # segs_cols_verbose="lv_name,vg_name,lv_attr,seg_start,seg_size,stripes,segtype,stripesize,chunksize"
    # Comma separated list of columns to sort by when reporting 'pvs --segments' command.
    # See 'pvs --segments -o help' for the list of possible fields.
    # pvsegs_sort="pv_name,pvseg_start"
    # Comma separated list of columns to sort by when reporting 'pvs --segments' command.
    # See 'pvs --segments -o help' for the list of possible fields.
    # pvsegs_cols="pv_name,vg_name,pv_fmt,pv_attr,pv_size,pv_free,pvseg_start,pvseg_size"
    # Comma separated list of columns to sort by when reporting 'pvs --segments' command in verbose mode.
    # See 'pvs --segments -o help' for the list of possible fields.
    # pvsegs_cols_verbose="pv_name,vg_name,pv_fmt,pv_attr,pv_size,pv_free,pvseg_start,pvseg_size,lv_name,seg_start_pe,segtype,seg_pe_ranges"
    # Advanced section #
    # Metadata settings
    # metadata {
    # Default number of copies of metadata to hold on each PV. 0, 1 or 2.
    # You might want to override it from the command line with 0
    # when running pvcreate on new PVs which are to be added to large VGs.
    # pvmetadatacopies = 1
    # Default number of copies of metadata to maintain for each VG.
    # If set to a non-zero value, LVM automatically chooses which of
    # the available metadata areas to use to achieve the requested
    # number of copies of the VG metadata. If you set a value larger
    # than the the total number of metadata areas available then
    # metadata is stored in them all.
    # The default value of 0 ("unmanaged") disables this automatic
    # management and allows you to control which metadata areas
    # are used at the individual PV level using 'pvchange
    # --metadataignore y/n'.
    # vgmetadatacopies = 0
    # Approximate default size of on-disk metadata areas in sectors.
    # You should increase this if you have large volume groups or
    # you want to retain a large on-disk history of your metadata changes.
    # pvmetadatasize = 255
    # List of directories holding live copies of text format metadata.
    # These directories must not be on logical volumes!
    # It's possible to use LVM2 with a couple of directories here,
    # preferably on different (non-LV) filesystems, and with no other
    # on-disk metadata (pvmetadatacopies = 0). Or this can be in
    # addition to on-disk metadata areas.
    # The feature was originally added to simplify testing and is not
    # supported under low memory situations - the machine could lock up.
    # Never edit any files in these directories by hand unless you
    # you are absolutely sure you know what you are doing! Use
    # the supplied toolset to make changes (e.g. vgcfgrestore).
    # dirs = [ "/etc/lvm/metadata", "/mnt/disk2/lvm/metadata2" ]
    # Event daemon
    dmeventd {
    # mirror_library is the library used when monitoring a mirror device.
    # "libdevmapper-event-lvm2mirror.so" attempts to recover from
    # failures. It removes failed devices from a volume group and
    # reconfigures a mirror as necessary. If no mirror library is
    # provided, mirrors are not monitored through dmeventd.
    mirror_library = "libdevmapper-event-lvm2mirror.so"
    # snapshot_library is the library used when monitoring a snapshot device.
    # "libdevmapper-event-lvm2snapshot.so" monitors the filling of
    # snapshots and emits a warning through syslog when the use of
    # the snapshot exceeds 80%. The warning is repeated when 85%, 90% and
    # 95% of the snapshot is filled.
    snapshot_library = "libdevmapper-event-lvm2snapshot.so"
    # thin_library is the library used when monitoring a thin device.
    # "libdevmapper-event-lvm2thin.so" monitors the filling of
    # pool and emits a warning through syslog when the use of
    # the pool exceeds 80%. The warning is repeated when 85%, 90% and
    # 95% of the pool is filled.
    thin_library = "libdevmapper-event-lvm2thin.so"
    # Full path of the dmeventd binary.
    # executable = "/usr/sbin/dmeventd"

  • When i receive emails they are deleted and i do not know why

    I have an IPad Air version 7.1.2 and model MD787LL/A and it has 56.6 gb. When i receive emails the automatically delete themselves and i cannot figure out how to stop this. Can anyone help me with this please.
    Richard

    If you're using an IMAP account, also check your other devices to be sure you don't have some filters or rules set up that either delete or move emails to subfolders. You can see all Emails on your iPad, but displaying the sidebar showing Mailboxes, tapping the email account you are having trouble with (NOT the Inbox, but the section below), then tapping All Mail or something similar depending on your provider.
    If the mails are there, they are somehow being moved by one of your mail clients or by a rule you set up with your provider.

  • Ihave 51 iphoto library and they keep increasing and i do not know why

    My iphoto has 51 libraries and they keep increasing and i do not know why, i would like only one iphoto library and consolidate all photos in that.

    If you're using an IMAP account, also check your other devices to be sure you don't have some filters or rules set up that either delete or move emails to subfolders. You can see all Emails on your iPad, but displaying the sidebar showing Mailboxes, tapping the email account you are having trouble with (NOT the Inbox, but the section below), then tapping All Mail or something similar depending on your provider.
    If the mails are there, they are somehow being moved by one of your mail clients or by a rule you set up with your provider.

  • Vendor master maintenance from one client to other

    Hi,
    Vendor master will be created in a production client and transferred to other client using ALE.
    The changes will be made only in first prodcution client.
    For any changes in vendor master of those vendorsin first production client, needs to get updated in the second client too.
    Eg.
    I have 10 vendors in first client and 6 is related to second client.
    I am modifying the all the vendors. When i execute BD21 it selects all the vendors and posts to the destination(second) client.
    But, we would like to send idocs related to Second client vendors only.
    Note: We are identifying the second client vendors using a match code in a different table.
    We would like the system to check, for these match code for identifying the vendors and send the idoc..
    Can you help on this please?
    Thanks in advance,
    Sasi

    Hi,
    1. If your vendor changes should be updated from one system to other system through ALE, we need to active the change pointers.
    2. Change points can be activate through Tcode SALE
    3. After activating change points and your distribution model is ready, you can execute the program RBDMIDOC to genarate the IDOCs.
    4. Normally this program will be executed in the background
    5. And as you said, you have to do some validations before sending IDOCs. For this you can Filters and rules in the DM.
    OR you can write the code in user-exists of outbound posting program.
    Rewards if this info is useful.
    Thanks,

  • IChat server will not start

    For reasons unknown, our server kernel panicked and had to be restarted. This machine is an OD replica. Since that time, we have not been able to restart iChat server. All other services appear to be working correctly. iChat was working without any problems before the restart. When I click the "Start iChat" button in Server Admin, the wheel spins for a minute or so, and then quits without starting the service.
    A "sudo changeip -checkhostname" returns this:
    Primary address = 192.168.2.100
    Current HostName = day-server.applesales.com
    DNS HostName = day-server.applesales.com
    The names match. There is nothing to change.
    dirserv:success = "success"
    DNS is set up properly.
    When I attempt to change any settings for the iChat service, the panel in Server Admin turns gray when I press "Save" and remains inactive until I click on another service and then click back to iChat. None of the server settings are changed.
    Here are the entries from the system log during the time when the iChat service is attempting to start:
    Mar 2 14:30:40 day-server servermgrd[83]: servermgr_jabber: STARTING UP iChat Server.
    Mar 2 14:30:40 day-server servermgrd[83]: servermgr_jabber[N]: waiting for jabberd to finish startup...
    Mar 2 14:30:40 day-server jabberd/sm[9307]: starting up
    Mar 2 14:30:40 day-server jabberd/router[9308]: starting up
    Mar 2 14:30:40 day-server jabberd/router[9308]: loaded user table (1 users)
    Mar 2 14:30:40 day-server jabberd/sm[9307]: id: day-server.local
    Mar 2 14:30:40 day-server jabberd/router[9308]: loaded filters (0 rules)
    Mar 2 14:30:40 day-server jabberd/sm[9307]: initialised storage driver 'sqlite'
    Mar 2 14:30:40 day-server jabberd/sm[9307]: modules search path: /var/jabberd/modules/jabberd2
    Mar 2 14:30:40 day-server jabberd/sm[9307]: module 'iq-last' added to chain 'sess-end' (order 0 index 0 seq 0)
    Mar 2 14:30:40 day-server jabberd/resolver[9306]: starting up
    Mar 2 14:30:40 day-server jabberd/sm[9307]: module 'validate' added to chain 'in-sess' (order 0 index 1 seq 0)
    Mar 2 14:30:40 day-server jabberd/sm[9307]: module 'privacy' added to chain 'in-sess' (order 1 index 2 seq 0)
    Mar 2 14:30:40 day-server jabberd/sm[9307]: module 'roster' added to chain 'in-sess' (order 2 index 3 seq 0)
    Mar 2 14:30:40 day-server jabberd/sm[9307]: module 'vacation' added to chain 'in-sess' (order 3 index 4 seq 0)
    Mar 2 14:30:40 day-server jabberd/sm[9307]: module 'iq-vcard' added to chain 'in-sess' (order 4 index 5 seq 0)
    Mar 2 14:30:40 day-server jabberd/sm[9307]: module 'iq-ping' added to chain 'in-sess' (order 5 index 6 seq 0)
    Mar 2 14:30:40 day-server jabberd/sm[9307]: module 'iq-private' added to chain 'in-sess' (order 6 index 7 seq 0)
    Mar 2 14:30:40 day-server jabberd/sm[9307]: module 'disco' added to chain 'in-sess' (order 7 index 8 seq 0)
    Mar 2 14:30:40 day-server jabberd/sm[9307]: module 'amp' added to chain 'in-sess' (order 8 index 9 seq 0)
    Mar 2 14:30:40 day-server jabberd/router[9308]: [127.0.0.1, port=5347] listening for incoming connections
    Mar 2 14:30:40 day-server jabberd/sm[9307]: module 'offline' added to chain 'in-sess' (order 9 index 10 seq 0)
    Mar 2 14:30:40 day-server jabberd/sm[9307]: module 'announce' added to chain 'in-sess' (order 10 index 11 seq 0)
    Mar 2 14:30:40 day-server jabberd/sm[9307]: module 'presence' added to chain 'in-sess' (order 11 index 12 seq 0)
    Mar 2 14:30:40 day-server jabberd/sm[9307]: module 'deliver' added to chain 'in-sess' (order 12 index 13 seq 0)
    Mar 2 14:30:40 day-server jabberd/sm[9307]: module 'session' added to chain 'in-router' (order 0 index 14 seq 0)
    Mar 2 14:30:40 day-server jabberd/resolver[9306]: attempting connection to router at 127.0.0.1, port=5347
    Mar 2 14:30:40 day-server jabberd/sm[9307]: module 'validate' added to chain 'in-router' (order 1 index 1 seq 1)
    Mar 2 14:30:40 day-server jabberd/sm[9307]: module 'presence' added to chain 'in-router' (order 2 index 12 seq 1)
    Mar 2 14:30:40 day-server jabberd/sm[9307]: module 'privacy' added to chain 'in-router' (order 3 index 2 seq 1)
    Mar 2 14:30:40 day-server jabberd/sm[9307]: module 'privacy' added to chain 'out-router' (order 0 index 2 seq 2)
    Mar 2 14:30:40 day-server jabberd/sm[9307]: module 'iq-last' added to chain 'pkt-sm' (order 0 index 0 seq 1)
    Mar 2 14:30:40 day-server jabberd/sm[9307]: module 'iq-ping' added to chain 'pkt-sm' (order 1 index 6 seq 1)
    Mar 2 14:30:40 day-server jabberd/sm[9307]: module 'iq-time' added to chain 'pkt-sm' (order 2 index 15 seq 0)
    Mar 2 14:30:40 day-server jabberd/sm[9307]: module 'iq-version' added to chain 'pkt-sm' (order 3 index 16 seq 0)
    Mar 2 14:30:40 day-server jabberd/router[9308]: [127.0.0.1, port=50953] connect
    Mar 2 14:30:40 day-server jabberd/sm[9307]: module 'amp' added to chain 'pkt-sm' (order 4 index 9 seq 1)
    Mar 2 14:30:40 day-server jabberd/sm[9307]: module 'disco' added to chain 'pkt-sm' (order 5 index 8 seq 1)
    Mar 2 14:30:40 day-server jabberd/sm[9307]: module 'announce' added to chain 'pkt-sm' (order 6 index 11 seq 1)
    Mar 2 14:30:40 day-server jabberd/sm[9307]: module 'help' added to chain 'pkt-sm' (order 7 index 17 seq 0)
    Mar 2 14:30:40 day-server jabberd/sm[9307]: module 'echo' added to chain 'pkt-sm' (order 8 index 18 seq 0)
    Mar 2 14:30:40 day-server jabberd/sm[9307]: module 'roster' added to chain 'pkt-user' (order 0 index 3 seq 1)
    Mar 2 14:30:40 day-server jabberd/sm[9307]: module 'presence' added to chain 'pkt-user' (order 1 index 12 seq 2)
    Mar 2 14:30:40 day-server jabberd/sm[9307]: module 'iq-vcard' added to chain 'pkt-user' (order 2 index 5 seq 1)
    Mar 2 14:30:40 day-server jabberd/sm[9307]: module 'amp' added to chain 'pkt-user' (order 3 index 9 seq 2)
    Mar 2 14:30:40 day-server jabberd/sm[9307]: module 'deliver' added to chain 'pkt-user' (order 4 index 13 seq 1)
    Mar 2 14:30:40 day-server jabberd/sm[9307]: module 'vacation' added to chain 'pkt-user' (order 5 index 4 seq 1)
    Mar 2 14:30:40 day-server jabberd/sm[9307]: module 'offline' added to chain 'pkt-user' (order 6 index 10 seq 1)
    Mar 2 14:30:40 day-server jabberd/sm[9307]: module 'disco-publish' added to chain 'pkt-user' (order 7 index 19 seq 0)
    Mar 2 14:30:40 day-server jabberd/sm[9307]: module 'iq-last' added to chain 'pkt-user' (order 8 index 0 seq 2)
    Mar 2 14:30:40 day-server jabberd/sm[9307]: module 'session' added to chain 'pkt-router' (order 0 index 14 seq 1)
    Mar 2 14:30:40 day-server jabberd/sm[9307]: module 'disco' added to chain 'pkt-router' (order 1 index 8 seq 2)
    Mar 2 14:30:40 day-server jabberd/sm[9307]: module 'active' added to chain 'user-load' (order 0 index 20 seq 0)
    Mar 2 14:30:40 day-server jabberd/sm[9307]: module 'roster' added to chain 'user-load' (order 1 index 3 seq 2)
    Mar 2 14:30:40 day-server jabberd/sm[9307]: module 'roster-publish' added to chain 'user-load' (order 2 index 21 seq 0)
    Mar 2 14:30:40 day-server jabberd/sm[9307]: module 'privacy' added to chain 'user-load' (order 3 index 2 seq 3)
    Mar 2 14:30:40 day-server jabberd/sm[9307]: module 'disco-publish' added to chain 'user-load' (order 4 index 19 seq 1)
    Mar 2 14:30:40 day-server jabberd/sm[9307]: module 'vacation' added to chain 'user-load' (order 5 index 4 seq 2)
    Mar 2 14:30:40 day-server jabberd/sm[9307]: module 'active' added to chain 'user-create' (order 0 index 20 seq 1)
    Mar 2 14:30:40 day-server jabberd/sm[9307]: module 'template-roster' added to chain 'user-create' (order 1 index 22 seq 0)
    Mar 2 14:30:40 day-server jabberd/sm[9307]: module 'active' added to chain 'user-delete' (order 0 index 20 seq 2)
    Mar 2 14:30:40 day-server jabberd/sm[9307]: module 'announce' added to chain 'user-delete' (order 1 index 11 seq 2)
    Mar 2 14:30:40 day-server jabberd/router[9308]: [127.0.0.1, port=50954] connect
    Mar 2 14:30:40 day-server jabberd/sm[9307]: module 'disco-publish' added to chain 'user-delete' (order 2 index 19 seq 2)
    Mar 2 14:30:40 day-server jabberd/sm[9307]: module 'offline' added to chain 'user-delete' (order 3 index 10 seq 2)
    Mar 2 14:30:40 day-server jabberd/sm[9307]: module 'privacy' added to chain 'user-delete' (order 4 index 2 seq 4)
    Mar 2 14:30:40 day-server jabberd/sm[9307]: module 'roster' added to chain 'user-delete' (order 5 index 3 seq 3)
    Mar 2 14:30:40 day-server jabberd/sm[9307]: module 'vacation' added to chain 'user-delete' (order 6 index 4 seq 3)
    Mar 2 14:30:40 day-server jabberd/router[9308]: [127.0.0.1, port=50954] authenticated as conference.day-server.applesales.com
    Mar 2 14:30:40 day-server jabberd/router[9308]: [conference.day-server.applesales.com] online (bound to 127.0.0.1, port 50954)
    Mar 2 14:30:40 day-server jabberd/sm[9307]: module 'iq-last' added to chain 'user-delete' (order 7 index 0 seq 3)
    Mar 2 14:30:40 day-server jabberd/sm[9307]: module 'iq-private' added to chain 'user-delete' (order 8 index 7 seq 1)
    Mar 2 14:30:40 day-server jabberd/sm[9307]: module 'iq-vcard' added to chain 'user-delete' (order 9 index 5 seq 2)
    Mar 2 14:30:40 day-server jabberd/sm[9307]: version: jabberd sm 2.1.24.1-326.1
    Mar 2 14:30:40 day-server jabberd/s2s[9311]: starting up (interval=60, queue=60, keepalive=0, idle=86400)
    Mar 2 14:30:40 day-server jabberd/c2s[9309]: starting up
    Mar 2 14:30:40 day-server jabberd/c2s[9309]: modules search path: /var/jabberd/modules/jabberd2
    Mar 2 14:30:40 day-server jabberd/c2s[9309]: initialized auth module 'sqlite'
    Mar 2 14:30:40 day-server jabberd/sm[9307]: attempting connection to router at 127.0.0.1, port=5347
    Mar 2 14:30:40 day-server jabberd/router[9308]: [127.0.0.1, port=50953] authenticated as jabberd
    Mar 2 14:30:40 day-server jabberd/router[9308]: [127.0.0.1, port=50955] connect
    Mar 2 14:30:40 day-server jabberd/router[9308]: [127.0.0.1, port=50955] authenticated as jabberd
    Mar 2 14:30:40 day-server jabberd/c2s[9309]: no local.id configured, aborting
    Mar 2 14:30:40 day-server jabberd/router[9308]: shutting down
    Mar 2 14:30:40 day-server jabberd/router[9308]: [127.0.0.1, port=50953] disconnect
    Mar 2 14:30:40 day-server jabberd/s2s[9311]: attempting connection to router at 127.0.0.1, port=5347
    Mar 2 14:30:40 day-server jabberd/s2s[9311]: shutting down
    Mar 2 14:30:40 day-server jabberd/s2s[9311]: connection to router closed
    Mar 2 14:30:40 day-server jabberd/resolver[9306]: connection to router established
    Mar 2 14:30:40 day-server jabberd/resolver[9306]: shutting down
    Mar 2 14:30:40 day-server jabberd/sm[9307]: connection to router established
    Mar 2 14:30:40 day-server jabberd/sm[9307]: shutting down
    Mar 2 14:30:41 day-server jabberd/router[9308]: [127.0.0.1, port=50954] disconnect
    Mar 2 14:30:41 day-server jabberd/router[9308]: [conference.day-server.applesales.com] offline
    Mar 2 14:30:42 day-server jabberd/router[9308]: [127.0.0.1, port=50955] disconnect
    Mar 2 14:30:45 day-server org.jabber.jabberd[9305]: ERROR: c2s died. Shutting down server.
    Mar 2 14:30:45 day-server com.apple.launchd[1] (org.jabber.jabberd): Throttling respawn: Will start in 5 seconds
    Mar 2 14:30:50 day-server jabberd/router[9315]: starting up
    Mar 2 14:30:50 day-server jabberd/router[9315]: loaded user table (1 users)
    Mar 2 14:30:50 day-server jabberd/router[9315]: loaded filters (0 rules)
    Mar 2 14:30:50 day-server jabberd/resolver[9313]: starting up
    Mar 2 14:30:50 day-server jabberd/sm[9314]: starting up
    Mar 2 14:30:50 day-server jabberd/router[9315]: [127.0.0.1, port=5347] listening for incoming connections
    Mar 2 14:30:50 day-server jabberd/sm[9314]: id: day-server.local
    Mar 2 14:30:50 day-server jabberd/s2s[9318]: starting up (interval=60, queue=60, keepalive=0, idle=86400)
    Mar 2 14:30:50 day-server jabberd/sm[9314]: initialised storage driver 'sqlite'
    Mar 2 14:30:50 day-server jabberd/sm[9314]: modules search path: /var/jabberd/modules/jabberd2
    Mar 2 14:30:50 day-server jabberd/sm[9314]: module 'iq-last' added to chain 'sess-end' (order 0 index 0 seq 0)
    Mar 2 14:30:50 day-server jabberd/sm[9314]: module 'validate' added to chain 'in-sess' (order 0 index 1 seq 0)
    Mar 2 14:30:50 day-server jabberd/sm[9314]: module 'privacy' added to chain 'in-sess' (order 1 index 2 seq 0)
    Mar 2 14:30:50 day-server jabberd/sm[9314]: module 'roster' added to chain 'in-sess' (order 2 index 3 seq 0)
    Mar 2 14:30:50 day-server jabberd/sm[9314]: module 'vacation' added to chain 'in-sess' (order 3 index 4 seq 0)
    Mar 2 14:30:50 day-server jabberd/sm[9314]: module 'iq-vcard' added to chain 'in-sess' (order 4 index 5 seq 0)
    Mar 2 14:30:50 day-server jabberd/sm[9314]: module 'iq-ping' added to chain 'in-sess' (order 5 index 6 seq 0)
    Mar 2 14:30:50 day-server jabberd/resolver[9313]: attempting connection to router at 127.0.0.1, port=5347
    Mar 2 14:30:50 day-server jabberd/sm[9314]: module 'iq-private' added to chain 'in-sess' (order 6 index 7 seq 0)
    Mar 2 14:30:50 day-server jabberd/sm[9314]: module 'disco' added to chain 'in-sess' (order 7 index 8 seq 0)
    Mar 2 14:30:50 day-server jabberd/sm[9314]: module 'amp' added to chain 'in-sess' (order 8 index 9 seq 0)
    Mar 2 14:30:50 day-server jabberd/sm[9314]: module 'offline' added to chain 'in-sess' (order 9 index 10 seq 0)
    Mar 2 14:30:50 day-server jabberd/router[9315]: [127.0.0.1, port=50958] connect
    Mar 2 14:30:50 day-server jabberd/sm[9314]: module 'announce' added to chain 'in-sess' (order 10 index 11 seq 0)
    Mar 2 14:30:50 day-server jabberd/sm[9314]: module 'presence' added to chain 'in-sess' (order 11 index 12 seq 0)
    Mar 2 14:30:50 day-server jabberd/sm[9314]: module 'deliver' added to chain 'in-sess' (order 12 index 13 seq 0)
    Mar 2 14:30:50 day-server jabberd/sm[9314]: module 'session' added to chain 'in-router' (order 0 index 14 seq 0)
    Mar 2 14:30:50 day-server jabberd/sm[9314]: module 'validate' added to chain 'in-router' (order 1 index 1 seq 1)
    Mar 2 14:30:50 day-server jabberd/sm[9314]: module 'presence' added to chain 'in-router' (order 2 index 12 seq 1)
    Mar 2 14:30:50 day-server jabberd/sm[9314]: module 'privacy' added to chain 'in-router' (order 3 index 2 seq 1)
    Mar 2 14:30:50 day-server jabberd/sm[9314]: module 'privacy' added to chain 'out-router' (order 0 index 2 seq 2)
    Mar 2 14:30:50 day-server jabberd/sm[9314]: module 'iq-last' added to chain 'pkt-sm' (order 0 index 0 seq 1)
    Mar 2 14:30:50 day-server jabberd/sm[9314]: module 'iq-ping' added to chain 'pkt-sm' (order 1 index 6 seq 1)
    Mar 2 14:30:50 day-server jabberd/sm[9314]: module 'iq-time' added to chain 'pkt-sm' (order 2 index 15 seq 0)
    Mar 2 14:30:50 day-server jabberd/sm[9314]: module 'iq-version' added to chain 'pkt-sm' (order 3 index 16 seq 0)
    Mar 2 14:30:50 day-server jabberd/sm[9314]: module 'amp' added to chain 'pkt-sm' (order 4 index 9 seq 1)
    Mar 2 14:30:50 day-server jabberd/sm[9314]: module 'disco' added to chain 'pkt-sm' (order 5 index 8 seq 1)
    Mar 2 14:30:50 day-server jabberd/sm[9314]: module 'announce' added to chain 'pkt-sm' (order 6 index 11 seq 1)
    Mar 2 14:30:50 day-server jabberd/sm[9314]: module 'help' added to chain 'pkt-sm' (order 7 index 17 seq 0)
    Mar 2 14:30:50 day-server jabberd/sm[9314]: module 'echo' added to chain 'pkt-sm' (order 8 index 18 seq 0)
    Mar 2 14:30:50 day-server jabberd/sm[9314]: module 'roster' added to chain 'pkt-user' (order 0 index 3 seq 1)
    Mar 2 14:30:50 day-server jabberd/sm[9314]: module 'presence' added to chain 'pkt-user' (order 1 index 12 seq 2)
    Mar 2 14:30:50 day-server jabberd/sm[9314]: module 'iq-vcard' added to chain 'pkt-user' (order 2 index 5 seq 1)
    Mar 2 14:30:50 day-server jabberd/s2s[9318]: attempting connection to router at 127.0.0.1, port=5347
    Mar 2 14:30:50 day-server jabberd/sm[9314]: module 'amp' added to chain 'pkt-user' (order 3 index 9 seq 2)
    Mar 2 14:30:50 day-server jabberd/sm[9314]: module 'deliver' added to chain 'pkt-user' (order 4 index 13 seq 1)
    Mar 2 14:30:50 day-server jabberd/sm[9314]: module 'vacation' added to chain 'pkt-user' (order 5 index 4 seq 1)
    Mar 2 14:30:50 day-server jabberd/sm[9314]: module 'offline' added to chain 'pkt-user' (order 6 index 10 seq 1)
    Mar 2 14:30:50 day-server jabberd/router[9315]: [127.0.0.1, port=50959] connect
    Mar 2 14:30:50 day-server jabberd/sm[9314]: module 'disco-publish' added to chain 'pkt-user' (order 7 index 19 seq 0)
    Mar 2 14:30:50 day-server jabberd/sm[9314]: module 'iq-last' added to chain 'pkt-user' (order 8 index 0 seq 2)
    Mar 2 14:30:50 day-server jabberd/sm[9314]: module 'session' added to chain 'pkt-router' (order 0 index 14 seq 1)
    Mar 2 14:30:50 day-server jabberd/sm[9314]: module 'disco' added to chain 'pkt-router' (order 1 index 8 seq 2)
    Mar 2 14:30:50 day-server jabberd/sm[9314]: module 'active' added to chain 'user-load' (order 0 index 20 seq 0)
    Mar 2 14:30:50 day-server jabberd/sm[9314]: module 'roster' added to chain 'user-load' (order 1 index 3 seq 2)
    Mar 2 14:30:50 day-server jabberd/sm[9314]: module 'roster-publish' added to chain 'user-load' (order 2 index 21 seq 0)
    Mar 2 14:30:50 day-server jabberd/sm[9314]: module 'privacy' added to chain 'user-load' (order 3 index 2 seq 3)
    Mar 2 14:30:50 day-server jabberd/sm[9314]: module 'disco-publish' added to chain 'user-load' (order 4 index 19 seq 1)
    Mar 2 14:30:50 day-server jabberd/sm[9314]: module 'vacation' added to chain 'user-load' (order 5 index 4 seq 2)
    Mar 2 14:30:50 day-server jabberd/sm[9314]: module 'active' added to chain 'user-create' (order 0 index 20 seq 1)
    Mar 2 14:30:50 day-server jabberd/sm[9314]: module 'template-roster' added to chain 'user-create' (order 1 index 22 seq 0)
    Mar 2 14:30:50 day-server jabberd/sm[9314]: module 'active' added to chain 'user-delete' (order 0 index 20 seq 2)
    Mar 2 14:30:50 day-server jabberd/sm[9314]: module 'announce' added to chain 'user-delete' (order 1 index 11 seq 2)
    Mar 2 14:30:50 day-server jabberd/sm[9314]: module 'disco-publish' added to chain 'user-delete' (order 2 index 19 seq 2)
    Mar 2 14:30:50 day-server jabberd/sm[9314]: module 'offline' added to chain 'user-delete' (order 3 index 10 seq 2)
    Mar 2 14:30:50 day-server jabberd/sm[9314]: module 'privacy' added to chain 'user-delete' (order 4 index 2 seq 4)
    Mar 2 14:30:50 day-server jabberd/sm[9314]: module 'roster' added to chain 'user-delete' (order 5 index 3 seq 3)
    Mar 2 14:30:50 day-server jabberd/sm[9314]: module 'vacation' added to chain 'user-delete' (order 6 index 4 seq 3)
    Mar 2 14:30:50 day-server jabberd/sm[9314]: module 'iq-last' added to chain 'user-delete' (order 7 index 0 seq 3)
    Mar 2 14:30:50 day-server jabberd/sm[9314]: module 'iq-private' added to chain 'user-delete' (order 8 index 7 seq 1)
    Mar 2 14:30:50 day-server jabberd/sm[9314]: module 'iq-vcard' added to chain 'user-delete' (order 9 index 5 seq 2)
    Mar 2 14:30:50 day-server jabberd/sm[9314]: version: jabberd sm 2.1.24.1-326.1
    Mar 2 14:30:50 day-server jabberd/c2s[9316]: starting up
    Mar 2 14:30:50 day-server jabberd/router[9315]: [127.0.0.1, port=50958] authenticated as jabberd
    Mar 2 14:30:50 day-server jabberd/c2s[9316]: modules search path: /var/jabberd/modules/jabberd2
    Mar 2 14:30:50 day-server jabberd/c2s[9316]: initialized auth module 'sqlite'
    Mar 2 14:30:50 day-server jabberd/router[9315]: [127.0.0.1, port=50959] authenticated as jabberd
    Mar 2 14:30:50 day-server jabberd/sm[9314]: attempting connection to router at 127.0.0.1, port=5347
    Mar 2 14:30:50 day-server jabberd/router[9315]: [127.0.0.1, port=50960] connect
    Mar 2 14:30:50 day-server jabberd/c2s[9316]: no local.id configured, aborting
    Mar 2 14:30:50 day-server jabberd/router[9315]: shutting down
    Mar 2 14:30:50 day-server jabberd/router[9315]: [127.0.0.1, port=50960] disconnect
    Mar 2 14:30:50 day-server jabberd/sm[9314]: shutting down
    Mar 2 14:30:50 day-server jabberd/resolver[9313]: connection to router established
    Mar 2 14:30:50 day-server jabberd/resolver[9313]: shutting down
    Mar 2 14:30:50 day-server jabberd/s2s[9318]: connection to router established
    Mar 2 14:30:50 day-server jabberd/s2s[9318]: shutting down
    Mar 2 14:30:50 day-server jabberd/s2s[9318]: connection to router closed
    Mar 2 14:30:51 day-server jabberd/router[9315]: [127.0.0.1, port=50958] disconnect
    Mar 2 14:30:52 day-server jabberd/router[9315]: [127.0.0.1, port=50959] disconnect
    Mar 2 14:30:55 day-server org.jabber.jabberd[9312]: ERROR: c2s died. Shutting down server.
    Mar 2 14:30:55 day-server com.apple.launchd[1] (org.jabber.jabberd): Throttling respawn: Will start in 5 seconds
    Mar 2 14:31:00 day-server jabberd/router[9325]: starting up
    Mar 2 14:31:00 day-server jabberd/router[9325]: loaded user table (1 users)
    Mar 2 14:31:00 day-server jabberd/router[9325]: loaded filters (0 rules)
    Mar 2 14:31:00 day-server jabberd/sm[9324]: starting up
    Mar 2 14:31:00 day-server jabberd/router[9325]: [127.0.0.1, port=5347] listening for incoming connections
    Mar 2 14:31:00 day-server jabberd/sm[9324]: id: day-server.local
    Mar 2 14:31:00 day-server jabberd/router[9325]: [127.0.0.1, port=50974] connect
    Mar 2 14:31:00 day-server jabberd/sm[9324]: initialised storage driver 'sqlite'
    Mar 2 14:31:00 day-server jabberd/sm[9324]: modules search path: /var/jabberd/modules/jabberd2
    Mar 2 14:31:00 day-server jabberd/sm[9324]: module 'iq-last' added to chain 'sess-end' (order 0 index 0 seq 0)
    Mar 2 14:31:00 day-server jabberd/router[9325]: [127.0.0.1, port=50974] authenticated as conference.day-server.applesales.com
    Mar 2 14:31:00 day-server jabberd/router[9325]: [conference.day-server.applesales.com] online (bound to 127.0.0.1, port 50974)
    Mar 2 14:31:00 day-server jabberd/sm[9324]: module 'validate' added to chain 'in-sess' (order 0 index 1 seq 0)
    Mar 2 14:31:00 day-server jabberd/sm[9324]: module 'privacy' added to chain 'in-sess' (order 1 index 2 seq 0)
    Mar 2 14:31:00 day-server jabberd/sm[9324]: module 'roster' added to chain 'in-sess' (order 2 index 3 seq 0)
    Mar 2 14:31:00 day-server jabberd/s2s[9328]: starting up (interval=60, queue=60, keepalive=0, idle=86400)
    Mar 2 14:31:00 day-server jabberd/sm[9324]: module 'vacation' added to chain 'in-sess' (order 3 index 4 seq 0)
    Mar 2 14:31:00 day-server jabberd/resolver[9323]: starting up
    Mar 2 14:31:00 day-server jabberd/sm[9324]: module 'iq-vcard' added to chain 'in-sess' (order 4 index 5 seq 0)
    Mar 2 14:31:00 day-server jabberd/sm[9324]: module 'iq-ping' added to chain 'in-sess' (order 5 index 6 seq 0)
    Mar 2 14:31:00 day-server jabberd/sm[9324]: module 'iq-private' added to chain 'in-sess' (order 6 index 7 seq 0)
    Mar 2 14:31:00 day-server jabberd/sm[9324]: module 'disco' added to chain 'in-sess' (order 7 index 8 seq 0)
    Mar 2 14:31:00 day-server jabberd/sm[9324]: module 'amp' added to chain 'in-sess' (order 8 index 9 seq 0)
    Mar 2 14:31:00 day-server jabberd/sm[9324]: module 'offline' added to chain 'in-sess' (order 9 index 10 seq 0)
    Mar 2 14:31:00 day-server jabberd/sm[9324]: module 'announce' added to chain 'in-sess' (order 10 index 11 seq 0)
    Mar 2 14:31:00 day-server jabberd/sm[9324]: module 'presence' added to chain 'in-sess' (order 11 index 12 seq 0)
    Mar 2 14:31:00 day-server jabberd/c2s[9326]: starting up
    Mar 2 14:31:00 day-server jabberd/sm[9324]: module 'deliver' added to chain 'in-sess' (order 12 index 13 seq 0)
    Mar 2 14:31:00 day-server jabberd/c2s[9326]: modules search path: /var/jabberd/modules/jabberd2
    Mar 2 14:31:00 day-server jabberd/sm[9324]: module 'session' added to chain 'in-router' (order 0 index 14 seq 0)
    Mar 2 14:31:00 day-server jabberd/sm[9324]: module 'validate' added to chain 'in-router' (order 1 index 1 seq 1)
    Mar 2 14:31:00 day-server jabberd/c2s[9326]: initialized auth module 'sqlite'
    Mar 2 14:31:00 day-server jabberd/sm[9324]: module 'presence' added to chain 'in-router' (order 2 index 12 seq 1)
    Mar 2 14:31:00 day-server jabberd/sm[9324]: module 'privacy' added to chain 'in-router' (order 3 index 2 seq 1)
    Mar 2 14:31:00 day-server jabberd/sm[9324]: module 'privacy' added to chain 'out-router' (order 0 index 2 seq 2)
    Mar 2 14:31:00 day-server jabberd/sm[9324]: module 'iq-last' added to chain 'pkt-sm' (order 0 index 0 seq 1)
    Mar 2 14:31:00 day-server jabberd/sm[9324]: module 'iq-ping' added to chain 'pkt-sm' (order 1 index 6 seq 1)
    Mar 2 14:31:00 day-server jabberd/sm[9324]: module 'iq-time' added to chain 'pkt-sm' (order 2 index 15 seq 0)
    Mar 2 14:31:00 day-server jabberd/sm[9324]: module 'iq-version' added to chain 'pkt-sm' (order 3 index 16 seq 0)
    Mar 2 14:31:00 day-server jabberd/sm[9324]: module 'amp' added to chain 'pkt-sm' (order 4 index 9 seq 1)
    Mar 2 14:31:00 day-server jabberd/sm[9324]: module 'disco' added to chain 'pkt-sm' (order 5 index 8 seq 1)
    Mar 2 14:31:00 day-server jabberd/sm[9324]: module 'announce' added to chain 'pkt-sm' (order 6 index 11 seq 1)
    Mar 2 14:31:00 day-server jabberd/sm[9324]: module 'help' added to chain 'pkt-sm' (order 7 index 17 seq 0)
    Mar 2 14:31:00 day-server jabberd/sm[9324]: module 'echo' added to chain 'pkt-sm' (order 8 index 18 seq 0)
    Mar 2 14:31:00 day-server jabberd/sm[9324]: module 'roster' added to chain 'pkt-user' (order 0 index 3 seq 1)
    Mar 2 14:31:00 day-server jabberd/sm[9324]: module 'presence' added to chain 'pkt-user' (order 1 index 12 seq 2)
    Mar 2 14:31:00 day-server jabberd/sm[9324]: module 'iq-vcard' added to chain 'pkt-user' (order 2 index 5 seq 1)
    Mar 2 14:31:00 day-server jabberd/sm[9324]: module 'amp' added to chain 'pkt-user' (order 3 index 9 seq 2)
    Mar 2 14:31:00 day-server jabberd/resolver[9323]: attempting connection to router at 127.0.0.1, port=5347
    Mar 2 14:31:00 day-server jabberd/sm[9324]: module 'deliver' added to chain 'pkt-user' (order 4 index 13 seq 1)
    Mar 2 14:31:00 day-server jabberd/sm[9324]: module 'vacation' added to chain 'pkt-user' (order 5 index 4 seq 1)
    Mar 2 14:31:00 day-server jabberd/sm[9324]: module 'offline' added to chain 'pkt-user' (order 6 index 10 seq 1)
    Mar 2 14:31:00 day-server jabberd/sm[9324]: module 'disco-publish' added to chain 'pkt-user' (order 7 index 19 seq 0)
    Mar 2 14:31:00 day-server jabberd/router[9325]: [127.0.0.1, port=50975] connect
    Mar 2 14:31:00 day-server jabberd/sm[9324]: module 'iq-last' added to chain 'pkt-user' (order 8 index 0 seq 2)
    Mar 2 14:31:00 day-server jabberd/sm[9324]: module 'session' added to chain 'pkt-router' (order 0 index 14 seq 1)
    Mar 2 14:31:00 day-server jabberd/sm[9324]: module 'disco' added to chain 'pkt-router' (order 1 index 8 seq 2)
    Mar 2 14:31:00 day-server jabberd/sm[9324]: module 'active' added to chain 'user-load' (order 0 index 20 seq 0)
    Mar 2 14:31:00 day-server jabberd/sm[9324]: module 'roster' added to chain 'user-load' (order 1 index 3 seq 2)
    Mar 2 14:31:00 day-server jabberd/sm[9324]: module 'roster-publish' added to chain 'user-load' (order 2 index 21 seq 0)
    Mar 2 14:31:00 day-server jabberd/s2s[9328]: attempting connection to router at 127.0.0.1, port=5347
    Mar 2 14:31:00 day-server jabberd/sm[9324]: module 'privacy' added to chain 'user-load' (order 3 index 2 seq 3)
    Mar 2 14:31:00 day-server jabberd/sm[9324]: module 'disco-publish' added to chain 'user-load' (order 4 index 19 seq 1)
    Mar 2 14:31:00 day-server jabberd/sm[9324]: module 'vacation' added to chain 'user-load' (order 5 index 4 seq 2)
    Mar 2 14:31:00 day-server jabberd/sm[9324]: module 'active' added to chain 'user-create' (order 0 index 20 seq 1)
    Mar 2 14:31:00 day-server jabberd/sm[9324]: module 'template-roster' added to chain 'user-create' (order 1 index 22 seq 0)
    Mar 2 14:31:00 day-server jabberd/sm[9324]: module 'active' added to chain 'user-delete' (order 0 index 20 seq 2)
    Mar 2 14:31:00 day-server jabberd/sm[9324]: module 'announce' added to chain 'user-delete' (order 1 index 11 seq 2)
    Mar 2 14:31:00 day-server jabberd/sm[9324]: module 'disco-publish' added to chain 'user-delete' (order 2 index 19 seq 2)
    Mar 2 14:31:00 day-server jabberd/sm[9324]: module 'offline' added to chain 'user-delete' (order 3 index 10 seq 2)
    Mar 2 14:31:00 day-server jabberd/sm[9324]: module 'privacy' added to chain 'user-delete' (order 4 index 2 seq 4)
    Mar 2 14:31:00 day-server jabberd/sm[9324]: module 'roster' added to chain 'user-delete' (order 5 index 3 seq 3)
    Mar 2 14:31:00 day-server jabberd/c2s[9326]: no local.id configured, aborting
    Mar 2 14:31:00 day-server jabberd/sm[9324]: module 'vacation' added to chain 'user-delete' (order 6 index 4 seq 3)
    Mar 2 14:31:00 day-server jabberd/sm[9324]: module 'iq-last' added to chain 'user-delete' (order 7 index 0 seq 3)
    Mar 2 14:31:00 day-server jabberd/sm[9324]: module 'iq-private' added to chain 'user-delete' (order 8 index 7 seq 1)
    Mar 2 14:31:00 day-server jabberd/sm[9324]: module 'iq-vcard' added to chain 'user-delete' (order 9 index 5 seq 2)
    Mar 2 14:31:00 day-server jabberd/sm[9324]: version: jabberd sm 2.1.24.1-326.1
    Mar 2 14:31:00 day-server jabberd/router[9325]: [127.0.0.1, port=50976] connect
    Mar 2 14:31:00 day-server jabberd/router[9325]: shutting down
    Mar 2 14:31:00 day-server jabberd/router[9325]: [127.0.0.1, port=50974] disconnect
    Mar 2 14:31:00 day-server jabberd/router[9325]: [conference.day-server.applesales.com] offline
    Mar 2 14:31:00 day-server jabberd/resolver[9323]: shutting down
    Mar 2 14:31:00 day-server jabberd/s2s[9328]: shutting down
    Mar 2 14:31:00 day-server jabberd/s2s[9328]: connection to router closed
    Mar 2 14:31:00 day-server jabberd/sm[9324]: attempting connection to router at 127.0.0.1, port=5347
    Mar 2 14:31:00 day-server jabberd/sm[9324]: shutting down
    Mar 2 14:31:01 day-server jabberd/router[9325]: [127.0.0.1, port=50975] disconnect
    Mar 2 14:31:02 day-server jabberd/router[9325]: [127.0.0.1, port=50976] disconnect
    Mar 2 14:31:05 day-server org.jabber.jabberd[9322]: ERROR: c2s died. Shutting down server.
    Mar 2 14:31:05 day-server com.apple.launchd[1] (org.jabber.jabberd): Throttling respawn: Will start in 5 seconds
    Mar 2 14:31:10 day-server jabberd/resolver[9331]: starting up
    Mar 2 14:31:10 day-server jabberd/router[9333]: starting up
    Mar 2 14:31:10 day-server jabberd/router[9333]: loaded user table (1 users)
    Mar 2 14:31:10 day-server jabberd/router[9333]: loaded filters (0 rules)
    Mar 2 14:31:10 day-server jabberd/resolver[9331]: attempting connection to router at 127.0.0.1, port=5347
    Mar 2 14:31:10 day-server jabberd/resolver[9331]: [4] [router] write error: Broken pipe (32)
    Mar 2 14:31:10 day-server jabberd/resolver[9331]: connection to router closed
    Mar 2 14:31:10 day-server jabberd/resolver[9331]: attempting reconnect (3 left)
    Mar 2 14:31:10 day-server jabberd/s2s[9336]: starting up (interval=60, queue=60, keepalive=0, idle=86400)
    Mar 2 14:31:10 day-server jabberd/sm[9332]: starting up
    Mar 2 14:31:10 day-server jabberd/router[9333]: [127.0.0.1, port=5347] listening for incoming connections
    Mar 2 14:31:10 day-server jabberd/sm[9332]: id: day-server.local
    Mar 2 14:31:10 day-server jabberd/c2s[9334]: starting up
    Mar 2 14:31:10 day-server jabberd/c2s[9334]: modules search path: /var/jabberd/modules/jabberd2
    Mar 2 14:31:10 day-server jabberd/sm[9332]: initialised storage driver 'sqlite'
    Mar 2 14:31:10 day-server jabberd/sm[9332]: modules search path: /var/jabberd/modules/jabberd2
    Mar 2 14:31:10 day-server jabberd/c2s[9334]: initialized auth module 'sqlite'
    Mar 2 14:31:10 day-server jabberd/sm[9332]: module 'iq-last' added to chain 'sess-end' (order 0 index 0 seq 0)
    Mar 2 14:31:10 day-server jabberd/sm[9332]: module 'validate' added to chain 'in-sess' (order 0 index 1 seq 0)
    Mar 2 14:31:10 day-server jabberd/sm[9332]: module 'privacy' added to chain 'in-sess' (order 1 index 2 seq 0)
    Mar 2 14:31:10 day-server jabberd/sm[9332]: module 'roster' added to chain 'in-sess' (order 2 index 3 seq 0)
    Mar 2 14:31:10 day-server jabberd/sm[9332]: module 'vacation' added to chain 'in-sess' (order 3 index 4 seq 0)
    Mar 2 14:31:10 day-server jabberd/sm[9332]: module 'iq-vcard' added to chain 'in-sess' (order 4 index 5 seq 0)
    Mar 2 14:31:10 day-server jabberd/sm[9332]: module 'iq-ping' added to chain 'in-sess' (order 5 index 6 seq 0)
    Mar 2 14:31:10 day-server jabberd/sm[9332]: module 'iq-private' added to chain 'in-sess' (order 6 index 7 seq 0)
    Mar 2 14:31:10 day-server jabberd/sm[9332]: module 'disco' added to chain 'in-sess' (order 7 index 8 seq 0)
    Mar 2 14:31:10 day-server jabberd/sm[9332]: module 'amp' added to chain 'in-sess' (order 8 index 9 seq 0)
    Mar 2 14:31:10 day-server jabberd/sm[9332]: module 'offline' added to chain 'in-sess' (order 9 index 10 seq 0)
    Mar 2 14:31:10 day-server jabberd/sm[9332]: module 'announce' added to chain 'in-sess' (order 10 index 11 seq 0)
    Mar 2 14:31:10 day-server jabberd/sm[9332]: module 'presence' added to chain 'in-sess' (order 11 index 12 seq 0)
    Mar 2 14:31:10 day-server jabberd/sm[9332]: module 'deliver' added to chain 'in-sess' (order 12 index 13 seq 0)
    Mar 2 14:31:10 day-server jabberd/sm[9332]: module 'session' added to chain 'in-router' (order 0 index 14 seq 0)
    Mar 2 14:31:10 day-server jabberd/sm[9332]: module 'validate' added to chain 'in-router' (order 1 index 1 seq 1)
    Mar 2 14:31:10 day-server jabberd/sm[9332]: module 'presence' added to chain 'in-router' (order 2 index 12 seq 1)
    Mar 2 14:31:10 day-server jabberd/sm[9332]: module 'privacy' added to chain 'in-router' (order 3 index 2 seq 1)
    Mar 2 14:31:10 day-server jabberd/sm[9332]: module 'privacy' added to chain 'out-router' (order 0 index 2 seq 2)
    Mar 2 14:31:10 day-server jabberd/sm[9332]: module 'iq-last' added to chain 'pkt-sm' (order 0 index 0 seq 1)
    Mar 2 14:31:10 day-server jabberd/sm[9332]: module 'iq-ping' added to chain 'pkt-sm' (order 1 index 6 seq 1)
    Mar 2 14:31:10 day-server jabberd/sm[9332]: module 'iq-time' added to chain 'pkt-sm' (order 2 index 15 seq 0)
    Mar 2 14:31:10 day-server jabberd/sm[9332]: module 'iq-version' added to chain 'pkt-sm' (order 3 index 16 seq 0)
    Mar 2 14:31:10 day-server jabberd/sm[9332]: module 'amp' added to chain 'pkt-sm' (order 4 index 9 seq 1)
    Mar 2 14:31:10 day-server jabberd/sm[9332]: module 'disco' added to chain 'pkt-sm' (order 5 index 8 seq 1)
    Mar 2 14:31:10 day-server jabberd/sm[9332]: module 'announce' added to chain 'pkt-sm' (order 6 index 11 seq 1)
    Mar 2 14:31:10 day-server jabberd/sm[9332]: module 'help' added to chain 'pkt-sm' (order 7 index 17 seq 0)
    Mar 2 14:31:10 day-server jabberd/sm[9332]: module 'echo' added to chain 'pkt-sm' (order 8 index 18 seq 0)
    Mar 2 14:31:10 day-server jabberd/sm[9332]: module 'roster' added to chain 'pkt-user' (order 0 index 3 seq 1)
    Mar 2 14:31:10 day-server jabberd/sm[9332]: module 'presence' added to chain 'pkt-user' (order 1 index 12 seq 2)
    Mar 2 14:31:10 day-server jabberd/sm[9332]: module 'iq-vcard' added to chain 'pkt-user' (order 2 index 5 seq 1)
    Mar 2 14:31:10 day-server jabberd/sm[9332]: module 'amp' added to chain 'pkt-user' (order 3 index 9 seq 2)
    Mar 2 14:31:10 day-server jabberd/sm[9332]: module 'deliver' added to chain 'pkt-user' (order 4 index 13 seq 1)
    Mar 2 14:31:10 day-server jabberd/sm[9332]: module 'vacation' added to chain 'pkt-user' (order 5 index 4 seq 1)
    Mar 2 14:31:10 day-server jabberd/sm[9332]: module 'offline' added to chain 'pkt-user' (order 6 index 10 seq 1)
    Mar 2 14:31:10 day-server jabberd/sm[9332]: module 'disco-publish' added to chain 'pkt-user' (order 7 index 19 seq 0)
    Mar 2 14:31:10 day-server jabberd/sm[9332]: module 'iq-last' added to chain 'pkt-user' (order 8 index 0 seq 2)
    Mar 2 14:31:10 day-server jabberd/sm[9332]: module 'session' added to chain 'pkt-router' (order 0 index 14 seq 1)
    Mar 2 14:31:10 day-server jabberd/sm[9332]: module 'disco' added to chain 'pkt-router' (order 1 index 8 seq 2)
    Mar 2 14:31:10 day-server jabberd/s2s[9336]: attempting connection to router at 127.0.0.1, port=5347
    Mar 2 14:31:10 day-server jabberd/sm[9332]: module 'active' added to chain 'user-load' (order 0 index 20 seq 0)
    Mar 2 14:31:10 day-server jabberd/router[9333]: [127.0.0.1, port=51007] connect
    Mar 2 14:31:10 day-server jabberd/c2s[9334]: no local.id configured, aborting
    Mar 2 14:31:10 day-server jabberd/sm[9332]: module 'roster' added to chain 'user-load' (order 1 index 3 seq 2)
    Mar 2 14:31:10 day-server jabberd/sm[9332]: module 'roster-publish' added to chain 'user-load' (order 2 index 21 seq 0)
    Mar 2 14:31:10 day-server jabberd/sm[9332]: module 'privacy' added to chain 'user-load' (order 3 index 2 seq 3)
    Mar 2 14:31:10 day-server jabberd/sm[9332]: module 'disco-publish' added to chain 'user-load' (order 4 index 19 seq 1)
    Mar 2 14:31:10 day-server jabberd/sm[9332]: module 'vacation' added to chain 'user-load' (order 5 index 4 seq 2)
    Mar 2 14:31:10 day-server jabberd/sm[9332]: module 'active' added to chain 'user-create' (order 0 index 20 seq 1)
    Mar 2 14:31:10 day-server jabberd/sm[9332]: module 'template-roster' added to chain 'user-create' (order 1 index 22 seq 0)
    Mar 2 14:31:10 day-server jabberd/sm[9332]: module 'active' added to chain 'user-delete' (order 0 index 20 seq 2)
    Mar 2 14:31:10 day-server jabberd/sm[9332]: module 'announce' added to chain 'user-delete' (order 1 index 11 seq 2)
    Mar 2 14:31:10 day-server jabberd/sm[9332]: module 'disco-publish' added to chain 'user-delete' (order 2 index 19 seq 2)
    Mar 2 14:31:10 day-server jabberd/sm[9332]: module 'offline' added to chain 'user-delete' (order 3 index 10 seq 2)
    Mar 2 14:31:10 day-server jabberd/sm[9332]: module 'privacy' added to chain 'user-delete' (order 4 index 2 seq 4)
    Mar 2 14:31:10 day-server jabberd/sm[9332]: module 'roster' added to chain 'user-delete' (order 5 index 3 seq 3)
    Mar 2 14:31:10 day-server jabberd/resolver[9331]: attempting connection to router at 127.0.0.1, port=5347
    Mar 2 14:31:10 day-server jabberd/sm[9332]: module 'vacation' added to chain 'user-delete' (order 6 index 4 seq 3)
    Mar 2 14:31:10 day-server jabberd/sm[9332]: module 'iq-last' added to chain 'user-delete' (order 7 index 0 seq 3)
    Mar 2 14:31:10 day-server jabberd/resolver[9331]: shutting down
    Mar 2 14:31:10 day-server jabberd/router[9333]: shutting down
    Mar 2 14:31:10 day-server jabberd/router[9333]: [127.0.0.1, port=51007] disconnect
    Mar 2 14:31:10 day-server jabberd/sm[9332]: module 'iq-private' added to chain 'user-delete' (order 8 index 7 seq 1)
    Mar 2 14:31:10 day-server jabberd/sm[9332]: module 'iq-vcard' added to chain 'user-delete' (order 9 index 5 seq 2)
    Mar 2 14:31:10 day-server jabberd/sm[9332]: version: jabberd sm 2.1.24.1-326.1
    Mar 2 14:31:10 day-server jabberd/s2s[9336]: shutting down
    Mar 2 14:31:10 day-server jabberd/s2s[9336]: connection to router closed
    Mar 2 14:31:10 day-server jabberd/sm[9332]: attempting connection to router at 127.0.0.1, port=5347
    Mar 2 14:31:10 day-server jabberd/sm[9332]: shutting down
    Mar 2 14:31:15 day-server org.jabber.jabberd[9330]: ERROR: c2s died. Shutting down server.
    Mar 2 14:31:15 day-server com.apple.launchd[1] (org.jabber.jabberd): Throttling respawn: Will start in 5 seconds
    Mar 2 14:31:20 day-server jabberd/resolver[9338]: starting up
    Mar 2 14:31:20 day-server jabberd/sm[9339]: starting up
    Mar 2 14:31:20 day-server jabberd/sm[9339]: id: day-server.local
    Mar 2 14:31:20 day-server jabberd/sm[9339]: initialised storage driver 'sqlite'
    Mar 2 14:31:20 day-server jabberd/sm[9339]: modules search path: /var/jabberd/modules/jabberd2
    Mar 2 14:31:20 day-server jabberd/sm[9339]: module 'iq-last' added to chain 'sess-end' (order 0 index 0 seq 0)
    Mar 2 14:31:20 day-server jabberd/sm[9339]: module 'validate' added to chain 'in-sess' (order 0 index 1 seq 0)
    Mar 2 14:31:20 day-server jabberd/sm[9339]: module 'privacy' added to chain 'in-sess' (order 1 index 2 seq 0)
    Mar 2 14:31:20 day-server jabberd/sm[9339]: module 'roster' added to chain 'in-sess' (order 2 index 3 seq 0)
    Mar 2 14:31:20 day-server jabberd/sm[9339]: module 'vacation' added to chain 'in-sess' (order 3 index 4 seq 0)
    Mar 2 14:31:20 day-server jabberd/sm[9339]: module 'iq-vcard' added to chain 'in-sess' (order 4 index 5 seq 0)
    Mar 2 14:31:20 day-server jabberd/resolver[9338]: attempting connection to router at 127.0.0.1, port=5347
    Mar 2 14:31:20 day-server jabberd/sm[9339]: module 'iq-ping' added to chain 'in-sess' (order 5 index 6 seq 0)
    Mar 2 14:31:20 day-server jabberd/sm[9339]: module 'iq-private' added to chain 'in-sess' (order 6 index 7 seq 0)
    Mar 2 14:31:20 day-server jabberd/resolver[9338]: [4] [router] write error: Broken pipe (32)
    Mar 2 14:31:20 day-server jabberd/resolver[9338]: connection to router closed
    Mar 2 14:31:20 day-server jabberd/sm[9339]: module 'disco' added to chain 'in-sess' (order 7 index 8 seq 0)
    Mar 2 14:31:20 day-server jabberd/resolver[9338]: attempting reconnect (3 left)
    Mar 2 14:31:20 day-server jabberd/sm[9339]: module 'amp' added to chain 'in-sess' (order 8 index 9 seq 0)
    Mar 2 14:31:20 day-server jabberd/sm[9339]: module 'offline' added to chain 'in-sess' (order 9 index 10 seq 0)
    Mar 2 14:31:20 day-server jabberd/sm[9339]: module 'announce' added to chain 'in-sess' (order 10 index 11 seq 0)
    Mar 2 14:31:20 day-server jabberd/sm[9339]: module 'presence' added to chain 'in-sess' (order 11 index 12 seq 0)
    Mar 2 14:31:20 day-server jabberd/c2s[9341]: starting up
    Mar 2 14:31:20 day-server jabberd/sm[9339]: module 'deliver' added to chain 'in-sess' (order 12 index 13 seq 0)
    Mar 2 14:31:20 day-server jabberd/sm[9339]: module 'session' added to chain 'in-router' (order 0 index 14 seq 0)
    Mar 2 14:31:20 day-server jabberd/sm[9339]: module 'validate' added to chain 'in-router' (order 1 index 1 seq 1)
    Mar 2 14:31:20 day-server jabberd/sm[9339]: module 'presence' added to chain 'in-router' (order 2 index 12 seq 1)
    Mar 2 14:31:20 day-server jabberd/sm[9339]: module 'privacy' added to chain 'in-router' (order 3 index 2 seq 1)
    Mar 2 14:31:20 day-server jabberd/sm[9339]: module 'privacy' added to chain 'out-router' (order 0 index 2 seq 2)
    Mar 2 14:31:20 day-server jabberd/sm[9339]: module 'iq-last' added to chain 'pkt-sm' (order 0 index 0 seq 1)
    Mar 2 14:31:20 day-server jabberd/sm[9339]: module 'iq-ping' added to chain 'pkt-sm' (order 1 index 6 seq 1)
    Mar 2 14:31:20 day-server jabberd/router[9340]: starting up
    Mar 2 14:31:20 day-server jabberd/c2s[9341]: modules search path: /var/jabberd/modules/jabberd2
    Mar 2 14:31:20 day-server jabberd/sm[9339]: module 'iq-time' added to chain 'pkt-sm' (order 2 index 15 seq 0)
    Mar 2 14:31:20 day-server jabberd/sm[9339]: module 'iq-version' added to chain 'pkt-sm' (order 3 index 16 seq 0)
    Mar 2 14:31:20 day-server jabberd/sm[9339]: module 'amp' added to chain 'pkt-sm' (order 4 index 9 seq 1)
    Mar 2 14:31:20 day-server jabberd/sm[9339]: module 'disco' added to chain 'pkt-sm' (order 5 index 8 seq 1)
    Mar 2 14:31:20 day-server jabberd/c2s[9341]: initialized auth module 'sqlite'
    Mar 2 14:31:20 day-server jabberd/sm[9339]: module 'announce' added to chain 'pkt-sm' (order 6 index 11 seq 1)
    Mar 2 14:31:20 day-server jabberd/sm[9339]: module 'help' added to chain 'pkt-sm' (order 7 index 17 seq 0)
    Mar 2 14:31:20 day-server jabberd/sm[9339]: module 'echo' added to chain 'pkt-sm' (order 8 index 18 seq 0)
    Mar 2 14:31:20 day-server jabberd/sm[9339]: module 'roster' added to chain 'pkt-user' (order 0 index 3 seq 1)
    Mar 2 14:31:20 day-server jabberd/sm[9339]: module 'presence' added to chain 'pkt-user' (order 1 index 12 seq 2)
    Mar 2 14:31:20 day-server jabberd/sm[9339]: module 'iq-vcard' added to chain 'pkt-user' (order 2 index 5 seq 1)
    Mar 2 14:31:20 day-server jabberd/sm[9339]: module 'amp' added to chain 'pkt-user' (order 3 index 9 seq 2)
    Mar 2 14:31:20 day-server jabberd/sm[9339]: module 'deliver' added to chain 'pkt-user' (order 4 index 13 seq 1)
    Mar 2 14:31:20 day-server jabberd/router[9340]: loaded user table (1 users)
    Mar 2 14:31:20 day-server jabberd/router[9340]: loaded filters (0 rules)
    Mar 2 14:31:20 day-server jabberd/s2s[9343]: starting up (interval=60, queue=60, keepalive=0, idle=86400)
    Mar 2 14:31:20 day-server jabberd/sm[9339]: module 'vacation' added to chain 'pkt-user' (order 5 index 4 seq 1)
    Mar 2 14:31:20 day-server jabberd/sm[9339]: module 'offline' added to chain 'pkt-user' (order 6 index 10 seq 1)
    Mar 2 14:31:20 day-server jabberd/sm[9339]: module 'disco-publish' added to chain 'pkt-user' (order 7 index 19 seq 0)
    Mar 2 14:31:20 day-server jabberd/sm[9339]: module 'iq-last' added to chain 'pkt-user' (order 8 index 0 seq 2)
    Mar 2 14:31:20 day-server jabberd/sm[9339]: module 'session' added to chain 'pkt-router' (order 0 index 14 seq 1)
    Mar 2 14:31:20 day-server jabberd/sm[9339]: module 'disco' added to chain 'pkt-router' (order 1 index 8 seq 2)
    Mar 2 14:31:20 day-server jabberd/sm[9339]: module 'active' added to chain 'user-load' (order 0 index 20 seq 0)
    Mar 2 14:31:20 day-server jabberd/sm[9339]: module 'roster' added to chain 'user-load' (order 1 index 3 seq 2)
    Mar 2 14:31:20 day-server jabberd/sm[9339]: module 'roster-publish' added to chain 'user-load' (order 2 index 21 seq 0)
    Mar 2 14:31:20 day-server jabberd/router[9340]: [127.0.0.1, port=5347] listening for incoming connections
    Mar 2 14:31:20 day-server jabberd/sm[9339]: module 'privacy' added to chain 'user-load' (order 3 index 2 seq 3)
    Mar 2 14:31:20 day-server jabberd/sm[9339]: module 'disco-publish' added to chain 'user-load' (order 4 index 19 seq 1)
    Mar 2 14:31:20 day-server jabberd/sm[9339]: module 'vacation' added to chain 'user-load' (order 5 index 4 seq 2)
    Mar 2 14:31:20 day-server jabberd/sm[9339]: module 'active' added to chain 'user-create' (order 0 index 20 seq 1)
    Mar 2 14:31:20 day-server jabberd/sm[9339]: module 'template-roster' added to chain 'user-create' (order 1 index 22 seq 0)
    Mar 2 14:31:20 day-server jabberd/sm[9339]: module 'active' added to chain 'user-delete' (order 0 index 20 seq 2)
    Mar 2 14:31:20 day-server jabberd/sm[9339]: module 'announce' added to chain 'user-delete' (order 1 index 11 seq 2)
    Mar 2 14:31:20 day-server jabberd/sm[9339]: module 'disco-publish' added to chain 'user-delete' (order 2 index 19 seq 2)
    Mar 2 14:31:20 day-server jabberd/sm[9339]: module 'offline' added to chain 'user-delete' (order 3 index 10 seq 2)
    Mar 2 14:31:20 day-server jabberd/sm[9339]: module 'privacy' added to chain 'user-delete' (order 4 index 2 seq 4)
    Mar 2 14:31:20 day-server jabberd/sm[9339]: module 'roster' added to chain 'user-delete' (order 5 index 3 seq 3)
    Mar 2 14:31:20 day-server jabberd/sm[9339]: module 'vacation' added to chain 'user-delete' (order 6 index 4 seq 3)
    Mar 2 14:31:20 day-server jabberd/sm[9339]: module 'iq-last' added to chain 'user-delete' (order 7 index 0 seq 3)
    Mar 2 14:31:20 day-server jabberd/c2s[9341]: no local.id configured, aborting
    Mar 2 14:31:20 day-server jabberd/sm[9339]: module 'iq-private' added to chain 'user-delete' (order 8 index 7 seq 1)
    Mar 2 14:31:20 day-server jabberd/sm[9339]: module 'iq-vcard' added to chain 'user-delete' (order 9 index 5 seq 2)
    Mar 2 14:31:20 day-server jabberd/sm[9339]: version: jabberd sm 2.1.24.1-326.1
    Mar 2 14:31:20 day-server jabberd/s2s[9343]: attempting connection to router at 127.0.0.1, port=5347
    Mar 2 14:31:20 day-server jabberd/s2s[9343]: shutting down
    Mar 2 14:31:20 day-server jabberd/router[9340]: shutting down
    Mar 2 14:31:20 day-server jabberd/s2s[9343]: connection to router closed
    Mar 2 14:31:20 day-server jabberd/resolver[9338]: attempting connection to router at 127.0.0.1, port=5347
    Mar 2 14:31:20 day-server jabberd/resolver[9338]: shutting down
    Mar 2 14:31:20 day-server jabberd/sm[9339]: attempting connection to router at 127.0.0.1, port=5347
    Mar 2 14:31:20 day-server jabberd/sm[9339]: shutting down
    Mar 2 14:31:29 day-server org.jabber.jabberd[9337]: ERROR: c2s died. Shutting down server.
    Mar 2 14:31:29 day-server com.apple.launchd[1] (org.jabber.jabberd): Throttling respawn: Will start in 1 seconds
    Mar 2 14:31:30 day-server jabberd/router[9359]: starting up
    Mar 2 14:31:30 day-server jabberd/router[9359]: loaded user table (1 users)
    Mar 2 14:31:30 day-server jabberd/router[9359]: loaded filters (0 rules)
    Mar 2 14:31:30 day-server jabberd/sm[9358]: starting up
    Mar 2 14:31:30 day-server jabberd/c2s[9360]: starting up
    Mar 2 14:31:30 day-server jabberd/sm[9358]: id: day-server.local
    Mar 2 14:31:30 day-server jabberd/c2s[9360]: modules search path: /var/jabberd/modules/jabberd2
    Mar 2 14:31:30 day-server jabberd/c2s[9360]: initialized auth module 'sqlite'
    Mar 2 14:31:30 day-server jabberd/resolver[9357]: starting up
    Mar 2 14:31:30 day-server jabberd/sm[9358]: initialised storage driver 'sqlite'
    Mar 2 14:31:30 day-server jabberd/sm[9358]: modules search path: /var/jabberd/modules/jabberd2
    Mar 2 14:31:30 day-server jabberd/sm[9358]: module 'iq-last' added to chain 'sess-end' (order 0 index 0 seq 0)
    Mar 2 14:31:30 day-server jabberd/sm[9358]: module 'validate' added to chain 'in-sess' (order 0 index 1 seq 0)
    Mar 2 14:31:30 day-server jabberd/sm[9358]: module 'privacy' added to chain 'in-sess' (order 1 index 2 seq 0)
    Mar 2 14:31:30 day-server jabberd/s2s[9362]: starting up (interval=60, queue=60, keepalive=0, idle=86400)
    Mar 2 14:31:30 day-server jabberd/sm[9358]: module 'roster' added to chain 'in-sess' (order 2 index 3 seq 0)
    Mar 2 14:31:30 day-server jabberd/router[9359]: [127.0.0.1, port=5347] listening for incoming connections
    Mar 2 14:31:30 day-server jabberd/sm[9358]: module 'vacation' added to chain 'in-sess' (order 3 index 4 seq 0)
    Mar 2 14:31:30 day-server jabberd/sm[9358]: module 'iq-vcard' added to chain 'in-sess' (order 4 index 5 seq 0)
    Mar 2 14:31:30 day-server jabberd/sm[9358]: module 'iq-ping' added to chain 'in-sess' (order 5 index 6 seq 0)
    Mar 2 14:31:30 day-server jabberd/sm[9358]: module 'iq-private' added to chain 'in-sess' (order 6 index 7 seq 0)
    Mar 2 14:31:30 day-server jabberd/sm[9358]: module 'disco' added to chain 'in-sess' (order 7 index 8 seq 0)
    Mar 2 14:31:30 day-server jabberd/sm[9358]: module 'amp' added to chain 'in-sess' (order 8 index 9 seq 0)
    Mar 2 14:31:30 day-server jabberd/sm[9358]: module 'offline' added to chain 'in-sess' (order 9 index 10 seq 0)
    Mar 2 14:31:30 day-server jabberd/sm[9358]: module 'announce' added to chain 'in-sess' (order 10 index 11 seq 0)
    Mar 2 14:31:30 day-server jabberd/sm[9358]: module 'presence' added to chain 'in-sess' (order 11 index 12 seq 0)
    Mar 2 14:31:30 day-server jabberd/sm[9358]: module 'deliver' added to chain 'in-sess' (order 12 index 13 seq 0)
    Mar 2 14:31:30 day-server jabberd/sm[9358]: module 'session' added to chain 'in-router' (order 0 index 14 seq 0)
    Mar 2 14:31:30 day-server jabberd/sm[9358]: module 'validate' added to chain 'in-router' (order 1 index 1 seq 1)
    Mar 2 14:31:30 day-server jabberd/sm[9358]: module 'presence' added to chain 'in-router' (order 2 index 12 seq 1)
    Mar 2 14:31:30 day-server jabberd/sm[9358]: module 'privacy' added to chain 'in-router' (order 3 index 2 seq 1)
    Mar 2 14:31:30 day-server jabberd/sm[9358]: module 'privacy' added to chain 'out-router' (order 0 index 2 seq 2)
    Mar 2 14:31:30 day-server jabberd/sm[9358]: module 'iq-last' added to chain 'pkt-sm' (order 0 index 0 seq 1)
    Mar 2 14:31:30 day-server jabberd/sm[9358]: module 'iq-ping' added to chain 'pkt-sm' (order 1 index 6 seq 1)
    Mar 2 14:31:30 day-server jabberd/sm[9358]: module 'iq-time' added to chain 'pkt-sm' (order 2 index 15 seq 0)
    Mar 2 14:31:30 day-server jabberd/sm[9358]: module 'iq-version' added to chain 'pkt-sm' (order 3 index 16 seq 0)
    Mar 2 14:31:30 day-server jabberd/sm[9358]: module 'amp' added to chain 'pkt-sm' (order 4 index 9 seq 1)
    Mar 2 14:31:30 day-server jabberd/sm[9358]: module 'disco' added to chain 'pkt-sm' (order 5 index 8 seq 1)
    Mar 2 14:31:30 day-server jabberd/sm[9358]: module 'announce' added to chain 'pkt-sm' (order 6 index 11 seq 1)
    Mar 2 14:31:30 day-server jabberd/sm[9358]: module 'help' added to chain 'pkt-sm' (order 7 index 17 seq 0)
    Mar 2 14:31:30 day-server jabberd/sm[9358]: module 'echo' added to chain 'pkt-sm' (order 8 index 18 seq 0)
    Mar 2 14:31:30 day-server jabberd/sm[9358]: module 'roster' added to chain 'pkt-user' (order 0 index 3 seq 1)
    Mar 2 14:31:30 day-server jabberd/sm[9358]: module 'presence' added to chain 'pkt-user' (order 1 index 12 seq 2)
    Mar 2 14:31:30 day-server jabberd/sm[9358]: module 'iq-vcard' added to chain 'pkt-user' (order 2 index 5 seq 1)
    Mar 2 14:31:30 day-server jabberd/c2s[9360]: no local.id configured, aborting
    Mar 2 14:31:30 day-server jabberd/resolver[9357]: attempting connection to router at 127.0.0.1, port=5347
    Mar 2 14:31:30 day-server jabberd/router[9359]: [127.0.0.1, port=51029] connect
    Mar 2 14:31:30 day-server jabberd/sm[9358]: module 'amp' added to chain 'pkt-user' (order 3 index 9 seq 2)
    Mar 2 14:31:30 day-server jabberd/sm[9358]: module 'deliver' added to chain 'pkt-user' (order 4 index 13 seq 1)
    Mar 2 14:31:30 day-server jabberd/sm[9358]: module 'vacation' added to chain 'pkt-user' (order 5 index 4 seq 1)
    Mar 2 14:31:30 day-server jabberd/sm[9358]: module 'offline' added to chain 'pkt-user' (order 6 index 10 seq 1)
    Mar 2 14:31:30 day-server jabberd/sm[9358]: module 'disco-publish' added to chain 'pkt-user' (order 7 index 19 seq 0)
    Mar 2 14:31:30 day-server jabberd/sm[9358]: module 'iq-last' added to chain 'pkt-user' (order 8 index 0 seq 2)
    Mar 2 14:31:30 day-server jabberd/sm[9358]: module 'session' added to chain 'pkt-router' (order 0 index 14 seq 1)
    Mar 2 14:31:30 day-server jabberd/sm[9358]: module 'disco' added to chain 'pkt-router' (order 1 index 8 seq 2)
    Mar 2 14:31:30 day-server jabberd/s2s[9362]: attempting connection to router at 127.0.0.1, port=5347
    Mar 2 14:31:30 day-server jabberd/sm[9358]: module 'active' added to chain 'user-load' (order 0 index 20 seq 0)
    Mar 2 14:31:30 day-server jabberd/sm[9358]: module 'roster' added to chain 'user-load' (order 1 index 3 seq 2)
    Mar 2 14:31:30 day-server jabberd/sm[9358]: module 'roster-publish' added to chain 'user-load' (order 2 index 21 seq 0)
    Mar 2 14:31:30 day-server jabberd/sm[9358]: module 'privacy' added to chain 'user-load' (order 3 index 2 seq 3)
    Mar 2 14:31:30 day-server jabberd/sm[9358]: module 'disco-publish' added to chain 'user-load' (order 4 index 19 seq 1)
    Mar 2 14:31:30 day-server jabberd/sm[9358]: module 'vacation' added to chain 'user-load' (order 5 index 4 seq 2)
    Mar 2 14:31:30 day-server jabberd/sm[9358]: module 'active' added to chain 'user-create' (order 0 index 20 seq 1)
    Mar 2 14:31:30 day-server jabberd/s2s[9362]: shutting down
    Mar 2 14:31:30 day-server jabberd/sm[9358]: module 'template-roster' added to chain 'user-create' (order 1 index 22 seq 0)
    Mar 2 14:31:30 day-server jabberd/sm[9358]: module 'active' added to chain 'user-delete' (order 0 index 20 seq 2)
    Mar 2 14:31:30 day-server jabberd/s2s[9362]: connection to router closed
    Mar 2 14:31:30 day-server jabberd/sm[9358]: module 'announce' added to chain 'user-delete' (order 1 index 11 seq 2)
    Mar 2 14:31:30 day-server jabberd/sm[9358]: module 'disco-publish' added to chain 'user-delete' (order 2 index 19 seq 2)
    Mar 2 14:31:30 day-server jabberd/sm[9358]: module 'offline' added to chain 'user-delete' (order 3 index 10 seq 2)
    Mar 2 14:31:30 day-server jabberd/sm[9358]: module 'privacy' added to chain 'user-delete' (order 4 index 2 seq 4)
    Mar 2 14:31:30 day-server jabberd/sm[9358]: module 'roster' added to chain 'user-delete' (order 5 index 3 seq 3)
    Mar 2 14:31:30 day-server jabberd/sm[9358]: module 'vacation' added to chain 'user-delete' (order 6 index 4 seq 3)
    Mar 2 14:31:30 day-server jabberd/sm[9358]: module 'iq-last' added to chain 'user-delete' (order 7 index 0 seq 3)
    Mar 2 14:31:30 day-server jabberd/sm[9358]: module 'iq-private' added to chain 'user-delete' (order 8 index 7 seq 1)
    Mar 2 14:31:30 day-server jabberd/sm[9358]: module 'iq-vcard' added to chain 'user-delete' (order 9 index 5 seq 2)
    Mar 2 14:31:30 day-server jabberd/sm[9358]: version: jabberd sm 2.1.24.1-326.1
    Mar 2 14:31:30 day-server jabberd/router[9359]: [127.0.0.1, port=51030] connect
    Mar 2 14:31:30 day-server jabberd/resolver[9357]: shutting down
    Mar 2 14:31:30 day-server jabberd/router[9359]: shutting down
    Mar 2 14:31:30 day-server jabberd/router[9359]: [127.0.0.1, port=51029] disconnect
    Mar 2 14:31:30 day-server jabberd/sm[9358]: attempting connection to router at 127.0.0.1, port=5347
    Mar 2 14:31:30 day-server jabberd/sm[9358]: shutting down
    Mar 2 14:31:31 day-server jabberd/router[9359]: [127.0.0.1, port=51030] disconnect
    Mar 2 14:31:35 day-server org.jabber.jabberd[9356]: ERROR: c2s died. Shutting down server.
    Mar 2 14:31:35 day-server com.apple.launchd[1] (org.jabber.jabberd): Throttling respawn: Will start in 5 seconds
    Mar 2 14:31:40 day-server servermgrd[83]: servermgr_jabber[E]: Error -- jabberd service failed to start
    Mar 2 14:31:40 day-server servermgrd[83]: servermgr_jabber[W]: some jabberd processes failed to start
    Mar 2 14:31:40 day-server servermgrd[83]: servermgr_jabber[N]: waiting for jabberd to finish shutdown...
    Mar 2 14:31:40 day-server servermgrd[83]: servermgr_jabber[N]: jabberd service shutdown completed.
    Mar 2 14:31:40 day-server servermgrd[83]: servermgr_jabber[E]: Error -- failed to start service: jabberd
    Mar 2 14:31:41 day-server servermgrd[83]: servermgr_info: markrunning_servicesconfigured(): marked running services configured: com.apple.ServerAdmin.DNS, com.apple.ServerAdmin.SWUpdate, com.apple.ServerAdmin.NetBoot, com.apple.ServerAdmin.Web, com.apple.ServerAdmin.NFS, com.apple.ServerAdmin.AppleFile, com.apple.ServerAdmin.IPFirewall, com.apple.ServerAdmin.DirectoryServices
    I'm particularly concerned about "jabberd/c2s[9309]: no local.id configured, aborting" messages. Neither a Google search nor a search of the Apple KB or these forums provides any insight into what that means. I suspect is may be related to the "Host Domains" setting in Server Admin, which shows that I have a host domain assigned.
    Any help is greatly appreciated.

    I solved my own problem.
    I was correct in assuming that the "no local.id configured, aborting" message was related to not having a "Host Domain" correctly assigned in Server Admin. Apparently sometime, somehow, and some way that I can't explain, the iChat server didn't have the host domain correctly set even though the correct setting shows in Server Admin. When I attempted to remove the existing host domain, leaving none, and save the result, Server Admin reacted by disabling the whole iChat service config screen, which is stupid. How about giving me an error instead, which reads something like, "You must set a host domain"?
    So I added a second host domain, temp.domain.com, and deleted the original. Saved the settings. Re-added the original domain, deleted the temp. Re-saved the settings. Now the iChat service starts and works.

  • Smart Sync Related Queries

    A. Any guidelines in defining parent chlid relation ships and association when making BAPI Wrappers???
        Any documents/note/links.
    C. How can we separate BAPI Wrappers Interface and filtering rules. Can I bring my Filtering /distribution rules defined at backend
        to MI Middleware. If yes How??? Any documents.
    D. Which type is suitable for Master Data and which Type is suitable for Transactional Data.
        Is it OK to make every BAPI Wrapper of type T51(Server Driven).
        Are there any drawbacks in this approach.
    E. In the case of Server Driven, who has more load Server or the middleware??
    regards
    anubhav

    Hi Anubhav,
        T51 is the best type of syncBO not only for master data, but for transactional data also.  This is the one with highest performance and the least load both on both backend and MI.
    In T51 case, backend informs MI about the changes in the data (add/modify/delete). Backend is the best person to identify the change in data as the data resides there. The task to idendify the data changes is quite easy in backend (depends on the backend implementation), but if there are too many ways (too many applications) the data can be changed in the backend, the effort to catch all these cases will be higher in the backend.
    In T01 case, MI identifies the changes in the data. Since the data is primarily residing in the backend and changes in data happens there, the only way MI can identify the changes is by comparing every record from the backend with the replicated data in the middleware RDB. This process will be very time consuming and can lead to performance problems if the data is huge. Also the replication time will be higher.
    In the case of master data which seldom occurs changes, the T01 replicator will run periodically ( as scheduled ) comapring the whole data to find out there is no changes. In the case of T51, the replicator will be run automatically only when the backend informs there is a change in data.
    Even for transactional data, T51 is better in terms of performance. The delay for the updation of data in the middleware after the change in backend is very small and is even configurable in middleware. So the latest data will be always there in middleware.
    Regards
    Ajith Chandran

  • Not all messages are delivered to Mail

    It's so frustrating! My web-based version of my POP account receives messages that Mail doesn't. It has nothing to do with junk filters or rules; the mail just never arrives. There's no particular domain after the '@' that doesn't arrive, although I first noticed it when someone with a gmail account tried to email me. Furthermore, I sent an email with my own gmail account to my pop account in question and it never arrived in Mail! Is something corrupted in my Mail app?
    I'd really appreciate your feedback on this.
    adrian

    Try the following.
    Quit Mail first and using the Finder, go to Home > Library > Mail > this account named folder (named by the user name and incoming mail server for the account) > MessageUidsAlreadyDownloaded.
    Delete the MessageUidsAlreadyDownloaded file and empty the Trash.
    Launch Mail and if successful, any previously downloaded messages that remain on the server will be downloaded again in addition to all messages available not yet downloaded by Mail.
    If not successful and although I haven't experienced the same, it has been reported by others here that certain spam messages or legit messages than contain unusual formatted HTML sometimes "clog" the receipt of all messages available at the incoming mail server. Look for and delete all spam messages that are available at the incoming mail server for the account via webmail access.

Maybe you are looking for