Re: 8.0 rc.d scripts less verbose?
Dimitry Andric pisze:
Index: etc/rc.subr
===
--- etc/rc.subr (revision 196888)
+++ etc/rc.subr (working copy)
@@ -680,7 +680,7 @@ run_rc_command()
# setup the full command to run
#
- [ -z "${rc_quiet}" ] && echo "Starting ${name}."
+ echo "Starting ${name}."
if [ -n "$_chroot" ]; then
_doit="\
${_nice:+nice -n $_nice }\
Wouldn't it be easier to set rc_quiet to zero-length value, like
rc_quiet=""?
--
Cezary Morga
"Research is the process of going up alleys to see if they are blind."
(Marston Bates)
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 8.0 rc.d scripts less verbose?
On 2009-09-16 09:54, Cezary Morga wrote: > Wouldn't it be easier to set rc_quiet to zero-length value, like > rc_quiet=""? No, rc_quiet is not user-settable (at least not from /etc/rc.conf). ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: newsyslog can't execute command?
Ferdinand Goldmann wrote: > Have I overlooked something, or is it not possible with newsyslog to run a > certain command after log rotation? :-( That's correct. A simple workaround is to write a small shell script that stores its PID in a file, then runs in the background and waits for a signal. It's a hack, but it works. Basically, something like this will do: #!/bin/sh - echo $$ > /var/run/loghandler-foo.pid while :; do kill -STOP $$ ... do whatever you want with the log file ... done Make sure that shell script is run in the background during system boot. The newsyslog.conf entry should look like this: /var/log/foo.log 644 3 100 * B /var/run/loghandler-foo.pid 19 The important thing is the number "19" at the end, which will cause newsyslog to send SIGCONT to the shell script after it has rotated the log file. Alternatively you can also use the shell's built-in "trap" command to use different signals. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd "What is this talk of 'release'? We do not make software 'releases'. Our software 'escapes', leaving a bloody trail of designers and quality assurance people in its wake." ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
PATA disks/DVD not detected on ATI IXP 700 - cannot boot
Hi. I'm trying to upgrade a machine to a new motherboard (the ECS A790GXM-AD3 AM3 790GX) my FreeBSD 7-STABLE system (GENERIC kernel, compiled from source on 10 Sept 2009) reaches the point where it's going to mount the root file system and can't find the disk. It drops me into the manual specification of root file system menu, but there are no GEOM-managed disks to choose from. There's only one drive in the system, a PATA-connected drive that boots correctly under the old (and I do mean old, circa 2005) motherboard. Booting from an install/rescue CDROM on a PATA_connected drive proceeds about the same: boots but cannot find the CDROM to mount. SATA drives seem to be found correctly, but I don't have any with FreeBSD on them. The ATA controller reports itself as an ATI IXP 700. There's more info on the motherboard here: http://www.newegg.com/Product/Product.aspx?Item=N82E16813135236&nm_mc=TEMC-RMA-Approvel&cm_mmc=TEMC-RMA-Approvel-_-Content-_-text-_- I haven't tried to boot from a USB drive yet, because ATA has so rarely failed me in the past, but I'm happy to do whatever will help to provide more diagnostic info. (The machine is at home, so I won't be able to do much data-gathering until tonight.) Thanks for any help. -- Ted Faber http://www.isi.edu/~faber PGP: http://www.isi.edu/~faber/pubkeys.asc Unexpected attachment on this mail? See http://www.isi.edu/~faber/FAQ.html#SIG pgpsjCtVt974B.pgp Description: PGP signature
Re: 8.0 rc.d scripts less verbose?
First off, this discussion should actually have been on
freebsd-current@ until 8.0-RELEASE is done, but that's a minor issue.
Cezary Morga wrote:
> Dimitry Andric pisze:
>> Index: etc/rc.subr
>> ===
>> --- etc/rc.subr(revision 196888)
>> +++ etc/rc.subr(working copy)
>> @@ -680,7 +680,7 @@ run_rc_command()
>>
>> # setup the full command to run
>> #
>> -[ -z "${rc_quiet}" ] && echo "Starting ${name}."
>> +echo "Starting ${name}."
>> if [ -n "$_chroot" ]; then
>> _doit="\
>> ${_nice:+nice -n $_nice }\
>
> Wouldn't it be easier to set rc_quiet to zero-length value, like
> rc_quiet=""?
That actually would give off too much information because rc_quiet
suppresses error messages about scripts that don't currently have
_enable set to anything useful. That's arguably a bug, but it's a bug
that we've come to depend on.
The attached patch adds a knob you can set in rc.conf to see "Starting
foo" messages again. If people find this useful I'll be glad to commit
it. I'm also open to suggestions for a better name.
Doug
--
This .signature sanitized for your protection
--- /usr/src/etc/rc.subr2009-09-16 14:18:07.0 -0700
+++ rc.subr 2009-09-16 16:56:39.0 -0700
@@ -708,7 +708,7 @@
# setup the full command to run
#
- [ -z "${rc_quiet}" ] && echo "Starting ${name}."
+ [ -z "${rc_quiet}" -o -n "${rc_starting}" ] && echo
"Starting ${name}."
if [ -n "$_chroot" ]; then
_doit="\
${_nice:+nice -n $_nice }\
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 7.2-release/amd64: panic, spin lock held too long
Dan, is that machine equipped with Hyperthreading? Attilio Yes. It's an Intel Atom 330, which is a dualcore CPU with HT (4 cores visible in "top" as a result) Yes, mine is also Atom 330. I cannot test the patch because my machine is also in production now. But I have tested it with hyperthreading. powerd with HyperThreading -> spin lock hold too long powerd without HyperThreading -> no problem no powerd with/without HyperThreading -> no problem This blog article also describe the same situation: http://hype-o-thetic.com/2009/07/09/freenas-d945gclf2-configuration/ By the way, I found that the readings of coretemp don't significant change when I enabled powerd so that I doubt that powerd may not be very useful for Atom CPU? Thanks very much, C.C. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 6.2 sporadically locks up
2009/6/17 Ed Maste : > On Tue, Jun 16, 2009 at 07:03:34PM +0400, pluknet wrote: > >> As for allpcpu, I often see the picture, when one CPU runs the "irq17: >> bce1 aacu0" thread >> and another one runs arcconf. I wonder if that might be a source of >> bad locking or races, or.. >> The arcconf utility uses ioctl that goes into aac/aacu(4) internals. > > Do you see the same result w/ the in-tree aac(4) driver as opposed to > Adaptec's version? > > -Ed > Sorry for late reply. Several months testing shows that in-tree aac(4) as of 6.4 (and later) has no this problem. Thanks. -- wbr, pluknet ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
