Well, I at least found the problem--whenever ezipupd loads, the permissions and ownership changes from this:
drwxr-xr-x 16 root root 0 Dec 5 22:15 . drwxr-xr-x 16 root root 0 Dec 5 22:15 .. drwxr-xr-x 2 root root 0 Dec 5 22:15 bin drwxr-xr-x 4 root root 0 Dec 4 21:03 boot drwxr-xr-x 3 root root 0 Dec 5 22:15 dev drwxr-xr-x 22 root root 0 Dec 5 22:15 etc drwxr-xr-x 2 root root 0 Dec 5 22:14 initrd drwxr-xr-x 5 root root 0 Dec 5 22:14 lib lrwxrwxrwx 1 root root 26 Dec 5 22:14 linuxrc -> var/lib/lrpkg/root.linuxrc drwxr-xr-x 2 root root 5.5k Dec 5 22:35 mnt drwxr-xr-x 2 root root 0 Dec 5 22:14 nfs -rw-r--r-- 1 root root 0 Nov 29 2001 null dr-xr-xr-x 26 root root 0 Dec 5 22:14 proc drwxr-x--- 2 root root 0 Dec 5 22:14 root drwxr-xr-x 2 root root 0 Dec 5 22:15 sbin drwxrwxrwt 4 root root 0 Dec 5 22:15 tmp drwxr-xr-x 7 root root 0 Dec 5 22:14 usr drwxr-xr-x 10 root root 0 Dec 5 22:15 var to this: drwx------ 16 501 501 0 May 19 2002 . drwx------ 16 501 501 0 May 19 2002 .. drwxr-xr-x 2 root root 0 Dec 5 00:07 bin drwxr-xr-x 4 root root 0 Dec 4 21:03 boot drwxr-xr-x 3 root root 0 Dec 5 06:42 dev drwxr-xr-x 22 501 501 0 Dec 5 21:56 etc drwxr-xr-x 2 root root 0 Dec 5 00:06 initrd drwxr-xr-x 5 root root 0 Dec 5 00:07 lib lrwxrwxrwx 1 root root 26 Dec 5 00:06 linuxrc -> var/lib/lrpkg/root.linuxrc drwxr-xr-x 2 root root 5.5k Dec 5 22:01 mnt drwxr-xr-x 2 root root 0 Dec 5 00:06 nfs -rw-r--r-- 1 root root 0 Nov 29 2001 null dr-xr-xr-x 27 root root 0 Dec 5 00:06 proc drwxr-x--- 2 root root 0 Dec 5 00:06 root drwxr-xr-x 2 root root 0 Dec 5 00:07 sbin drwxrwxrwt 5 root root 0 Dec 5 21:57 tmp drwxr-xr-x 7 501 501 0 May 19 2002 usr drwxr-xr-x 10 501 501 0 May 19 2002 var Note the 501's for the user and group. These must have been stored when ez-ipupd was packaged. By simply chmod 755 'ing and chown root.root 'ing the modified dirs, the weblet once again runs. By backing up the packages after fixing the permissions weblet functions normally after a restart. Is this a bug, by design, or something that is just not documented? Is my solution, changing the permissions by hand, valid? Or is there a better way to handle this? Thanks, Levi > Message: 11 > From: "levi" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Date: Wed, 4 Dec 2002 23:32:26 -0600 > Subject: [leaf-user] Problem with ez-ipupdate on Bering 1.0 Stable > > I have made the move to Bering, after using Redhat 7.2 and Shorewall for > quite some time. I have managed to get Bering set up and running quite > similar to my RH setup, providing firewall services, dhcp, PPTP, etc. I > have one problem though... > > I have a typical 2 nic setup, with a cable modem as my portal to the outside > world. I have a dynamic IP address (changes about every 1.5 weeks) and > would like to maintain my dyndns.org hostname when the IP changes. When I > load the LEAF module ez-ipupd.lrp, I loose connectivity to the weblet status > pages on Bering. I have tracked it down to this one package--without it, > everything works as expected. As soon as I install ezipupdate, inetd no > longer fires off the sh-httpd process, and subsequently, no longer > generating the weblet pages. I have looked through the files and > documentation for Bering and ez-ipupd and have come up with nothing thus > far. Can someone could point me in the right direction or tell me what I > am missing? > > > Thanks, > Levi ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ------------------------------------------------------------------------ leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
