Re: Let a daemon process print a message
syslog() with the proper facility is probably the best way to do this. Another possibility is opening /dev/console, but I think that will aquire a controlling terminal. On Mon, 13 Sep 1999, Zhihui Zhang wrote: Can anyone tell me how to let a daemon process print a message to the console? Adding printf() does not work (I wonder if a daemon process has been cut of relationship with stdout). Thanks for any help. -- Zhihui Zhang. Please visit http://www.freebsd.org -- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Let a daemon process print a message
syslog() with the proper facility is probably the best way to do this. Another possibility is opening /dev/console, but I think that will aquire a controlling terminal. On Mon, 13 Sep 1999, Zhihui Zhang wrote: Can anyone tell me how to let a daemon process print a message to the console? Adding printf() does not work (I wonder if a daemon process has been cut of relationship with stdout). Thanks for any help. -- Zhihui Zhang. Please visit http://www.freebsd.org -- To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: A Challenge
I have about 5 years experance with FreeBSD. I am running it at home connected to a cable modem. My server is fairly secure from the outside. I periodically read and act upon the builins from CERT, etc. The box is just going to be running NATD and IPFW, maybe DHCLIENT. Some suggestions: dump natd/ipfw, use ipf and ipnat instead so you can use keepstate, which is very close to a stateful packet filter). subscribe to bugtraq (http://www.securityfocus.com, it's somewhere in there). dont install X, or any other services not absolutely necessary for the operation of the firewall. Administration should be (ideally) done at console (no x!) remove privledges of all executables that you dont require. Enable them on a case by case basis, if they need to be used for the operation of the firewall. Mr. NT is been told he can try and break-in, crash what ever this box from the internet side. I am asking for links, pointer to make sure this is configured as secure/solid as possible. I will be installing 3.3-STABLE over this weekend (9/11/1999). I really want to make sure we win. Might want to write chroot() wrappers around all network daemons too. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: A Challenge
I have about 5 years experance with FreeBSD. I am running it at home connected to a cable modem. My server is fairly secure from the outside. I periodically read and act upon the builins from CERT, etc. The box is just going to be running NATD and IPFW, maybe DHCLIENT. Some suggestions: dump natd/ipfw, use ipf and ipnat instead so you can use keepstate, which is very close to a stateful packet filter). subscribe to bugtraq (http://www.securityfocus.com, it's somewhere in there). dont install X, or any other services not absolutely necessary for the operation of the firewall. Administration should be (ideally) done at console (no x!) remove privledges of all executables that you dont require. Enable them on a case by case basis, if they need to be used for the operation of the firewall. Mr. NT is been told he can try and break-in, crash what ever this box from the internet side. I am asking for links, pointer to make sure this is configured as secure/solid as possible. I will be installing 3.3-STABLE over this weekend (9/11/1999). I really want to make sure we win. Might want to write chroot() wrappers around all network daemons too. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
