1. Please take a little time for this simple survey! Thank you for participating!
    Dismiss Notice
  2. Dear Pleskians, please read this carefully! New attachments and other rules Thank you!
    Dismiss Notice
  3. Dear Pleskians, I really hope that you will share your opinion in this Special topic for chatter about Plesk in the Clouds. Thank you!
    Dismiss Notice

Piped Logs

Discussion in 'Plesk for Linux - 8.x and Older' started by Amin Taheri, Sep 29, 2007.

  1. Amin Taheri

    Amin Taheri Golden Pleskian Plesk Certified Professional

    Jul 5, 2007
    Likes Received:
    Seattle Area
    Hey guys,

    I hope some one can assit in educating me here - what is the piped logs feature, and how does that help?

    If I understand some of the basics correctly, it gives everyone one shared log file for apache access and error logs and allows for "less open files" on the OS and in apache in general.

    But beyond that, does it work better with the system resources, or does this add extra load? Does this change the way logs are parsed and rotated, or how clients get their distributed error and access logs for their domains?

    In 8.2 it says that you can support up to 900 domains with piped logs - what happens when you hit 901 - do you have to revert back to everyone has their own? What happens if you dont do that, does apache just stop?

    Thanks in advance for the education :)