info-cvs
[Top][All Lists]
Advanced

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

Re: CVS Mail Newbie quaestion


From: Mark D. Baushke
Subject: Re: CVS Mail Newbie quaestion
Date: Mon, 25 Jul 2005 01:14:04 -0700

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

Vijay Mishra <address@hidden> writes:

> Thanks for the detailed steps. I have done according to your
> instruction but getting this message in CVS client now while
> committing changes
> 
> sh: /usr/CVSRoot/CVSROOT/doLog: /usr/bin/perl
> : bad interpreter: No such file or directory

You need to provide additional information to help others diagnose your
problem. Useful answers to the following would be a start:

  a) What operating system and hardware platform are you using?
     (eg, If you run the command 'uname -a' you will find some of
      this kind of information).

  b) Does inserting the following three lines to the beginning of the
     doLog script help you?

: # use perl
eval 'exec /usr/bin/perl -S "$0" ${1+"$@"}'
   if 0;

Are you able to use

/usr/bin/perl -c /usr/CVSRoot/CVSROOT/doLog

and get 'syntax OK' out of it?

> I have perl (v5.8.0) installed on sever. And /usr/bin/perl path is also
> correct. 
> 
> What is wrong? Please help!! 

The error message indicates that some filename is not being accepted as
the interpreter. This could be one of a few things:

  a) the doLog itself does not like you to use '#!/usr/bin/perl' to
     specify the interpreter. You could try '#! /usr/bin/perl' which
     very old systems liked better than what you are using.

  b) you could try using shell syntax to run perl for you rather than
     trying to actually run perl as the interpreter directly.

  c) something that doLog is running is not recognized. This could mean
     that the `date '+%Y %M%m D%d %T %b'` is not doing the right thing

  d) It could mean that the 'co' command is not being found by your
     program.

Without further information, it is difficult to count the ways...

        -- Mark


> Best Regards
> Vijay Mishra
> 
> -----Original Message-----
> From: address@hidden [mailto:address@hidden On Behalf Of Mark D. Baushke
> Sent: Saturday, 23 July , 2005 7:41 PM
> To: Vijay Mishra
> Cc: address@hidden
> Subject: Re: CVS Mail Newbie quaestion 
> 
> Vijay Mishra <address@hidden> writes:
> 
> > Ok I downloaded both the files and placed the files in $CVSROOT/CVSROOT/
> > directory 
> > 
> > And done the follwing steps as status in doLog file
> > 
> > 1. Appended the log file with the following statement
> > 
> > "DEFAULT $CVSROOT/CVSROOT/doLog --user $USER %p %s" (>=cvs 1.12.x). 
> >     I putted (>=cvs 1.12.12) I believe x was the revison number of CVS.
> > Correct me If I am wring
> 
> Note that the text '(>=cvs 1.12.x)' is not a part of the line, nor are
> the quotes that surround the "DEFAULT...%s" text. That is
> 
>      --------------- cut here ---------------
> DEFAULT $CVSROOT/CVSROOT/doLog --user $USER %p %s
>      --------------- cut here ---------------
> 
> The line between the 'cut here' lines is the one
> you put into your $CVSROOT/CVSROOT/loginfo file.
> 
> > 2. Created one more directory in $CVSROOT/log
> > 
> > 3. touch $CVSROOT/log/commitlog (I have created the empty commitlog
> because
> > as such there was no file in this folder.)
> 
> Well, the instructions in the comments of the
> doLog script tell you to do it...
> 
> > 4. chown mishravijay $CVSROOT/log/commitlog (now by doing so I am the
> owner
> > of this file. Will it work for other users also? All CVS users have a
> > different login account)
> 
> The example suggested using 'cvsuser' which I
> suspect would have been the user that was setup to
> run in a :pserver: environment rather than your own userid.
> 
> The instructions also suggested changing the group
> to 'cvs' which expected to be the default group of
> the 'cvsuser' login that is running your :pserver:
> environment.
> 
> > 5. chmod 775 $CVSROOT/log/commitlog
> 
> This gives both user and group write permissions
> and no permissions to the rest of the world.
> 
> > 6. touch $CVSROOT/log/filelog (I have created the empty filelog because as
> > such there was no file in this folder.)
> > 
> > 7. chown mishravijay $CVSROOT/log/filelog 
> 
> Again, the instructions suggect 'cvsuser.cvs' to
> change the owner to 'cvsuser' and the group to
> 'cvs' and that should match how you have setup
> your :pserver: environment.
> 
> > 
> > 8. chmod 775 $CVSROOT/log/filelog
> > 
> > 
> > Now my question is where should I specify the
> > user which has to get mail notifications on
> > commit. And how to configure the accumMail file
> > also. Please let me know if there is any detail
> > article avaible for these configuration.
> 
> The script says that it will look up the CVSROOT
> filesystem hierarchy for a .mailUsersOnCommit file to be used
> which should contain the list of e-mail addresses to be sent
> the e-mail.
> 
> > I am very much new to the Linux enviornment. Please help
> 
> I have never used this
> cvsenhancements.sourceforge.net package, but I
> hope that I have cleared up some of your problems...
> 
>       Good luck,
>       -- Mark
> 
> > Thanks a lot
> > 
> > Best Regards
> > Vijay Mishra
> > 
> > -----Original Message-----
> > From: address@hidden
> > [mailto:address@hidden On Behalf Of Ed
> J
> > Sent: Friday, 22 July , 2005 5:16 PM
> > To: address@hidden
> > Subject: Re: CVS Mail Newbie quaestion
> > 
> > Look on cvsenhancements.sourceforge.net. For
> > emailing, I use two perl scripts I found there.
> > 
> > The first script is doLog. It's the hook to send
> > an email. You can control who gets emailed on a
> > directory-by-directory basis. CVS will call it
> > once for each directory in which you've made
> > commits. Unfortunately, you get a kind of
> > spamming effect when you commit from multiple
> > directories at once.
> > 
> > That problem is solved by the second script,
> > accumMail. It will defer and accumulate emails
> > generated by doLog. As a result, a commit within
> > multiple directories will produce just one email
> > with all the commit information, delayed by a
> > time you can control.
> > 
> > Ed J
> > 
> > "Vijay Mishra" <address@hidden> wrote in message
> > news:address@hidden
> > >
> > > Dear All,
> > >
> > > I have just finished setting up of CVS on my
> > > Linux box. I am pretty much new to CVS and
> > > just wondering can I setup email alerts for
> > > all my developers as soon as someone commit
> > > changes on CVS?
> > >
> > > I have searched the google but can't find a
> > > good article on that.
> > >
> > > Any sort of help will be highly appreciated.
> > >
> > >
> > > Best Regards
> > > Vijay Mishra
> > >
> > >
> > >
> > >
> > 
> > 
> > _______________________________________________
> > Info-cvs mailing list
> > address@hidden
> > http://lists.nongnu.org/mailman/listinfo/info-cvs
> > 
> > 
> > 
> > _______________________________________________
> > Info-cvs mailing list
> > address@hidden
> > http://lists.nongnu.org/mailman/listinfo/info-cvs
> > 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (FreeBSD)

iD8DBQFC5J9MCg7APGsDnFERAsL8AKDX2HNzO7ex0Ju6XHn4xhwP9pmGYACgpKlY
BWLUbkOYh4s+/9VAGc/1aZk=
=w3/M
-----END PGP SIGNATURE-----




reply via email to

[Prev in Thread] Current Thread [Next in Thread]