Yes I deleted it and when there is a post to the list, it is created again, with the posting in the file. [Note: (the "cat" file in the list dir has a permission 665, strange, ah? ... I have "umask 002" in my rc.init). I am not sure if this is a good idea but should I change the ../.bin/ files to add the path to the excutables? [like "cat=/bin/cat"; now it is "cat=cat"] Zhiliang On Mon, 20 Jun 2005, dmacdoug wrote:
Oops I meant, have you tried deleting that file named cat? Sorry about the typo.
On Mon, Jun 20, 2005 at 10:48:03AM -0700, dmacdoug wrote:
On Mon, Jun 20, 2005 at 09:55:52AM -0500, Zhiliang Hu wrote:
I got a bunch of errors like following in my Smarlist log file:
../.bin/subscribe: line 1: ./cat: Permission denied ../.bin/subscribe: line 112: ./cat: Permission denied ../.bin/subscribe: line 123: ./cat: Permission denied ../.bin/subscribe: line 140: ./cat: Permission denied ../.bin/subscribe: line 142: ./cat: Permission denied ../.bin/arch_retrieve: line 1: ./cat: Permission denied ../.bin/arch_retrieve: line 312: ./cat: Permission denied ../.bin/procbounce: line 142: ./cat: Permission denied
...
One odd thing is every successfully posted mail is saved into a file called "cat" in the list directory.
Have you tried simply that file named cat? It looks to me like it's trying to execute that file rather than the binary file /bin/cat which should be in your path. Why it's been created in the first place is another question.
Don M.
On Mon, Jun 20, 2005 at 01:45:07PM -0500, Zhiliang Hu wrote:
Yes I deleted it and when there is a post to the list, it is created again, with the posting in the file. [Note: (the "cat" file in the list dir has a permission 665, strange, ah? ... I have "umask 002" in my rc.init).
For whatever it's worth, my UMASK is 007. I wouldn't think anyone outside of user or group should need rights to the files created, certainly not execute rights.
I am not sure if this is a good idea but should I change the ../.bin/ files to add the path to the excutables? [like "cat=/bin/cat"; now it is "cat=cat"]
Zhiliang
The problem with putting the explicit path into the variable assignment like that is that, although it might possibly avoid the error, this variable is assigned in at least half a dozen different scripts, so it would probably need to be modified everywhere. And it shouldn't be necessary. Also, it doesn't attack the root of the problem. I suspect that, in some file which has been modified, there's an error in a procmail script which is creating this extra copy of the messages in this file. I'm no procmail whiz, and every time I want to make one I have to relearn it, it seems, so I'm no one to follow, but I would start by looking at every file that I'd modified and doing a diff between it and an unmodified version to make sure that none of my changes, purposeful or accidental, could be doing that. Don
participants (2)
-
dmacdoug -
Zhiliang Hu