Re: CVS Mail Newbie quaestion

[Mark D. Baushke]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Vijay Mishra <address@hidden> writes:

> b) After inserting the following lines in doLog script, I am not
> getting any error/warning messages on CVS client and commit is getting
> done successfully but the mail is never getting delivered
> 
> : # use perl
> eval 'exec /usr/bin/perl -S "$0" ${1+"$@"}'
>    if 0;

You may wish to add a bit more in the way of debugging output to verify
that the script is finding a .mailUsersOnCommit file and parsing it
properly.

You could uncomment the two open statements for /tmp/cvsOut and see
what, if anything gets put there in the way of error messages. Be sure to use

      touch /tmp/cvsOut
      chmod a+rw /tmp/cvsOut

if you do this even for a short term to avoid problems with anyone else
doing a commit.

You will probably also want to look at the $CVSROOT/CVSROOT/accumMail to
see if it is being used or verify that "mail" is in the default $PATH of
the user that is being run (ie, is /bin/ in PATH for your userid so that
a 'mail' executable is being found). If you have a /bin/mail on your
linux system, you could replace the '@mailCmd=("mail");' assignment with
'@mailCmd=("/bin/mail");' just to be sure it is being found.

Finally, you could always consider sending e-mail to the author of the
package asking for help... I won't really be able to provide any further
aid for you.

You may also wish to consider debugging the perl script by hand.

    cvs -t commit -m test-commit somefile

will show you how the doLog script is being run and you could always
look at the $CVSROOT/log/filelog file to see the kind of information
that was being written to its stdin and then use the perl debugger to
try to reproduce the state of the script for debugging purposes.

        Good luck,
        -- Mark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (FreeBSD)

iD8DBQFC5PaICg7APGsDnFERAlc+AKCPdkwZs4SMqACcUUhPVH81kiUcPACg8Mgf
30fSd3dt2KRHWL2m9eMoKQg=
=DayA
-----END PGP SIGNATURE-----