Sponsored Content
Full Discussion: Telnet FTP scripting
Top Forums UNIX for Dummies Questions & Answers Telnet FTP scripting Post 40592 by w33man on Thursday 18th of September 2003 12:45:40 PM
Old 09-18-2003
MySQL gander at

Yeah had a look just what i need. All i need to do now is write the scripts:
Shouldn't be a prob considering i dont have a clue about Unix, ah well such is life.

Cheers Crig
 

10 More Discussions You Might Find Interesting

1. IP Networking

FTP or Telnet

Dumb question I'm sure but how on earth do I transfer files from a sco unix machine to my windows 2000 machine. I'm typing commands on my Win2000 machine. All I can seem to do is move files around on the unix system? (8 Replies)
Discussion started by: Timbash
8 Replies

2. Cybersecurity

One accout for FTP other to TELNET

Hi All, If I want to have two user accounts from the same grop in UNIX Solaries. However, I want one of them to be used only for FTP while the other for TELNET. Can anybody tell me how to do that? Best Regards (13 Replies)
Discussion started by: omran
13 Replies

3. UNIX for Dummies Questions & Answers

scripting Telnet

can someone tell me how i can write a shell script that will automatically log me in to any machines i want without bothering me for some password input? (i know i have to put in a password but I would like to take care of that in the script) can anyone help me here? (2 Replies)
Discussion started by: TRUEST
2 Replies

4. Answers to Frequently Asked Questions

Automate FTP / Scripting FTP Transfers

One of our most frequent questions is how to automate ftp transfers. There are several approaches. Since I'm writing this post, we will start with my favorite technique. :) In Automated FTP task I present a simple example of my ksh co-process technique. And note that later in this thread I... (0 Replies)
Discussion started by: Perderabo
0 Replies

5. Shell Programming and Scripting

Automating telnet and ftp

Hi, I want to automate FTP. I have a fair idea that this can be done using expect scripting. But I dont how to do it. Please, can anyone give me an example of how to do it in Unix. Thanks in advance (2 Replies)
Discussion started by: sendhilmani123
2 Replies

6. UNIX for Dummies Questions & Answers

Ftp, telnet etc. not operational?

Well I have the programs and everything and the program itself seems to work, but they don't seem to be operateble. I ALWAYS get connection refused on everything. ftp, telnet, rlogin, ssh etc. So it must have something to do with some setting that doesn't allow connections to external hosts or... (6 Replies)
Discussion started by: riwa
6 Replies

7. Shell Programming and Scripting

Shell scripting with Telnet

Hi, im brasilian, sorry for bad english ok? Well, im writing one honeypot, look: #!/bin/bash echo "" echo `cat /etc/welcome.pot` echo "" echo -n "login: "; read usuario echo -n "Password: " #stty -echo read -s senha #stty echo exit Running it in localhost, thats right: ... (1 Reply)
Discussion started by: juniordevil
1 Replies

8. Shell Programming and Scripting

Need Help on Telnet using PERL Scripting

Iam trying to connect to a system through Telnet using net::Telnet Module #!/usr/bin/perl -w use net::Telnet $myPassword = "abcdef"; $telnet = new Net::Telnet ( Timeout=>10, Errmode=>'die'); $telnet->open (10.10.20.00); $telnet->waitfor ('/USERCODE: $/i'); $telnet->print('abc');... (2 Replies)
Discussion started by: sudhakaryadav
2 Replies

9. Shell Programming and Scripting

BASH (or else) scripting for Telnet

Hi everybody, I am thinking on writing a shell script to telnet to Cisco routers, and I am looking for help. I have researched some and could not find much on the topic, or at least much of help anyway... I read "expect" is one solution, but I am looking for something more flexible, as I... (1 Reply)
Discussion started by: ppucci
1 Replies

10. Shell Programming and Scripting

Telnet using shell Scripting

i have written a script as shown below : telnet 10.161.240.2 8100 <?xml version="1.0"?> <login_command> <sequence id="1" /> <access id="1"/> <user name = "user1" password = "pass"/> </login_command> <?xml version="1.0"?> <RegistrationDescriptor> <sequence id="1" /> <access id="1"/>... (4 Replies)
Discussion started by: akrati1
4 Replies
GIMPTOOL(1)							 GIMP Manual Pages						       GIMPTOOL(1)

