Discuss

discuss@lists.centos.org

34753 discussions

Vsftp is not writing a log file
by Todd Cary 20 Sep '05

20 Sep '05

No doubt I am making some stupid mistake in the log file, but I cannot get vsftp to create a log file showing the transfers. Here is my conf file: # Example config file /etc/vsftpd/vsftpd.conf # # The default compiled in settings are fairly paranoid. This sample file # loosens things up a bit, to make the ftp daemon more usable. # Please see vsftpd.conf.5 for all compiled in defaults. # # READ THIS: This example file is NOT an exhaustive list of vsftpd options. # Please read the vsftpd.conf.5 manual page to get a full idea of vsftpd's # capabilities. # # Allow anonymous FTP? (Beware - allowed by default if you comment this out). anonymous_enable=NO # # Uncomment this to allow local users to log in. local_enable=YES # # Uncomment this to enable any form of FTP write command. write_enable=YES # # Default umask for local users is 077. You may wish to change this to 022, # if your users expect that (022 is used by most other ftpd's) local_umask=022 # # Uncomment this to allow the anonymous FTP user to upload files. This only # has an effect if the above global write enable is activated. Also, you will # obviously need to create a directory writable by the FTP user. #anon_upload_enable=YES # # Uncomment this if you want the anonymous FTP user to be able to create # new directories. #anon_mkdir_write_enable=YES # # Activate directory messages - messages given to remote users when they # go into a certain directory. dirmessage_enable=YES # # Activate logging of uploads/downloads. xferlog_enable=YES # # Make sure PORT transfer connections originate from port 20 (ftp-data). connect_from_port_20=YES # # If you want, you can arrange for uploaded anonymous files to be owned by # a different user. Note! Using "root" for uploaded files is not # recommended! #chown_uploads=YES #chown_username=whoever # # You may override where the log file goes if you like. The default is shown # below. xferlog_file=/var/log/vsftpd.log # # If you want, you can have your log file in standard ftpd xferlog format xferlog_std_format=YES # # You may change the default value for timing out an idle session. #idle_session_timeout=600 # # You may change the default value for timing out a data connection. #data_connection_timeout=120 # # It is recommended that you define on your system a unique user which the # ftp server can use as a totally isolated and unprivileged user. #nopriv_user=ftpsecure # # Enable this and the server will recognise asynchronous ABOR requests. Not # recommended for security (the code is non-trivial). Not enabling it, # however, may confuse older FTP clients. #async_abor_enable=YES # # By default the server will pretend to allow ASCII mode but in fact ignore # the request. Turn on the below options to have the server actually do ASCII # mangling on files when in ASCII mode. # Beware that turning on ascii_download_enable enables malicious remote parties # to consume your I/O resources, by issuing the command "SIZE /big/file" in # ASCII mode. # These ASCII options are split into upload and download because you may wish # to enable ASCII uploads (to prevent uploaded scripts etc. from breaking), # without the DoS risk of SIZE and ASCII downloads. ASCII mangling should be # on the client anyway.. #ascii_upload_enable=YES #ascii_download_enable=YES # # You may fully customise the login banner string: #ftpd_banner=Welcome to blah FTP service. # # You may specify a file of disallowed anonymous e-mail addresses. Apparently # useful for combatting certain DoS attacks. #deny_email_enable=YES # (default follows) #banned_email_file=/etc/vsftpd.banned_emails # # You may specify an explicit list of local users to chroot() to their home # directory. If chroot_local_user is YES, then this list becomes a list of # users to NOT chroot(). #chroot_list_enable=YES # (default follows) #chroot_list_file=/etc/vsftpd.chroot_list # # You may activate the "-R" option to the builtin ls. This is disabled by # default to avoid remote users being able to cause excessive I/O on large # sites. However, some broken FTP clients such as "ncftp" and "mirror" assume # the presence of the "-R" option, so there is a strong case for enabling it. #ls_recurse_enable=YES pam_service_name=vsftpd userlist_enable=YES chroot_local_user=YES #enable for standalone mode listen=YES tcp_wrappers=YES -- Ariste Software 2200 D Street Ext Petaluma, CA 94952 (707) 773-4523

3 5

x86_64 rpms
by John Logsdon 20 Sep '05

20 Sep '05

I have just loaded up CentOS4.1 on a PE1850 with twin Intel x86_64's. When I came to clean out those packages I didn't want (because some always creep in however careful you are), apart from those with dependencies, I notice a lot of cases where there are two packages of the same name installed - one clearly an x86 package and one an x86_64 package. eg apr Is this intentional and if it is, how do I remove using rpm -e those packages with duplicate modules without removing those that will break dependencies? TIA John John Logsdon "Try to make things as simple Quantex Research Ltd, Manchester UK as possible but not simpler" j.logsdon(a)quantex-research.com a.einstein(a)relativity.org +44(0)161 445 4951/G:+44(0)7717758675 www.quantex-research.com

3 2

Re: Promise SATA support
by Admin 20 Sep '05

20 Sep '05

Hello, On Sat, 17 Sep 2005 15:28:18 +0200, Admin/Jan Erik wrote: > I have a Promise SATA 300 TX ( NOT raid ) that do have RHEL4 driver, but > this driver doesn't work with CentOS4 I have a Promise SATAII 150 TX4 controller which I belive is somewhat similar to your controller. And judging from http://www.promise.com/support/download/download2_eng.asp?productID=129&cate gory=all&os=100 the two controllers use the same driver. My controller wasn't supported by the first CentOS 4 (4.0) release, but with CentOS 4.1, things work fine out of the box, with no need to try to install special vendor drivers. By the way: The driver (kernel module) is called "sata_promise" on my system. Have you tried simply forgetting about the vendor's driver files, and just install CentOS 4.1, perhaps telling it to use the "sata_promise" driver, if manual intervention is needed? -- Greetings from Troels Arvin Hello Troels Arvin Maybe the promise SATA driver that is in CentOS is obsolete? Because it dosen't recognise my SATA card at all Here is theoutput from lspci: # lspci 00:00.0 Host bridge: VIA Technologies, Inc. VT8366/A/7 [Apollo KT266/A/333] 00:01.0 PCI bridge: VIA Technologies, Inc. VT8366/A/7 [Apollo KT266/A/333 AGP] 00:07.0 Unknown mass storage controller: Promise Technology, Inc.: Unknown device 3d17 (rev 02) 00:09.0 Ethernet controller: Intel Corp. 82541PI Gigabit Ethernet Controller (rev 05) 00:0b.0 USB Controller: NEC Corporation USB (rev 41) 00:0b.1 USB Controller: NEC Corporation USB (rev 41) 00:0b.2 USB Controller: NEC Corporation USB 2.0 (rev 02) 00:11.0 ISA bridge: VIA Technologies, Inc. VT8233 PCI to ISA Bridge 00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) 00:11.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 1b) 00:11.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 1b) 00:11.4 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 1b) 01:00.0 VGA compatible controller: S3 Inc. Trio 64 3D (rev 01) As you can see on line 3 there is Unknown mass storage controller. It's recognised as Promise, but that's all Any clues? B.T.W I have emailed support at promise and here is their reply: Hi The SATA300 TX card dose not support Kernel 2.6 only Kernel 2.4. Regards Jan Erik

1 0

install not recognizing RHEL
by Craig White 20 Sep '05

20 Sep '05

I am trying to install ArcServe 11 for Linux [root@linserv1 cdrom]# ./install Much license gibberish removed... ENTER NO (N) TO HALT THE INSTALLATION PROCESS. Please enter your choice:[Y|N] (default: N)Y Do you want to view the installation notes? (y/n):(default: y) N Cannot identify your Linux distribution or it is not yet supported. [root@linserv1 cdrom]# cat /etc/issue Red Hat Enterprise Linux ES release 3 (Taroon Update 5) Kernel \r on an \m [root@linserv1 cdrom]# cat /etc/issue.net Red Hat Enterprise Linux ES release 3 (Taroon Update 5) Kernel \r on an \m [root@linserv1 cdrom]# uname -a Linux linserv1.mullenpr.com 2.4.21-32.0.1.ELsmp #1 SMP Wed May 25 14:26:33 EDT 2005 i686 i686 i386 GNU/Linux Any suggestions? (this is a centOS 3.5 system)... # cat /etc/issue.bak CentOS release 3.5 (Final) Kernel \r on an \m Craig -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

5 9

pam and sasl2-sample-server failure
by scott.list 20 Sep '05

20 Sep '05

I'm setting up a postfix server using "The Book of Postfix". In ch 15 there is a section on testing saslauthd which I can't get to work. I can get it to work using shadow password authentication, but it fails on pam. I don't kow squat about troubleshooting pam. Any PAM wizzes out there that can help? I saw a unrelated post talking about something needing to be in the pam sasl group. Had no idea what that meant. sasl ins't a user, or group. I setup and try saslauthd -m /var/run/saslauthd -a pam -d sasl2-sample-server -s rcmd -p 8000 sasl2-sample-client -s rcmd -p 8000 -m LOGIN 127.0.0.1 If I set "-a shadow" it works. So I assume I have saslauthd working at least. But, if I set "-a pam" as listed above, it fails I believe it may be a PAM issue, could be sasl, but I'm hoping maybe someone will see the easy answer. I have in /etc/pam.d/smtp #%PAM-1.0 auth required pam_stack.so service=system-auth account required pam_stack.so service=system-auth Also: # saslauthd -v saslauthd 2.1.19 authentication mechanisms: getpwent kerberos5 pam rimap shadow ldap And /usr/lib/sasl2/smtpd.conf (also linked to sample.conf) # cat smtpd.conf loglevel: 7 pwcheck_method: saslauthd mech_list: PLAIN LOGIN Here are the results of a failed attempt: ------------------------------------- # saslauthd -m /var/run/saslauthd -a pam -d saslauthd[3176] :main : num_procs : 5 saslauthd[3176] :main : mech_option: NULL saslauthd[3176] :main : run_path : /var/run/saslauthd saslauthd[3176] :main : auth_mech : pam saslauthd[3176] :ipc_init : using accept lock file: /var/run/saslauthd/mux.accept saslauthd[3176] :detach_tty : master pid is: 0 saslauthd[3176] :ipc_init : listening on socket: /var/run/saslauthd/mux saslauthd[3176] :main : using process model saslauthd[3177] :get_accept_lock : acquired accept lock saslauthd[3176] :have_baby : forked child: 3177 saslauthd[3176] :have_baby : forked child: 3178 saslauthd[3176] :have_baby : forked child: 3179 saslauthd[3176] :have_baby : forked child: 3180 saslauthd[3177] :rel_accept_lock : released accept lock saslauthd[3177] :do_auth : auth failure: [user=testuser] [service=rcmd] [realm=] [mech=pam] [reason=PAM auth error] # sasl2-sample-server -s rcmd -p 8000 trying 2, 1, 6 trying 10, 1, 6 socket: Address family not supported by protocol accepted new connection send: {11} PLAIN LOGIN recv: {5} LOGIN recv: {1} N send: {9} Username: recv: {7} testuser send: {9} Password: recv: {6} xxxxxx performing SASL negotiation: authentication failureclosing connection # sasl2-sample-client -s rcmd -p 8000 -m LOGIN 127.0.0.1 receiving capability list... recv: {11} PLAIN LOGIN PLAIN LOGIN send: {5} LOGIN send: {1} N recv: {9} Username: please enter an authentication id: testuser Password: send: {7} testuser recv: {9} Password: send: {6} xxxxxx authentication failed closing connection -------------- # From syslog: Sep 19 09:33:45 tn1 saslauthd[3209]: main : num_procs : 5 Sep 19 09:33:45 tn1 saslauthd[3209]: main : mech_option: NULL Sep 19 09:33:45 tn1 saslauthd[3209]: main : run_path : /var/run/saslauthd Sep 19 09:33:45 tn1 saslauthd[3209]: main : auth_mech : pam Sep 19 09:33:45 tn1 saslauthd[3209]: ipc_init : using accept lock file: /var/run/saslauthd/mux.accept Sep 19 09:33:45 tn1 saslauthd[3209]: detach_tty : master pid is: 0 Sep 19 09:33:45 tn1 saslauthd[3209]: ipc_init : listening on socket: /var/run/saslauthd/mux Sep 19 09:33:45 tn1 saslauthd[3209]: main : using process model Sep 19 09:33:45 tn1 saslauthd[3210]: get_accept_lock : acquired accept lock Sep 19 09:33:45 tn1 saslauthd[3209]: have_baby : forked child: 3210 Sep 19 09:33:45 tn1 saslauthd[3209]: have_baby : forked child: 3211 Sep 19 09:33:45 tn1 saslauthd[3209]: have_baby : forked child: 3212 Sep 19 09:33:45 tn1 saslauthd[3209]: have_baby : forked child: 3213 Sep 19 09:34:03 tn1 saslauthd[3210]: rel_accept_lock : released accept lock Sep 19 09:34:03 tn1 saslauthd[3210]: DEBUG: auth_pam: pam_authenticate failed: Authentication failure Sep 19 09:34:03 tn1 saslauthd[3210]: do_auth : auth failure: [user=testuser] [service=rcmd] [realm=] [mech=pam] [reason=PAM auth error] Sep 19 09:34:03 tn1 saslauthd[3210]: get_accept_lock : acquired accept lock

3 2

Way to tell if monitor is on or off???
by Jerry Geis 20 Sep '05

20 Sep '05

I am looking for a way to tell if the monitor is on or off? xset q - seems to only work if DPMS turns off the monitor. If I or someone actually turns off the monitor xset q still shows on. If I do xset dpms force off ; sleep 5; xset q the monitor shows off. So is there a way to tell if the monitor is actually on or off? Thanks, Jerry

1 0

Apache error
by HaraldFinnås 19 Sep '05

19 Sep '05

Anyone seen these errors from apache before? *** glibc detected *** free(): invalid next size (fast): 0x0a2e4320 *** *** glibc detected *** free(): invalid next size (fast): 0x0a2e2068 *** [Mon Sep 19 13:29:48 2005] [notice] child pid 334 exit signal Aborted (6) [Mon Sep 19 13:29:48 2005] [notice] child pid 335 exit signal Aborted (6) This is CentOS 4.1 with all updates applied. Happens when trying to log on to the latest egroupware from cvs (from head). Regards, Harald

1 0

Installing Java on X86_64 CentOS 4.1
by Kai 19 Sep '05

19 Sep '05

I have some problems installing java support to my browser (firefox). This support I installed with no problem when running the 32 bit version on the same machine, but now I can't find the plugin. I running on S754 - AMD XP3000 this is the file i download: jre-1_5_0_04-linux-amd64.bin And I am following the installation instructions from this link: http://java.com/en/download/help/5000010500.xml Everything seems to install perfectly, but the libjavaplugin_oji.so is not included, I can't find. Maybe there is an other file to link up to? If someone has the answer, please! kai

10 14

Policy based routing
by Hugo Perez Casanova 19 Sep '05

19 Sep '05

Hi. Any one doing policy based routing in Centos 4.1? RHEL 3.4 does ok, but same configuration in CentOS 4.1 does not work. Is there something missing in kernel 2.6? Regards.

1 0

[OT] DirectDial.com ....
by William A. Mahaffey III 19 Sep '05

19 Sep '05

.... does anyone onlist have any 1st-hand experience (good or bad) w/ DirectDial.com for procuring computer components ? Thanks in advance :-). I am interested in them as a potential source for parts to build an Opteron box running Linux, probably CentOS, to bring this slightly on topic .... -- William A. Mahaffey III --------------------------------------------------------------------- Remember, ignorance is bliss, but willful ignorance is LIBERALISM !!!!

6 8

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss