Sponsored Content
Operating Systems Linux How to push Tomcat logs to remote syslog server? Post 302839341 by heshandh on Thursday 1st of August 2013 05:46:34 AM
Old 08-01-2013
Hi Singh,

Actually I don't want to use winscp. I need to automate using my script.
 

9 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Problem with Unix script to start remote Tomcat

I have Tomcat installed on a Unix box and I need to start it remotely from another Unix box. Tomcat is started using a script. When this script is run locally everything is fine. When I run the same script from remote box, tomcat starts but the command running the script does not terminate.:( ... (2 Replies)
Discussion started by: shrgh
2 Replies

2. UNIX for Dummies Questions & Answers

TomCat access in an Remote Linux Server

Hi all, I Installed Tomcat in an remote linux server (/usr/tomcat)and start service, using ./startup.sh (and tried with ./catalina.sh too). //----------------------------------------------------------------// # ./startup.sh Using CATALINA_BASE: /usr/tomcat/apache-tomcat-6.0.16/ Using... (1 Reply)
Discussion started by: gothama
1 Replies

3. Linux

sending messages from auditd logs to syslog server

I have the auditd running and I need to send the audit logs to a remote syslog server. Anyideas on how to do that? (1 Reply)
Discussion started by: jmathenge
1 Replies

4. Red Hat

Sending all apache logs to Syslog Server

Hi All, I need to send all apache logs to local syslog and then to syslog server (STRM – Security Threat response manager). I follow these steps:- vi /etc/httpd/conf/httpd.conf Added these lines :- ErrorLog syslog:local1 LogLevel notice Then in syslog.conf:- local1.crit... (3 Replies)
Discussion started by: sidhurana
3 Replies

5. UNIX for Advanced & Expert Users

Forwarding syslog msgs to remote server non standard port

Hello Forumers! Has anyone successfully implemented forwarding of syslog messages to a remote server which is listening on a port other than udp514? Thanks! (3 Replies)
Discussion started by: bluescreen
3 Replies

6. Shell Programming and Scripting

Problem starting of Tomcat on remote host

Hi All, I have several Tomcat 7.0.12 installations on remote servers for different projects. I need to start and stop them from a centralized server. Once I start the server remotely using ssh commands, server starts successfully but prompt does not exit. It keeps on holding. I have... (4 Replies)
Discussion started by: bhaskar_m
4 Replies

7. Web Development

Tomcat - Error Logs

Hi Gurus, Our tomcat server was found hanging and responding to requests although ports 8080 & 8009(AJP) were found in listening state. The catalina.out had the below output: We have JavaMelody(Monitoring tool) packaged along with our application and it seems that monitoring through... (3 Replies)
Discussion started by: Hari_Ganesh
3 Replies

8. UNIX for Dummies Questions & Answers

Syslog Messages from Remote Server are not writing to Log File Anymore

Hello All, Server: SUSE Linux Enterprise Server 11.3 (x86_64) Syslog-ng Version: syslog-ng 2.0.9 We have configured a Cisco router to send it's log messages to this server listed above. This has been working just perfectly for the last couple months, but we had never setup the log... (9 Replies)
Discussion started by: mrm5102
9 Replies

9. Shell Programming and Scripting

Script connect to remote server, not find files and exit only from remote server, but not from scrip

I have a script, which connecting to remote server and first checks, if the files are there by timestamp. If not I want the script exit without error. Below is a code TARFILE=${NAME}.tar TARGZFILE=${NAME}.tar.gz ssh ${DESTSERVNAME} 'cd /export/home/iciprod/download/let/monthly;... (3 Replies)
Discussion started by: digioleg54
3 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 03:43 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy