Re: FreeBSD 7.0-BETA2 Available
On Sunday 04 November 2007, Ken Smith wrote: > The 7.0-BETA2 builds have completed and are on many of the FreeBSD > mirror sites. If you want to update an existing machine using cvsup use > RELENG_7 as the branch tag. Instructions on using FreeBSD Update to > perform a binary upgrade from FreeBSD 6.x to 7.0-BETA2 will be provided > via the freebsd-stable list when available. These release announcements seem to be shorter and shorter with every release. Is there a changelog to see what has changed since BETA1? If so, would you please consider linking to it in future announcements? Thanks a lot :-) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Rotating web server logs without restarting Apache
On Saturday 26 November 2005 08:38, Dan O'Connor wrote: > In /etc/newsyslog.conf: > > /var/log/httpd-access.log 644 4 100 * J > /var/run/httpd.pid 30 > /var/log/httpd-error.log 644 4 100 * J > /var/run/httpd.pid 30 > > This will signal apache to do a graceful restart following a log > rotation... Great, thanks a lot. I'll try this and report back if I still have a problem. Ladislav ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Rotating web server logs without restarting Apache
Hi, Every time my httpd-access.log file is rotated I need to restart Apache, otherwise it won't write into the new httpd-access.log file. Is there a way for Apache (version 2.0.55 on FreeBSD 6.0) to write to the new log file without the need to restart it? I restart it routinely from a cron job, but occasionally Apache fails to restart (or more precisely, if fails to shutdown completely before it is told to come up again). Thank you very much for your help. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Time zone change confuses cron
On Tuesday 29 March 2005 08:08, you wrote: > To my knowledge, timezone is taken from the environment when a process > starts. If you want cron to honor the new timezone, restart cron, or > set the TZ explicitly in the relevant crontab. Ah, thank you very much. It's amazing that sometimes simple things like that complete elude one's brain :-) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Time zone change confuses cron
Hi, I've just changed the system time zone from local time to UTC by copying /usr/share/zoneinfo/Etc/UTC to /etc/localtime. To my dismay, I found that crontab (both /etc/crontab and user-level crontab) completely ignores the change and continues executing scripts according to the old time. What am I doing wrong? Thanks a lot for your help :-) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: PHP vulnerability and portupgrade
On Wednesday 22 December 2004 09:06, Mark Andrews wrote: > > Hello, > > > > Due to the recently discovered vulnerability in PHP versions older than > > 4.3.10 and 5.0.3, I decided to take a look at portupgrade to see if it > > is a good way to keep the ports collection up-to-date with respect to > > security issues. I ran cvsup on the security branch (tag=RELENG_5_3), > > then portsdb -Uu. However, portupgrade didn't find any ports that > > needed an upgrade. > > > > Am I doing something wrong or is portupgrade not the best tool to keep > > up with security advisories in ports? > > cvsup of ports does not use tag=RELENG_5_3. > > e.g. > *default host=cvsup.FreeBSD.org > *default base=/usr > *default prefix=/usr > *default release=cvs > *default delete use-rel-suffix > *default tag=. > ports-all > > Use portaudit to track security issues in ports. Thanks a lot for your reply. If I understand things correctly, I need to maintain two cvsup files - one that tracks security issues in the base FreeBSD 5.3 system (tag=RELENG_5_3, src-all) and one for the ports collection (tag=. , ports-all). Then every time I receive a FreeBSD security advisory I run cvsup on the former, and every time portaudit tells me about a new security issue in the ports collection, I run cvsup on the latter, then use portupgrade to upgrade vulnerable ports. Is this correct? I went through the security chapter of the FreeBSD handbook, but I found it disappointing that it doesn't explain how to keep a FreeBSD system up-to-date of security issues. Also, "The Complete FreeBSD" book by Greg Lehey doesn't even mention the existence of portaudit. Thanks again :-) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
PHP vulnerability and portupgrade
Hello, Due to the recently discovered vulnerability in PHP versions older than 4.3.10 and 5.0.3, I decided to take a look at portupgrade to see if it is a good way to keep the ports collection up-to-date with respect to security issues. I ran cvsup on the security branch (tag=RELENG_5_3), then portsdb -Uu. However, portupgrade didn't find any ports that needed an upgrade. Am I doing something wrong or is portupgrade not the best tool to keep up with security advisories in ports? Thank you for your help :-) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
