Sponsored Content
Operating Systems Linux SuSE vsftpd won't start on SLES 10 Post 302090084 by dave521 on Friday 22nd of September 2006 10:26:58 AM
Old 09-22-2006
In the /var/log/warn file:

zmd: NetworkManagerModule (WARN): Failed to connect to NetworkManager
zmd: Daemon (WARN): Not starting remote web server

The /var/log/rcvsftp.log file is empty.

How do I increase the level of logging? The only options i see in the vsftpd.conf file related to the logging level deal with logging requests/responses, and uploads/downloads.
 

10 More Discussions You Might Find Interesting

1. Solaris

nfsd won't start at boot up

Hi Inexplicably, nfsd no longer starts automatically on our Sun boxes running Solaris 9, so that 'automount' no longer functions automatically. The problem first manifested itself when we could not access files on any of the nfs automounted directories in our LAN after one of the servers (say... (19 Replies)
Discussion started by: dcshungu
19 Replies

2. UNIX for Dummies Questions & Answers

HP 10.20 Won start

After I log ino the machine, a window pops up indicating that I should check that the HOSTNAME is the same in these three files /etc//rc.configd/netconf /etc/hosts /var/adm/inetd.sec How do I change the hostname in these files? Thanks, Mike h (1 Reply)
Discussion started by: hutchin
1 Replies

3. Solaris

production server won't start please help me!

if anyone can help me here I will be in debt eternaly. I'm in a spot here fearing for my job. I tried to install a new scsi array on our E5500. I powered it down correctly, removed the terminator, connected the array and powered it on. It was taking so long to come up I freaked out and powered... (3 Replies)
Discussion started by: NewSolarisAdmin
3 Replies

4. UNIX for Dummies Questions & Answers

ToolTalk won't start

on my AIX 6.1 CDE's ToolTalk server won't start. It says: dtsession: Unable to exec /usr/dt/install/oldrules/dtrmrules.driver. A file or directory in the path name does not exist. How can I fix this? (0 Replies)
Discussion started by: rein
0 Replies

5. SuSE

How to start Apache2 and vsftpd at boot

My apache and ftp server is working fine but when I reboot the system ftp and web server is not running automatically. Please advise on how to start apache and ftp at boot. (9 Replies)
Discussion started by: real-chess
9 Replies

6. Red Hat

vsftpd service failed to start

hi, i am using RHEL 5 and i am not able to on the vsftp i have tried to on the vsftp service using command service vsftpd start Starting vsftpd for vsftpd: i am posting the content of my /etc/xinetd.d/vsftpd file # description: The vsftpd FTP... (2 Replies)
Discussion started by: u.n.i.x
2 Replies

7. Red Hat

VSFTPD Service Failed to Start

Today I have installed VSFTPD but service is failing to start. We have been using standard FTP successful but need to introduce an FTPS option. I have run YUM install VSFTPD and everything appeared to load ok. (If I run rpm - qa | grep vsftpd I get vsftpd-2.0.5-16.el5_4.1 which I... (4 Replies)
Discussion started by: PaulComins
4 Replies

8. SuSE

SLES 9 vs SLES 11 hard drive cache read timings are diffrent

Can anyone give me a little clue on why the hard drive cache read timings on sles 9 is better then sles 11? The same hardware was used in both test. I even deleted the ata_generic module from initrd. The speed difference is 10MB vs 5 MB Thanks (1 Reply)
Discussion started by: 3junior
1 Replies

9. Red Hat

vftpd won't start..

Hi, I am using redhat enterprise 5.7 have installed vsftpd successfully but every time I try to start the service it comes up with FAILED. Here is the contents of the vsftpd.conf file: # Allow anonymous FTP? (Beware - allowed by default if you comment this out). anonymous_enable=YES # #... (3 Replies)
Discussion started by: titley100
3 Replies

10. Fedora

Um, my computer suddenly won't start up

Okay, I'm fairly green at Fedora, but it has worked like a gem until now. On startup I get a screen that says this: Booting 'Fedora (3.6.11-4.fc16.x86_64)' Loading Fedora (3.611-4.fc16.x86_64) Loading initial ramdisk .... _Fedora-16-x86_6: Unexpected inconsistency; run fsck manually. ... (6 Replies)
Discussion started by: Anchorsteamer
6 Replies
tntnet.properties(7)						Tntnet users guide					      tntnet.properties(7)

NAME
tntnet.properties - configuration-file for tntnet (8) DESCRIPTION
tntnet(8) uses cxxtools for logging and is configured in the configuration-file tntnet.properties. Because cxxtools is a meta-logging-library, which can be compiled to use different logging-libraries, the content of tntnet.properties is dependend of the underlying logging-library. Cxxtool has a built-in logging-library as default, which is documented here. format The format of tntnet.properties is line-based. A line consists of a variable-name followed by a equals-symbol and a value. Lines, which does not follow this format and lines, which start with a hash (#), are ignored. It is recomended to prefix non-empty comments with a hash to make clear, that it is a comment. level The logging-library has 5 levels for logging: fatal, error, warn, info and debug. Fatal has the highers priority and "debug" the lowest. category Each log-message has a category. Categories are hierarchical. Names of subcategories are devided by a dot. log-message Each log-message has a level and a category. If the level of the message is higher or equal to the level of the category, the message is logged. To assign a level to a category put a line with the word "logger", a dot, the category, the symbol "=" and the category into tnt- net.properties. Only the first letter of the value is checked and case is ignored, so e.g. info can be specified with INFO, info, I or even ixxxx. If no level is specified for the current category, the upper category is checked. If nothing is found, the default level is used. The default level is specified by the variable "rootLogger". If no rootLogger is specified, the level error is used. destination If nothing else is specified, log-messages are printed to standard-output. To redirect output to a file, specify the filename with the variable file. The cxxtools-logger can limit the size of the log-file by rolling log-files. If the limit is reached, the current file is renamed by appending ".1" to it. If there is already a file with that name, this file is renamed to "*.2" and so on, until the maximum backupfile limit is reached. The oldest file is deleted then. To specify the maximum file size, set the variable maxfilesize. The value specified here can be postfixed with 'k' or 'M' to specify kBytes or MBytes. The maximum fileindex backed up is set with maxbackupindex. Since writing the file can take some time, output can be buffered and written physically in regular intervals. The interval is specified in milliseconds with the variable flushdelay. The logging-library starts a background-thread, which flushes the buffer regulary. This improves logging-speed significantly. The problem is, that a background-thread is used, which consumes resources and if the program crashes, the most recent log-messages might not be in the file. Log-messages can be sent to another host in the network with udp. This is done by specifying a hostname and a port with the variable host. The value must be a hostname, followed by a ':' and a port. Each log-message is sent in a single udp-message. EXAMPLES
logging to standard-output: rootLogger=INFO logger.tntnet=WARN logging to a file with rolling file and a background-flusher: rootLogger=INFO logger.tntnet=WARN file=tntnet.log maxfilesize=1MB maxbackupindex=10 flulshdelay=100 logging to another host rootLogger=INFO logger.tntnet=WARN host=pluto.tntnet.org:1234 AUTHOR
This manual page was written by Tommi Makitalo <tommi@tntnet.org>. SEE ALSO
tntnet(8) Tntnet 2006-08-13 tntnet.properties(7)
All times are GMT -4. The time now is 10:00 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy