Sponsored Content
Full Discussion: RHCS debug log level
Operating Systems Linux Red Hat RHCS debug log level Post 302513066 by sixstrings on Tuesday 12th of April 2011 09:22:33 AM
Old 04-12-2011
Use this in your rm tag.


<rm log_facility="local4" log_level="7">
 

10 More Discussions You Might Find Interesting

1. Programming

how to debug

i am new to solaris i have one module which contain certain header files and sub modules i want ot execute the module and c what the values are beeing assigned to variables is makefile only solution for this is there any editor to help it,so that i can c the flow of the program and also... (1 Reply)
Discussion started by: ramneek
1 Replies

2. Shell Programming and Scripting

runing script with log level 4

i have bash script with some batches, and when i putt log level 4 in script i get error while executing or if i rung script.sh with parameter log level 4. i appriciate some advice :) (3 Replies)
Discussion started by: unknown1
3 Replies

3. Solaris

Difference between run level & init level

what are the major Difference Between run level & init level (2 Replies)
Discussion started by: rajaramrnb
2 Replies

4. UNIX for Dummies Questions & Answers

How to change the log level for cron?

Hello, I'm wondering how to change the log level to level 2 for cron without manually have to restart it with every boot. I didn't thing this would be hard to find, but searching has cause me to come up empty. System is Ubuntu Karmic/9.10 With thanks, Narnie (6 Replies)
Discussion started by: Narnie
6 Replies

5. Red Hat

How to install RHCS on RHEL 6.1

Hi , I want to install RHCS on a remote RHEL machine. This machine is in amazon ec2, is there any way to do it without accessing the media? # cat /etc/redhat-release Red Hat Enterprise Linux Server release 6.1 (Santiago) Thanks in advance. (1 Reply)
Discussion started by: sussus2326
1 Replies

6. Shell Programming and Scripting

If - then -else debug please

Can you help please ? ./get_df.sh: syntax error at line 13 : `then' unexpected #!/bin/ksh while : do PER=`df -h /DATA/ | nawk '{if (NR != 1) { sub (/%/,""); print $(NF-1)}}'` if then if] then mailx -s "FS over 90 per" me@company.com touch... (2 Replies)
Discussion started by: drbiloukos
2 Replies

7. AIX

Missing Base level fileset of bos.adt.debug

I need to install "bos.adt.debug" in AIX ( version 6100-06-05-1115). I found the right bff U818918 and I smitty to install it and encountered the "missing requisites" error as attached in which missing the "base level fileset" bos.adt.debug 6.1.0.0. And I couldn't find this fileset from the... (3 Replies)
Discussion started by: bshcheng
3 Replies

8. OS X (Apple)

Debug help

Hello, I was looking at kernel log's and found some parts what was "interesting" I previously started looking what has been going on in my computer because I had hacker attacks on my machine. Installed Avira & Little Snitch - softwares Previously my computer opened few folders what I have... (1 Reply)
Discussion started by: Scourge-
1 Replies

9. Red Hat

SSL certificate generation on OS level or application level

We have a RHEL 5.8 server at the production level and we have a Java application on this server. I know of the SSL certificate generation at the OS (RHEL) level but it is implemented on the Java application by our development team using the Java keytool. My doubt is that is the SSL generation can... (3 Replies)
Discussion started by: RHCE
3 Replies

10. AIX

Auth module debug log

How can I log the auth and security module messages in AIX syslog ? I need to see all authentication requests coming (when users login) and the calls made for authenticating these users. Target system is AIX 6.1 (1 Reply)
Discussion started by: vs1
1 Replies
pppoec(1)						      General Commands Manual							 pppoec(1)

NAME
pppoec - PPPoE (Point to Point Protocol over Ethernet) client SYNOPSIS
interface-name interface-name config-file] debug-level] log-file] retry-number] DESCRIPTION
discovers an access concentrator that is willing to offer services to the client. It obtains a unique session-id from the selected access concentrator. then forks a daemon which performs the session phase functionalities of PPPoE as mentioned in RFC 2516. Options supports the following options: Specify the configuration file with absolute path to be used by The default configuration file is Specify the debug level at which logging has to be enabled. The three debug levels are: Logs all error messages. To log these messages, type on the command line. Logs all warning messages. To log these messages, type on the command line. Logs function level debug messages. To log these messages, type on the command line. Specify the name of the network interface (e.g., to be used for the PPPoE session. Specify the log file with absolute path, to which pppoec must log all messages. The default log file is Specify the frequency of PADI (PPPoE Active Discovery Initiation) or PADR (PPPoE Active Discovery Request) packet retransmission when an access concentrator does not respond to the client's request. The default value is 3. EXAMPLES
An example usage of the command is as follows: WARNINGS
Note that, you cannot run the client daemon without file. See pppoec.conf(4) for more information. Also, do not use to terminate Instead, use to kill the client daemon. AUTHOR
was developed by Hewlett-Packard. FILES
PPPoE server daemon PPPoE relay PPPoE client configuration file PPP daemon SEE ALSO
pppd(1), pppoerd(1M), pppoesd(1M), pppoec.conf(4). pppoec(1)
All times are GMT -4. The time now is 05:23 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy