Quote:
Originally Posted by ultranothing
1- how can start,stop.restart services in openbsd(like squid,ssh,network,...) ??
|
Built-in services are started by rc(8) environment variables. The default settings are found in /etc/rc.conf, and the admin should normally make local changes to these variables in /etc/rc.conf.local. See rc.conf(5) for more information.
3rd party packages are started by scripts the admin writes in /etc/rc.local. See rc(8), again.
The network is started by rc(8). The admin may restart the entire network or an individual NIC through:
# sh /etc/netstart [nic]
Please see netstart(8), and all of FAQ 6.
For your 3rd party packages, the admin may manually stop/start daemons, or, if the application does not come with management scripts, the admin may write his/her own.
Quote:
2- how we can use openbsd as cache , bandwidth controller ,,after installlation delay_pool not supported ?????? what i have to do ??
|
Regarding bandwidth: I've already answered that question in your first thread:
http://www.daemonforums.org/showthre...3652#post26188
The bandwidth tool is OpenBSD's Packet Filter, PF. I instructed you to read the PF Users Guide, which is part of the OpenBSD FAQ. Please read it.
Regarding cache: what kind? If HTTP, the admin typically uses Squid, which is a 3rd party package, and one you already mentioned. If you intend a cache for something other than HTTP, please restate your question.
Quote:
3- my new server has 4 HDD SCSI and i want to use as i said for cache-proxy ,.... . i want to use all 4 HDDs also use RAID but it is only to use one HDD (sd0,ds1,sd2,sd3) and it is only sd0 ,, it is maybe to use all or no and how ????
|
The current answer is RAIDframe. A newer technology, Softraid, is still in development and may not be suitable for production -- the only redundancy configuration is RAID1, and after a drive failure, the array must be backed up and then restored, it cannot reestablish a mirror. RAIDframe is a fully functional RAID 0/1/3/5 solution, but it requires a custom kernel. RAIDframe is described in FAQ 14, and custom kernels are described in FAQ 5. Read both, very carefully.