[no description] https://git.osdyson.ru/mirror/pkgsrc/atom?h=pkgsrc_2008Q2 2006-04-08T05:02:59Z 2006-04-08T05:02:59Z jlam jlam 2006-04-08T05:02:59Z urn:sha1:016841ded538972e7f2685290588e257d07379c6 2005-05-02T20:33:57Z reed reed 2005-05-02T20:33:57Z urn:sha1:22c4e451098bcb1ffee496c70c2b37805278db1a And always is defined as share/examples/rc.d which was the default before. This rc.d scripts are not automatically added to PLISTs now also. So add to each corresponding PLIST as required. This was discussed on tech-pkg in late January and late April. Todo: remove the RCD_SCRIPTS_EXAMPLEDIR uses in MESSAGES and elsewhere and remove the RCD_SCRIPTS_EXAMPLEDIR itself. 2004-04-23T22:07:52Z reed reed 2004-04-23T22:07:52Z urn:sha1:cba182b47fc5b42f77862f4b5a18898200c81105 the RCD_SCRIPTS rc.d script(s) to the PLIST. This GENERATE_PLIST idea is part of Greg A. Woods' PR #22954. This helps when the RC_SCRIPTS are installed to a different ${RCD_SCRIPTS_EXAMPLEDIR}. (Later, the default RCD_SCRIPTS_EXAMPLEDIR will be changed to be more clear that they are the examples.) These patches also remove the etc/rc.d/ scripts from PLISTs (of packages that use RCD_SCRIPTS). (This also removes now unused references from openssh* makefiles. Note that qmail package has not been changed yet.) I have been doing automatic PLIST registration for RC_SCRIPTS for over a year. Not all of these packages have been tested, but many have been tested and used. Somethings maybe to do: - a few packages still manually install the rc.d scripts to hard-coded etc/rc.d. These need to be fixed. - maybe remove from mk/${OPSYS}.pkg.dist mtree specifications too. 2004-04-01T05:19:02Z xtraeme xtraeme 2004-04-01T05:19:02Z urn:sha1:69f26aeb58e446afff994ae61e236d8f256ddf46 Thy was designed to be as fast and lightweight as possible. For speed, she uses sendfile(), and does not fork. Among the features are name-based virtual hosts, userdir and directory index support; Range, If-Modified-Since, keep-alive, on-the-fly compression and of course, CGI, IPv6 and TLS support. Thy does not require (but can use) a configuration file to run.