NAME
gimptool - perform various Gimpy functions SYNOPSIS
gimptool [--prefix[=DIR]] [--exec-prefix[=DIR]] [--version] [--help] [--quiet] [--silent] [-n] [--just-print] [--dry-run] [--recon] [--bindir] [--sbindir] [--libexecdir] [--datadir] [--sysconfdir] [--sharedstatedir] [--localstatedir] [--libdir] [--infodir] [--mandir] [--includedir] [--gimpplugindir] [--gimpdatadir] [--libs] [--libs-noui] [--cflags] [--cflags-noi] [--build plug-in.c] [--build-strip plug-in.c] [--install plug-in.c] [--install-strip plug-in.c] [--install-admin plug-in.c] [--install-bin plug-in] [--install-admin-strip plug-in.c] [--install-bin-strip plug-in] [--install-admin-bin plug-in] [--install-script script.scm] [--install-admin-script script.scm] [--uninstall-bin plug-in] [--uninstall-admin-bin plug-in] [--uninstall-script script.scm] [--uninstall-admin-script script.scm] DESCRIPTION
gimptool is a tool that can, among other things, build plug-ins or scripts and install them if they are distributed in one source file. gimptool can also be used by programs that need to know what libraries and include-paths Gimp was compiled with. This is especially useful in Makefiles. On Unix, gimptool is a script. On Windows, it is a program. They should be more or less compatible. This manual page describes the Unix script version. OPTIONS
gimptool accepts the following options: --version Print the currently installed version of Gimp on the standard output. --help Print out the help blurb, showing commonly used commandline options. --quiet Run quietly without echoing any of the build commands. --silent Run silently without echoing any of the build commands. Same as --quiet. -n Test mode. Print the commands but dont actually execute them. Useful for making dry runs for testing. --just-print Test mode. Print the commands but dont actually execute them. Same as -n. --dry-run Test mode. Print the commands but dont actually execute them. Same as -n. --recon Test mode. Print the commands but dont actually execute them. Same as -n. --bindir Outputs the bindir used to install the Gimp. --sbindir Outputs the sbindir used to install the Gimp. --libexecdir Outputs the libexecdir used to install the Gimp. --datadir Outputs the datadir used to install the Gimp. --sysconfdir Outputs the sysconfdir used to install the Gimp. --sharedstatedir Outputs the sharedstatedir used to install the Gimp. --localstatedir Outputs the localstatedir used to install the Gimp. --libdir Outputs the libdir used to install the Gimp. --infodir Outputs the infodir used to install the Gimp. --mandir Outputs the mandir used to install the Gimp. --includedir Outputs the includedir used to install the Gimp. --gimpdatadir Outputs the actual directory where the Gimp data files were installed. --gimpplugindir Outputs the actual directory where the Gimp plugins were installed. --build plug-in.c Compile and link plug-in.c into a Gimp plug-in. --build-strip plug-in.c Compile,link, and strip plug-in.c into a Gimp plug-in. --install plug-in.c Compile, link, and install plug-in.c into the user's personal Gimp plug-in directory ($HOME/.gimp-1.2/plug-ins) --install-strip plug-in.c Compile, link,strip, and install plug-in.c into the user's personal Gimp plug-in directory ($HOME/.gimp-1.2/plug-ins) --install-admin plug-in.c Compile, link, and install plug-in.c into the system-wide Gimp plug-in directory (/usr/lib/gimp/1.2/plug-ins) --install-bin plug-in Install plug-in into the user's personal Gimp plug-in directory ($HOME/.gimp-1.2/plug-ins) --install-admin-bin plug-in Install plug-in into the system-wide Gimp plug-in directory (/usr/lib/gimp/1.2/plug-ins) --install-bin-strip plug-in Install stripped plug-in into the user's personal Gimp plug-in directory ($HOME/.gimp-1.2/plug-ins) --install-admin-bin-strip plug-in Install stripped plug-in into the system-wide Gimp plug-in directory (/usr/lib/gimp/1.2/plug-ins) --install-script script.scm Install script.scm into the user's personal Gimp script directory ($HOME/.gimp-1.2/scripts) --install-admin-script script.scm Install script.scm into the system-wide Gimp script directory (/usr/share/gimp/1.2/scripts) --uninstall-bin plug-in Uninstall plug-in from the user's personal Gimp plug-in directory ($HOME/.gimp-1.2/plug-ins) --uninstall-admin-bin plug-in Uninstall plug-in from the system-wide Gimp plug-in directory (/usr/lib/gimp/1.2/plug-ins) --uninstall-script script.scm Uninstall script.scm from the user's personal Gimp script directory ($HOME/.gimp-1.2/scripts) --uninstall-admin-script script.scm Uninstall script.scm from the system-wide Gimp script directory (/usr/share/gimp/1.2/scripts) --libs Print the linker flags that are necessary to link a Gimp plug-in. --libs-noui Print the linker flags that are necessary to link a Gimp plug-in, for plugins that do not require the GTK libs. --cflags Print the compiler flags that are necessary to compile a Gimp plug-in. --clags-noui Print the compiler flags that are necessary to compile a Gimp plug-in for plugins that do not require the GTK libs. --prefix=PREFIX If specified, use PREFIX instead of the installation prefix that Gimp was built with when computing the output for the --cflags and --libs options. This option is also used for the exec prefix if --exec-prefix was not specified. This option must be specified before any --libs or --cflags options. --exec-prefix=PREFIX If specified, use PREFIX instead of the installation exec prefix that Gimp was built with when computing the output for the --cflags and --libs options. This option must be specified before any --libs or --cflags options. ENVIRONMENT
GTK_CONFIG to get the location of the gtk-config program. CC to get the name of the desired C compiler. CFLAGS to get the preferred flags to pass to the C compiler for plug-in building. DESTDIR to add a prefix to the install/uninstall path. LDFLAGS to get the prefered flags for passing to the linker. LIBS for passing extra libs that may be needed in the build process. For example, LIBS=-lintl . GTK_CONFIG path to the gtk-config shell script used by gimptool and in the build process of many gtk apps. SEE ALSO
gimp(1), gimprc(5), gimp-remote(1), gtk-config(1) AUTHORS
gimptool was written by Manish Singh (yosh@gimp.org) and based on gtk-config by Owen Taylor (owen@gtk.org). This man page was written by Ben Gertzfield (che@debian.org), and tweaked by Manish Singh (yosh@gimp.org), Adrian Likins (adrian@gimp.org) and Marc Lehmann (pcg@goof.com>). COPYRIGHT
Copyright (C) 1998 Owen Taylor and Manish Singh Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, pro- vided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in sup- porting documentation. Version 1.2.3 26 June 2001 GIMPTOOL(1)
All times are GMT -4. The time now is 05:42 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy