[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [leafnode-list] leafnode 2.0b won't accept messages from mail2news.



On Thu, 5 Sep 2002 19:57:06 +0100, Robert wrote:
>  On Tue, 3 Sep 2002, robert@xxxxxxxxxxxxxxxxxxxxxxxxxxxx wrote:
>  
> > On Tue, 03 Sep 2002, Arne Hanssen verbalised:
> >> 
> >> fetchnews mode: get articles, get headers, get bodies, post articles
> >> found 19 articles in in.coming.
>  .
> >> I can't figure out what the problem is (it may be that Mandrake
> >> changes something (it runs a security script every hour)), but
> >> the funny thing is that "ordinary" news works ok and mail2news
> >> places messages in 'in.coming' - but leafnode claims that it can't
> >> read in.coming 
> > 
> > I see this as well but only (I think) when the daily msec security
> > script is running, for me it then settles down and the in.coming
> > messages get posted
>  
>  I was wrong, I see this when they get posted (or should get posted) when
>  fetchnews sees them and now that I have the latest snapshot (thanks!!) they
>  do get moved to failed.postings :-(
>  
>  found 9 articles in in.coming.
>  store: cannot open current directory
>  Could not store /var/spool/news/in.coming/3615-1031250303-1: 
>        "OS trouble, see previous log messages for details", 
>        moving to /var/spool/news/failed.postings/
>  
>  I think what's happening is that I run fetchnews using sudo -u news,
>  does sudo keep the current pwd? I guess so.
>  news can't open my home directory and it chokes
>  
>  Why does it need to open the current directory? 
>  Well I've looked at store.c and I can see why, it need to get back there
>  
>  I tried running it from /tmp and it worked so unless the OS problem had
>  gone away, that looks to be the cause.

I'm going in another direction, my root cronscript looked like this:

  cd /tmp
  su news -c "/usr/local/sbin/fetchnews -vvv"

Now I changed it to:

  cd /var/spool/news
  su news -c "/usr/local/sbin/fetchnews -vvv"

And fetchnews did place in.coming messages into my local.*-groups, at
least when I ran the script manually (from root).  I need to se what
happens when crond runs it the next couple of days...

-- 
Vennlig hilsen / Best regards
Arne Hanssen

-- 
leafnode-list@xxxxxxxxxxxxxxxxxxxxxxxxxxxx -- mailing list for leafnode
To unsubscribe, send mail with "unsubscribe" in the subject to the list