On Thu, Dec 22, 2005 at 09:14:43PM +0100, Santiago Vila wrote: > On Thu, 22 Dec 2005, xavier wrote: > > > the problem is that i'm trying to set VERBOSE and LOGFILE, > > so i can't use -m > > You can set VERBOSE and LOGFILE on the command line. > What problem do you have with that? > > Sample .procmailrc: > > :0: > everything > > When I do this: > > $ procmail .procmailrc VERBOSE=on LOGFILE=`tty` < /tmp/mensaje > > I see something like this: > > procmail: [19466] Thu Dec 22 21:10:07 2005 > procmail: Assigning "LOGFILE=/dev/tty6" > procmail: Opening "/dev/tty6" > procmail: Rcfile: "/home/user/.procmailrc" > procmail: Assigning "MAILDIR=/home/user" > [...] > > > Of course, if you set VERBOSE in .procmailrc itself, it will set a > value for such variable, and whatever value you gave on the command > line will be forgotten from that point,
yes, and LOGFILE too. very annoying to test. > but that's how it is supposed > to work. i don't agree. what's the point discarding env var we painfully added on the command line ? in what case would it be useful to wipe environnement ? what's the point of starting a debug session in `tty` if it's to be overriden 5 lines later by the config file ? (which is right to set the verbose to off and logfile to something fine : it's a production setup. cmd line is, in this case, used to debug..) usually, command line switches overrides config files... so does env. var. anyway, you can close the bug if you don't agree. bye thanks for your answers. -- xavier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
