Sponsored Content
Operating Systems Linux How to push Tomcat logs to remote syslog server? Post 302839271 by RavinderSingh13 on Thursday 1st of August 2013 03:08:20 AM
Old 08-01-2013
Hello,

Hope I have understood your requirement correctly. You can use winscp tool to put the logs in to some other server.



Thanks,
R. Singh
 

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
KDOC(1) 						     KDOC Documentation System							   KDOC(1)

NAME
KDOC -- Programmers' Documentation Extraction and Generation Tool SYNOPSIS
kdoc [-DqpieaP] [-f format] [-n libname] [-d outdir] [-u url] [-l lib] kdoc [--help] kdoc [--version] DESCRIPTION
KDOC uses specially formatted comments in your C++ headers and CORBA IDL files to create cross-referenced documentation in various formats. KDOC can also correctly handle "signal" and "slot" specifiers as used by the Qt GUI Toolkit. EXAMPLES
kdoc -f html -d /home/web/komdoc -n kom *.idl kdoc -d /home/web/kdecore -u "http://www.mydomain/kdecore/" -n kdecore ~/kdelibs/kdecore/*.h -lqt OPTIONS
--stdin, -i Read the filenames to process from standard input. Ignored if filenames are specified at the command line. --format <string>, -f <string> Generate output in the specific format. This can be used many times to generate documentation in multiple formats. The default format is "html". See the OUTPUT FORMAT OPTIONS section for a list of available formats. --outputdir <path>, -d <path> Write output in the specified path. --url <url>, -u <url> The URL which will be used for links when cross-referencing with this library. --name <string>, -n <string> Set the name of the library being processed, eg "kdecore" If no name is set, no index file is produced. --xref <library>, -l <library> Cross-reference with the specified library. This will allow referencing of classes etc that exist in the linked library. This option can be specified multiple times. For linking to work, you need to have generated documentation for the linked library with kdoc, so that the necessary index file is produced. --libdir <path>, -L <path> Set the directory that will be used to store the index files generated for cross-referencing. This is also used to search for index files for xref. The default is $HOME/.kdoc. If multiple paths are specified, each will be searched in order of specification on the command line. Unless --liboutdir is specified (see below), the generated .kdoc file will be written to the first path specified with this option. --liboutdir <path> Set the directory where newly created xref libraries (see above) will be written. The default is the libdir. --compress, -z Compress generated KDOC index files with gzip to save space. --private, -p Document all private members. These are not documented by default. --skip-internal, -i Do not document internal members. They are documented as internal by default. --skip-deprecated, -e Do not document deprecated members. They are documented as deprecated by default. --strip-h-path Strip the path from the filenames in the output. PREPROCESSOR OPTIONS
--cpp, -P Pass each source file through the C preprocessor. Currently g++ is required for this, but this requirement will change before 2.0. Directories for inclusion in the preprocessor header search path can be specified via the -I option. --docincluded Parse files that are included by the preprocessor #include macro. This is off by default. -cppcmd <command>, -C <command> Specify the preprocessor command that will be used. The default is: g++ -Wp,-C -E All specified -I paths will be appended to the command. This option quietly enables the -P option. --includedir <path>, -I <path> Add a directory to the preprocessor's header search paths. Requires the -P option. This option can be specified multiple times. OUTPUT FORMAT OPTIONS
html Output documentation in HTML format. This is the default. latex Output documentation as a LaTeX document. man Output documentation as man pages. texinfo Output documentation in texinfo format. You must set the library name with the -n option for the output to be generated. docbook Output documentation in the DocBook SGML format. You must set the library name with the -n option for the output to be generated. check Print a report about the documentation, eg undocumented classes and functions. Output format modifiers --html-css <url> In HTML format, the stylesheet specified by this option will be used by the generated documentation. --html-cols <1, 2 ..> In HTML format, set the number of columns for the Class Index. --html-logo <image url> In HTML format, specify the logo image to display on every page. It will appear to the left of the quick links. CROSS-REFERENCING LIBRARIES FILES
*.kdoc, *.kdoc.gz These are files that contain information about a library that has been processed with kdoc. It is read for cross-referencing with other libraries when the -l option is used. The .gz extension signifies gzipped cross-reference files. kdoc is capable of reading these, and generates them when the -z option is used. ENVIRONMENT
KDOCLIBS If this is set, it is used as the default for the directory where generated cross-reference index files are saved. See also the --lib- dir option. SEE ALSO
See qt2kdoc for info on linking with the Qt docs, and makekdedoc for info on generating documentation for the KDE libraries. BUGS
Lots and Lots. Please send reports to the address kdoc@kde.org. AUTHOR
Sirtaj Singh Kang <taj@kde.org>. KDOC has a web page at: http://www.ph.unimelb.edu.au/~ssk/kde/kdoc COPYRIGHT
The KDOC tool is Copyright (c) 1998 by Sirtaj Singh Kang. KDOC is free software under the conditions of the GNU Public License. 2.0a54 2001-05-20 KDOC(1)
All times are GMT -4. The time now is 03:16 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy