tcp services (ssh,ftp) does not work

dear all, i have put sshd_enable="YES" and inetd_enable="YES" in /etc/rc.conf. netstat -an also shows that the port numbers 21 and 22 are in listen state ftp is uncommented in /etc/inetd.conf but still the ssh/ftp services does not work. when i ftp from another computer the netstat shows conne

monitoring resident memory of a process

I am trying to monitor the resident memory size of some apache processes to find out what the memory footprint is like. I was planning on using the perl Proc::ProcessTable module, but it seems to be lacking information: uid: 0 gid: 0 pid: 78297 ppid: 78296 pgrp: 78297 sess: 78297 flags: sldr utime

Re: monitoring resident memory of a process

From: "grover mitchell" <[EMAIL PROTECTED]> I am trying to monitor the resident memory size of some apache processes to find out what the memory footprint is like. I was planning on using the perl Proc::ProcessTable module, but it seems to be lacking information: How about 'ps v'? David __

Re: tcp services (ssh,ftp) does not work

At 02:07 AM 10/30/2005 -0800, kamal kc wrote: | dear all, | | i have put sshd_enable="YES" | and inetd_enable="YES" | in /etc/rc.conf. | | netstat -an also shows that the port numbers | 21 and 22 are in listen state | | ftp is uncommented in /etc/inetd.conf | | but still the ssh/ftp services do

ext2 large_file

I recently tried to use ext2 on FreeBSD but have decided not to when I saw that the support for large files is missing (and went with msdosfs instead). Now I accidentaly noticed that large_file support is present in latest NetBSD (and maybe OpenBSD). Is anyone interested in porting the support

signal handling in child process.

hello, i have a daemon program and installed a signal_handler() function for it. from signal_handler: case SIGCHLD: if ((wait(&status)) == -1) return; if (WIFSIGNALED(status)) return; if (WIFSTOPPED(status)) return; if (WIFEXITED(status)) return; break; in child process i am doing a

Re: tcp services (ssh,ftp) does not work

For future reference, you should not cross post to FreeBSD lists. If you are unsure what the best list will be, start with freebsd-questions. Good luck, Doug -- This .signature sanitized for your protection ___ freebsd-hackers@freebsd.org mailin