Problems with View/Pro and Command
[1/7] from: holger:rebol at: 12-Sep-2001 10:02
On Wed, Sep 12, 2001 at 12:21:07PM -0400, CRIBBSJ wrote:
> Problem #1:
> I wrote a script that ftp's some files from one of my company's Linux
<<quoted lines omitted: 4>>
> seems that because I am running it using View/Pro, it is trying to connect to
> the display server even though I don't need it to.
Try adding something like
export DISPLAY=localhost:0
or
setenv DISPLAY localhost:0
depending on which shell you use and where your X server is, to the
script run by cron.
Connecting to the X server is done automatically to ensure that
system/view/screen-face/size is set correctly. That's why you see
the error.
View/Pro is not really intended for use with non-interactive scripts.
That's what Command is for.
> Problem #2:
> This problem actually stems from the first. Since I think the first problem
<<quoted lines omitted: 6>>
> FTP. I am running this on a Redhat 6.1 box and I am wondering if there is
> some kind of problem with Command running on this version of OS.
No. Sounds like your user.r is wrong. You are probably using different
settings (for proxy or ftp-passive) for Command than you are using for
View/Pro. If you installed Command and View in different places then
your user.r might just be in the wrong directory.
> What also makes me mad is that I have spent over $400 recently buying
> View/Pro and Command, yet I can't get ANY technical support from RT.
Asking on the mailing list is usually the easiest way. We do respond
through feedback as well, and sometimes more quickly, but have fallen
a little behind there recently, partly due to vacations. Sorry for that.
--
Holger Kruse
[holger--rebol--com]
[2/7] from: holger:rebol at: 12-Sep-2001 11:19
On Wed, Sep 12, 2001 at 02:11:50PM -0400, CRIBBSJ wrote:
> Holger, I appreciate your response. Maybe I am mistaken, but I thought using
> feedback was our main method of communication with RT if we had a problem
> with a purchased product.
Yes, you are right. Usually it is...
> I had already tried the things you recommended before I posted the problems
> to this list, with no success. However, I am assuming, by your response,
> that if I can get View/Pro to run the script correctly, that means Command
> should work also.
Yes. There is no difference in the way both versions handle FTP.
--
Holger Kruse
[holger--rebol--com]
[3/7] from: cribbsj:oakwood at: 12-Sep-2001 14:11
On Wednesday 12 September 2001 01:02 pm, you wrote:
> Asking on the mailing list is usually the easiest way. We do respond
> through feedback as well, and sometimes more quickly, but have fallen
> a little behind there recently, partly due to vacations. Sorry for that.
Holger, I appreciate your response. Maybe I am mistaken, but I thought using
feedback was our main method of communication with RT if we had a problem
with a purchased product.
I had already tried the things you recommended before I posted the problems
to this list, with no success. However, I am assuming, by your response,
that if I can get View/Pro to run the script correctly, that means Command
should work also. I will try again to get Command to work.
Thanks again for your response.
Jamey.
[4/7] from: cribbsj:oakwood at: 12-Sep-2001 15:16
On Wednesday 12 September 2001 01:02 pm, you wrote:
> > Problem #2:
> >
<<quoted lines omitted: 12>>
> View/Pro. If you installed Command and View in different places then
> your user.r might just be in the wrong directory.
Okay, Holger, here is what I tried. I reinstalled Command, set everything
up, and tried to ftp thru the firewall to the site I am trying to get to.
Got the same error about a socket listen error on the proxy.
Next, I installed View/Command and set up the user and prefs files using all
the correct stuff. Tried to ftp, same error.
Finally, I installed regular View (the free one). I used the same user.r and
prefs.r that I used above and tried to ftp to the site...and it worked!!!
So, to me, this indicates some kind of difference between Command (or
View/Command) and regular View. Any ideas?
Jamey.
[5/7] from: holger:rebol at: 12-Sep-2001 13:55
On Wed, Sep 12, 2001 at 03:16:07PM -0400, CRIBBSJ wrote:
> Okay, Holger, here is what I tried. I reinstalled Command, set everything
> up, and tried to ftp thru the firewall to the site I am trying to get to.
<<quoted lines omitted: 5>>
> So, to me, this indicates some kind of difference between Command (or
> View/Command) and regular View. Any ideas?
Try adding
system/schemes/ftp/passive: true
(or false, try either way) at the beginning of your script.
--
Holger Kruse
[holger--rebol--com]
[6/7] from: cribbsj:oakwood at: 12-Sep-2001 12:21
I have run into a couple of problems, one with View/Pro and one with Command.
I have submitted the problems to feedback.r days ago, but have not heard a
word from RT. I was wondering if anyone on the list had encountered similar
problems.
Problem #1:
I wrote a script that ftp's some files from one of my company's Linux
servers, through our firewall, and to a ftp server on the net. It works
great when I run it from a telnet session on the Linux box, but when I
schedule it through cron, it fails saying it cannot connect to the X display
server. Even though I have no gui (view or vid) commands in my script, it
seems that because I am running it using View/Pro, it is trying to connect to
the display server even though I don't need it to. The reason am using
View/Pro instead of just Core is that I needed shell access to first encrypt
the file using PGP.
Problem #2:
This problem actually stems from the first. Since I think the first problem
has to do with that I am using View/Pro, I convinced my boss to cough up
$350 to purchase Command. That way, I could have shell access to run PGP
without having to worry about the interpreter trying to connect to a display
server when I run it from cron. Great idea, right? Well, the script that I
wrote works great on View/Pro, but it bombs out under Command. I get an
error saying that there is some kind of TCP socket listen error when I try to
FTP. I am running this on a Redhat 6.1 box and I am wondering if there is
some kind of problem with Command running on this version of OS.
So, to make a long rant short, I am approaching a deadline with putting this
script into production. I am close to rewriting the whole thing in Perl,
which is not going to make me happy.
What also makes me mad is that I have spent over $400 recently buying
View/Pro and Command, yet I can't get ANY technical support from RT. I
really like the language, but I am thinking that I made a mistake when I
decided to start using it for work related things.
Jamey.
[7/7] from: cribbsj:oakwood at: 13-Sep-2001 10:25
On Wednesday 12 September 2001 04:55 pm, you wrote:
> On Wed, Sep 12, 2001 at 03:16:07PM -0400, CRIBBSJ wrote:
> > Okay, Holger, here is what I tried. I reinstalled Command, set
<<quoted lines omitted: 13>>
> system/schemes/ftp/passive: true
> (or false, try either way) at the beginning of your script.
Tried it both ways (true and false) and still got the error:
Access Error: Error opening socket listen port
Where: connect-proxy
Near: read ftp://user:[pass--host]/
Jamey
--
To unsubscribe from this list, please send an email to
[rebol-request--rebol--com] with
unsubscribe" in the
Notes
- Quoted lines have been omitted from some messages.
View the message alone to see the lines that have been omitted