[NTLUG:Discuss] cannot execute /usr/bin/perl /etc/vocp/vocp.pl

Robert Thompson ntlug at thorshammer.org
Mon Nov 28 18:18:53 CST 2005


I am not familiar with vgetty, but what part of vgetty
runs /etc/vocp.vocp.pl? Does it get run from cron, the web (apache), a
daemon, etc? Each of these should have a user associated with the
program (cron, apache, www, nobody, etc). Once you know that user you
can su to them and run the script to see what errors you get (you will
probably need to edit /etc/passwd and give them a valid shell if
it's /sbin/nologin or somesuch (remember to change it back when you're
done)).

Robert Thompson

On Mon, 2005-11-28 at 17:09 +0000, m m wrote:
> Robert and all:
> 
> Yes,  perl is in the /usr/bin.
> and the vocp.pl has been modified to fit my system. ( I guess :) )
> 
> The good question is
> "Which user is attempting to execute /etc/vocp/vocp.pl"
> 
> I don't know which user execute /etc/vocp/vocp.pl.
> That is why I set the permission to 777
> does the permission 777 don't count?
> 
> How do I find out which user  is attempting to execute the program?
> 
> Thanks.
> 
> >From: Robert Thompson <ntlug at thorshammer.org>
> >Reply-To: NTLUG Discussion List <discuss at ntlug.org>
> >To: NTLUG Discussion List <discuss at ntlug.org>
> >Subject: Re: [NTLUG:Discuss] cannot execute /usr/bin/perl /etc/vocp/vocp.pl
> >Date: Sun, 27 Nov 2005 19:19:05 -0600
> >
> >If you do a 'which perl' is it in /usr/bin? Which user is attempting to
> >execute /etc/vocp/vocp.pl and can you su to that user and execute the
> >script? Are there any configs in vocp.pl that need to be changed?
> >
> >It's best to troubleshoot the first error message(s) before going to the
> >next ones unless you know they are harmless. The early errors could be
> >the cause of the later ones.
> >
> >Robert Thompson
> >
> >
> >On Sun, 2005-11-27 at 18:21 +0000, m m wrote:
> > > Hi All,
> > >
> > > I spend all my Thanksgiving holiday with "vgetty".  Here is my problem.
> > > Please help, Thanks
> > >
> > > Here is the log file, I inseerted my question in the log file:
> > >
> > > 04/30 01:05:12 yS0  reading ring_type ring configuration from config 
> >file
> > > /etc/mgetty+sendfax/voice.conf
> > > 04/30 01:05:14 yS0  vgetty: Executing shell script /etc/vocp/vocp.pl 
> >with
> > > shell /usr/bin/perl
> > > 04/30 01:05:14 yS0  vgetty: cannot execute /usr/bin/perl 
> >/etc/vocp/vocp.pl
> > >
> > > - why does this happened? the /etc/vocp/vocp.pl has set to 777
> > > - I am able to run it on command line
> > >
> > > 04/30 01:05:14 yS0  vgetty: Got child 3906 exit status 25344 signal
> > > 04/30 01:05:14 yS0  vgetty: could not write to shell
> > >
> > > -why does this "write to shell"  mean?
> > >
> > > 04/30 01:05:14 yS0  vgetty: shell script /etc/vocp/vocp.pl exited 
> >unnormally
> > > 04/30 01:05:14 yS0  playing voice file 
> >/var/spool/voice/messages/usr_eng.rmd
> > > 04/30 01:05:14 yS0  vgetty: cannot set effective GID to 503: Operation 
> >not
> > > permitted
> > >
> > > - what permission and to whom?
> > > - GID 503 is phone
> > > - in /etc/group I have a line like this
> > > -  phone:x:503:
> > > - and I  appended root
> > > - phone:x:503:root
> > > - still have the same peoblem
> > >
> > >
> > > 04/30 01:05:14 yS0  vgetty: Could not play greeting message
> > > 04/30 01:05:15 yS0  recording voice file
> > > /var/spool/voice/incoming/v-3875-925434314.rmd
> > > 04/30 01:05:15 yS0  vgetty: cannot set effective GID to 503: Operation 
> >not
> > > permitted
> > > 04/30 01:05:15 yS0  vgetty: Could not record a message
> > > --
> > > 04/30 01:05:15 yS0  vgetty: experimental test release 0.9.32 / with 
> >duplex
> > > patch
> > > 04/30 01:05:15 yS0  mgetty: interim release 1.1.33-Apr10
> > > 04/30 01:05:15 yS0  reading generic configuration from config file
> > > /etc/mgetty+sendfax/voice.conf
> > > 04/30 01:05:15 yS0  reading program vgetty configuration from config 
> >file
> > > /etc/mgetty+sendfax/voice.conf
> > > 04/30 01:05:15 yS0  reading port ttyS0 configuration from config file
> > > /etc/mgetty+sendfax/voice.conf
> > > 04/30 01:05:15 yS0  check for lockfiles
> > > 04/30 01:05:15 yS0  locking the line
> > > 04/30 01:05:16 yS0  lowering DTR to reset Modem
> > > 04/30 01:05:17 yS0  send: \dATQ0V1H0[0d]
> > > 04/30 01:05:17 yS0  waiting for ``OK'' ** found **
> > > 04/30 01:05:17 yS0  send: ATS0=0Q0&D3&C1[0d]
> > > 04/30 01:05:17 yS0  waiting for ``OK'' ** found **
> > > 04/30 01:05:17 yS0  mdm_send: 'ATI'
> > > 04/30 01:05:18 yS0  USR Courier/Sportster V.34(+) detected
> > > 04/30 01:05:18 yS0  mdm_send: 'ATI3'
> > > 04/30 01:05:18 yS0  additional info: 'USRobotics Sportster Voice 33600 
> >Fax
> > > RS Rev. 2.0'
> > > 04/30 01:05:18 yS0  modem quirks: 0080
> > > 04/30 01:05:18 yS0  mdm_send: 'AT+FCLASS=2.0' -> OK
> > > 04/30 01:05:18 yS0  mdm_send: 'AT+FAA=1;+FCR=1' -> OK
> > > 04/30 01:05:18 yS0  mdm_send: 'AT+FBO=1' -> OK
> > > 04/30 01:05:18 yS0  mdm_send: 'AT+FNR=1,1,1,0' -> OK
> > > 04/30 01:05:19 yS0  mdm_send: 'AT+FLI="49 115 xxxxxxxx"' -> OK
> > > 04/30 01:05:19 yS0  mdm_send: 'AT+FCC=1,5,0,2,0,0,0,0' -> OK
> > > 04/30 01:05:19 yS0  detecting voice modem type
> > > 04/30 01:05:21 yS0  US Robotics detected
> > > 04/30 01:05:22 yS0  US Robotics voice modem
> > > 04/30 01:05:22 yS0  This is a driver beta version. V0.4.b3
> > > 04/30 01:05:22 yS0  VTD setup successful
> > > 04/30 01:05:24 yS0  waiting...
> > >
> > > _________________________________________________________________
> > > FREE pop-up blocking with the new MSN Toolbar  get it now!
> > > http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/
> > >
> > >
> > > _______________________________________________
> > > https://ntlug.org/mailman/listinfo/discuss
> > >
> >
> >
> >_______________________________________________
> >https://ntlug.org/mailman/listinfo/discuss
> 
> _________________________________________________________________
> Is your PC infected? Get a FREE online computer virus scan from McAfee 
> Security. http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963
> 
> 
> _______________________________________________
> https://ntlug.org/mailman/listinfo/discuss
> 





More information about the Discuss mailing list