436 No space""/>

    Search the FAQ Archives

3 - A - B - C - D - E - F - G - H - I - J - K - L - M
N - O - P - Q - R - S - T - U - V - W - X - Y - Z
faqs.org - Internet FAQ Archives

INN FAQ Part 5/9: Other error messages and what they mean
Section - (5.3) log file fills with " 436 No space"

( Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Part8 - Part9 - Single Page )
[ Usenet FAQs | Web FAQs | Documents | RFC Index | Business Photos and Profiles ]


Top Document: INN FAQ Part 5/9: Other error messages and what they mean
Previous Document: (5.2) Bad file number writing history file -- throttling
Next Document: (5.4) Why does my innd often die with the message "Can't sync history, interrupted system call"
See reader questions & answers on this topic! - Help others by sharing your knowledge
innd issues this message if it cannot create a directory for a group,
_no matter what the reason for the failure_.  In most cases,
/usr/spool/news (and the mount point it is symlinked to, if any)
accidentally has permissions and ownerships that do not permit write
access by innd (which runs as "news").  After chowning them to news,
and setting the permissions to 755, everything should work fine.




User Contributions:


Comment about this article, ask questions, or add new information about this topic:
CAPTCHA