Hi Melissa Unfortunately we cannot support you if you're using your own filesystem/kernel/other. At best I can point you in a direction but you will have to debug it yourself. The /etc/init.d/tcpborphserver file is responsible for starting tcpborphserver using the standard Debian init script infrastructure. I don't know how you managed to get it to work before without this file. You should be able to just copy it from a known-good filesystem, paying attention to permissions or otherwise create your own one.
Jason On 04 Oct 2010, at 20:00, Soriano, Melissa (335J) wrote: > Hi Henry, > > Thanks for your e-mail. My problem is that the latest version of > tcpborphserver is not coming up automatically on boot-up. I do not have > /etc/init.d/tcpborphserver. > > I compiled the kernel myself. I am using my own filesystem, but it is the > same filesystem as I was using before I upgraded the kernel. > > I did not customize startup to point to /borph when I compiled the kernel. > How can I do this? > > I am using the 2.6.25-svn3327 kernel. I linked to the latest tcpborphserver > and sym linked to it in /usr/local/sbin/ as Jason recommended. > > o...@roach1:~$ ls -lart /usr/local/sbin > total 272 > drwxrwsr-x 10 root staff 4096 Jan 22 2009 .. > -rwxr-xr-x 1 root staff 266102 Oct 4 17:49 > tcpborphserver2-2010-08-27-r3304-signfix > lrwxrwxrwx 1 root staff 56 Oct 4 17:50 tcpborphserver2 -> > /usr/local/sbin/tcpborphserver2-2010-08-27-r3304-signfix > drwxrwsr-x 2 root staff 4096 Oct 4 17:50 . > o...@roach1:~$ > > Thank you, > Melissa > >> -----Original Message----- >> From: Henry Chen [mailto:[email protected]] >> Sent: Tuesday, September 28, 2010 11:11 AM >> To: Soriano, Melissa (335J) >> Cc: Wang, Duo (335J); [email protected] >> Subject: Re: [casper] tcpborphserver version, ?wordwrite always returns >> zero >> >> Hi Melissa, >> >> I've been playing around a bit with the new -signfix version of >> tcpborphserver. The patch works for me if I do >> >> /etc/init.d/tcpborphserver stop >> >> then replace tcpborphserver2 in /usr/local/sbin and reboot. Then >> the new version of the server comes up properly at boot. Did you >> have customized startup to point to /borph when you compiled the >> kernel? >> >> Thanks, >> Henry >> >> On 9/28/2010 9:24 AM, Soriano, Melissa (335J) wrote: >>> Dear Jason, >>> >>> Thank you for the LatestVersions wiki page. >>> >>>> The latest binary in SVN is from 2009 >>>> >> (http://casper.berkeley.edu/svn/trunk/roach/sw/binaries/linux/uImage- >>>> jiffy-20091110). Did you recompile the kernel yourself? >>> >>> Yes, I checked out the roach/sw/linux directory and recompiled the >> kernel myself. I needed the kernel source to compile my kernel modules >> against. >>> >>> o...@roach1:~$ uname -a >>> Linux roach1 2.6.25-svn3327 #2 Tue Sep 28 09:05:39 PDT 2010 ppc >> GNU/Linux >>> >>>>> We are using tcpborphserver 0.2110. Is this the latest version? >>>> No, latest version is >>>> >> http://casper.berkeley.edu/svn/trunk/roach/sw/binaries/tcpborphserver/t >>>> cpborphserver2-2010-08-27-r3304-signfix >>>> You could try that one. I don't have any problems using other >> commands >>>> or running tut2 (the 10GbE tutorial) using the recommended >> versions... >>> >>> I picked up the version above and copied it to the /borph directory, >> then rebooted the board. However, when I look at the process list, I >> don't see tcpborphserver.. >>> >>> o...@roach1:~$ ps -ef >>> UID PID PPID C STIME TTY TIME CMD >>> root 1 0 2 16:20 ? 00:00:00 init [2] >>> root 2 0 0 16:20 ? 00:00:00 [kthreadd] >>> root 3 2 0 16:20 ? 00:00:00 [ksoftirqd/0] >>> root 4 2 0 16:20 ? 00:00:00 [events/0] >>> root 5 2 0 16:20 ? 00:00:00 [khelper] >>> root 48 2 0 16:20 ? 00:00:00 [kblockd/0] >>> root 58 2 0 16:20 ? 00:00:00 [khubd] >>> root 65 2 0 16:20 ? 00:00:00 [kmmcd] >>> root 85 2 0 16:20 ? 00:00:00 [bkexecd] >>> root 86 2 0 16:20 ? 00:00:00 [pdflush] >>> root 87 2 0 16:20 ? 00:00:00 [pdflush] >>> root 88 2 0 16:20 ? 00:00:00 [kswapd0] >>> root 89 2 0 16:20 ? 00:00:00 [aio/0] >>> root 123 2 0 16:20 ? 00:00:00 [mtdblockd] >>> root 161 2 0 16:20 ? 00:00:00 [krmond] >>> root 167 2 0 16:20 ? 00:00:00 [rpciod/0] >>> daemon 387 1 0 16:21 ? 00:00:00 /sbin/portmap >>> statd 394 1 0 16:21 ? 00:00:00 /sbin/rpc.statd >>> root 402 2 0 16:21 ? 00:00:00 [lockd] >>> root 496 1 0 16:21 ? 00:00:00 /sbin/syslogd >>> root 505 1 0 16:21 ? 00:00:00 /sbin/klogd -x >>> root 532 1 0 16:21 ? 00:00:00 /usr/sbin/inetd >>> ntp 545 1 0 16:21 ? 00:00:00 /usr/sbin/ntpd -p >> /var/run/ntpd.pid -u 100:102 -g >>> root 567 1 0 16:21 ? 00:00:00 /usr/sbin/cron >>> root 626 1 0 16:21 ttyS0 00:00:00 /sbin/getty -L ttyS0 >> 115200 vt100 >>> telnetd 627 532 1 16:21 ? 00:00:00 in.telnetd: psdg5.lab >>> root 629 627 2 16:21 pts/0 00:00:00 login -h psdg5.lab -p >>> ops 630 629 1 16:21 pts/0 00:00:00 -sh >>> ops 634 630 0 16:21 pts/0 00:00:00 ps -ef >>> >>> o...@roach1:~$ ls -lart /borph >>> total 1108 >>> -rwxr-xr-x 1 root root 33 Jul 16 2009 rc >>> -rwxr-xr-x 1 root root 577036 Jul 17 2009 tcpborphserver.orig >>> drwxr-xr-x 29 root root 4096 Aug 3 04:12 .. >>> -rwxr--r-- 1 root root 266102 Sep 28 16:19 tcpborphserver2-2010-08- >> 27-r3304-signfix >>> drwxr-xr-x 2 root root 4096 Sep 28 16:19 . >>> -rwxr-xr-x 1 root root 266102 Sep 28 16:20 tcpborphserver >>> >>> Why would tcpborphserver fail to launch on start-up? >>> >>> Thank you for your help. >>> >>> Regards, >>> Melissa >>> >>> >
