Hi, James, > James Walker writes: > >> /usr/bin/64/snort Uncommitted 64-bit Command >> > > What's this about? What does the utility do that actually requires > 64-bit operation? (Does it read from kernel memory directly?) > From functions points of view, there is no difference between 32-bit and 64-bit "snort" binaries. 64-bit snort is an optional choice when building the binary. And if you really concern about it, I can remove 64-bit part. Please tell me your idea. > Is snort ordinarily used in daemon mode? If so, shouldn't there be an > SMF configuration for it? Otherwise, users are forced to roll their > own, and the project seems incomplete. > I finished the SMF manifest in /var/svc/manifest/network/snort.xml;
And the related start script is "/lib/svc/method/snortd", it only contains "start" option. And when "enable" the service, it will call "/usr/bin/snort -d -D" to start the daemon. Please see the attachment. Through testing on my SPARC and X86 OpenSolaris 0906 machines, the SMF manifest and snortd script could work well. Thanks Jason -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: snortd URL: <http://mail.opensolaris.org/pipermail/opensolaris-arc/attachments/20090504/412037b9/attachment.ksh>
