Outstanding issues

[Carter Bullard]

Well, the problem is that argus cannot in its strategies assume  
anything other
than a vanilla unix/linux machine underneath it.  So we can't rely on  
links or
named pipes existing in the chroot'd directory.  The syslog stuff is  
doable, I
just have to open the log in the argus initialization, and just not  
close it.
This is not a problem.    There will be other stuff to worry about,  
but I have
enough to start doing some implementation work soon.

Maybe before the end of the week.

Carter


On Sep 25, 2006, at 10:13 PM, Darren Spruell wrote:

> On 9/25/06, Carter Bullard <carter at qosient.com> wrote:
>> I'll have to have delayed opening of some things, but if the notion
>> is that we're just controlling output file generation, I maybe  
>> able to
>> do this in a short period of time.
>>
>> Seems like we'll have to change how we use syslog, as we current
>> call openlog() and closelog() in each ArgusLog() call, and that won't
>> work if we're chroot()'d.
>
> Is this trouble remedied by having syslogd create a log socket in  
> the chroot?
>
> -- 
> Darren Spruell
> phatbuckett at gmail.com
>


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist1.pair.net/pipermail/argus/attachments/20060925/3e280d65/attachment.html>