On Sat, 2007-01-20 at 23:01 +0100, Daniel Pielmeier wrote:
> > The only last thing I could suggest is running lsof to see what files
> > are being accessed when you start the net.eth1 script.
> 
> I tried lsof, but is there a possibility to run it constantly or for a
> specified time to catch the complete progress of the script, like the
> top command  to monitor all files which are used by this process. As
> far as i can see lsof list only the current processes and the files
> used and then it stops.

don't know :) someone else will have to help you there...

> > a better option would be `emerge --noconfmem <package>`, which
> > esentially re-does all your conf files.
> 
> I tried this also but i can't figure out which files could be
> responsible for this

something like this should do it:

for i in `sudo find /etc -name ._cfg\*`; do tkdiff `echo $i | awk
'{ sub(/._cfg...._/,""); print }'` $i; done

replace tkdiff with your favourite.

> Additionally i tried this, running the init-script and then i applied
> this find command
> 
> find / -mount -cmin -1
> 
> which lists all the files which status has changed the last minute,
> but there are no files which could be the reason for the changing if
> the tables.
> I don't know if this command does what i want. I think it lists the
> files which are altered and which are accessed. Am i right here?

it will list files that have been accessed, only if you _don't_ have
noatime in /etc/fstab for that filesystem.  noatime says don't update
the time when the file is accessed (but not changed).  the default is
atime, but a lot of people use noatime for speed improvements.


> This gets a bit frustrating for me now i always have to reset my
> iptables manually after i start my internet connection. Is it possible
> that there is no real file causing this trouble?

There must be something, somewhere doing it.. Maybe you could join the
shorewall ml and see what they say?  As a workaround, you could add this
to /etc/conf.d/net:

 postup() {
    if [[ $1 == "eth1" ]] ; then
       /etc/init.d/iptables restart
    fi
 }

or something similar.  Not the ideal solution, but at least it would do
it automatically.

sorry I can't help any further :)
-- 
Iain Buchanan <iaindb at netspace dot net dot au>

Mollison's Bureaucracy Hypothesis:
        If an idea can survive a bureaucratic review and be implemented
        it wasn't worth doing.

-- 
gentoo-user@gentoo.org mailing list

Reply via email to