zfs over geli over zfs (was: Re: zfs flag denoting unclean shutdown?)
On 10/02/2013 08:13 PM, Matthew Seaman wrote: On 02/10/2013 16:34, Nikos Vassiliadis wrote: Is there a way to know if a zfs pool had an unclean shutdown? An attribute or maybe something during mount time similar to what ufs does (WARNING: / was not properly dismounted)? Other than looking at the system logs for evidence of an abnormal shutdown, no. (Absence of anything in the logs is pretty good evidence for the system falling over pretty hard... Usually something to do with the power being turned off.) However, due to the design of ZFS unclean shutdowns like this are nowhere near as problematic as on UFS. Basically, you're guaranteed that what is written on disk is always consistent. You might lose a few transactions -- essentially the last few seconds of file system activity -- but that doesn't usually make a great deal of difference after the system reboots again. Oh, yeah -- absolutely no time will be needed to be spent cleaning and repairing filesystems: with ZFS, reboot after crash is as fast as a normal reboot. Thanks Matthew, I realized I should have used a more appropriate subject. I'll explain what my actual goal is:) I am after a really specific use-case and the last minute transactions are important. Using a zpool over geli over a zvol. I'd like to know if during shutdown the kernel flushes all zfs files caches in order so these last minutes transactions won't be lost. The unmounting order is far from obvious (zfs over geli over zfs) and i wonder if such a scheme will succeed. I can't afford losing the last transactions of my home dir every time i shutdown my laptop;) The obvious solution is to create two slices and dedicate a slice to geli. Like this: mypool lives on slice1 myencpool lives on slice2.eli I am after this: mypool lives on slice1 myencpool lives on /dev/zvol/mypool/avolume.eli The second scheme will allow me to have an encypted home and not to pre-allocate space. A quick test showed that it might work... On the other hand conceptually seems like a very bad idea haha. I think I've heard people doing this zfs over geli over zfs before... Thanks for any thoughts, Nikos ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
zfs flag denoting unclean shutdown?
Hi, Is there a way to know if a zfs pool had an unclean shutdown? An attribute or maybe something during mount time similar to what ufs does (WARNING: / was not properly dismounted)? Thanks, Nikos ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: zfs flag denoting unclean shutdown?
On 02/10/2013 16:34, Nikos Vassiliadis wrote: Is there a way to know if a zfs pool had an unclean shutdown? An attribute or maybe something during mount time similar to what ufs does (WARNING: / was not properly dismounted)? Other than looking at the system logs for evidence of an abnormal shutdown, no. (Absence of anything in the logs is pretty good evidence for the system falling over pretty hard... Usually something to do with the power being turned off.) However, due to the design of ZFS unclean shutdowns like this are nowhere near as problematic as on UFS. Basically, you're guaranteed that what is written on disk is always consistent. You might lose a few transactions -- essentially the last few seconds of file system activity -- but that doesn't usually make a great deal of difference after the system reboots again. Oh, yeah -- absolutely no time will be needed to be spent cleaning and repairing filesystems: with ZFS, reboot after crash is as fast as a normal reboot. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Question about those special (countdown numbers) at shutdown / sync
Hello! I am curious about the special (count down numbers) at shutdown / sync. Those nubmers is like 8 8 8 8 2 1 2 1 0 0 0 0. Actually what do those numbers mean? Thanks and regards, Patrick Dung ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Question about those special (countdown numbers) at shutdown / sync
On Thu, 5 Sep 2013 21:30:29 +0800 (SGT), Patrick Dung wrote: I am curious about the special (count down numbers) at shutdown / sync. Those nubmers is like 8 8 8 8 2 1 2 1 0 0 0 0. Actually what do those numbers mean? Those numbers show you how many buffers have to be synced until the system is ready to finally shut down and power off. This makes sure no pending hard disk operations will be left and forgotten in memory. The important text displayed prior to the numbers is: Syncing disks, buffers remaining... You can find it here: /usr/src/sys/kern/kern_shutdown.c around line 330 (8-STABLE/i386 here). -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Question about those special (countdown numbers) at shutdown / sync
Thanks for the answer. That is cool and unique. From: Polytropon free...@edvax.de To: Patrick Dung patrick_...@yahoo.com.hk Cc: freebsd-questions@freebsd.org freebsd-questions@freebsd.org Sent: Thursday, September 5, 2013 9:42 PM Subject: Re: Question about those special (countdown numbers) at shutdown / sync On Thu, 5 Sep 2013 21:30:29 +0800 (SGT), Patrick Dung wrote: I am curious about the special (count down numbers) at shutdown / sync. Those nubmers is like 8 8 8 8 2 1 2 1 0 0 0 0. Actually what do those numbers mean? Those numbers show you how many buffers have to be synced until the system is ready to finally shut down and power off. This makes sure no pending hard disk operations will be left and forgotten in memory. The important text displayed prior to the numbers is: Syncing disks, buffers remaining... You can find it here: /usr/src/sys/kern/kern_shutdown.c around line 330 (8-STABLE/i386 here). -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: with ACPI=on, 9.1-RELEASE shutdown automatically
On Fri, May 10, 2013 at 01:03:45PM +0200, Eduardo Morras wrote: Hi Eduardo, On Fri, 10 May 2013 12:34:14 +0200 Xavier xavierfreebsdquesti...@gmail.com wrote: Hi to all, About this email subject, on acer Aspire 5634WLMi machine and 9.1-RELEASE OS, FreeBSD shutdown the machine automatically in few minuts. In freebsd-es a similar problem was reported some months ago. The cause is fan switch off after startup menu and rising temperature. It looks like ec controller problem (Acer doesn't provide documentation about Embedded Controller, all is done by try and error and can damage the laptop) Yes, is the same situation. I don't solved the problem. For this reason I post here now. And, I wait a long time for try new situations and not crossposting the problem in other mailing list. How can I debug the reason of the problem ? A not so good wokaround is down the temperature where cpu Hz is adjusted: #sysctl hw.acpi.thermal.user_override=1 #sysctl hw.acpi.thermal.tz0._PSV=65C #sysctl hw.acpi.thermal.user_override=0 First of all, I load the correct ACPI mapping driver for acer laptops ( this situation ): acpi_wmi(4) root@casa:/root # kldstat | grep acpi 41 0xc13dd000 462c acpi_wmi.ko root@casa:/root # Now I try yours values: First, de defaults values: root@casa:/root # sysctl -a | grep hw.acpi.thermal.user_override hw.acpi.thermal.user_override: 0 root@casa:/root # sysctl -a | grep hw.acpi.thermal.tz0._PSV hw.acpi.thermal.tz0._PSV: -1 root@casa:/root # sysctl -a | grep hw.acpi.thermal.tz1._PSV hw.acpi.thermal.tz1._PSV: 95,0C root@casa:/root # sysctl -a | grep hw.acpi.thermal.user_override hw.acpi.thermal.user_override: 0 root@casa:/root # I change to your suggerations: root@casa:/root # sysctl hw.acpi.thermal.user_override=1 hw.acpi.thermal.user_override: 0 - 1 root@casa:/root # sysctl hw.acpi.thermal.tz0._PSV=65C hw.acpi.thermal.tz0._PSV: -1 - 65,0C root@casa:/root # sysctl hw.acpi.thermal.tz1._PSV=65C hw.acpi.thermal.tz1._PSV: 95,0C - 65,0C root@casa:/root # sysctl -a | grep hw.acpi.thermal.user_override hw.acpi.thermal.user_override: 1 root@casa:/root # sysctl -a | grep hw.acpi.thermal.tz0._PSV hw.acpi.thermal.tz0._PSV: 65,0C root@casa:/root # sysctl -a | grep hw.acpi.thermal.tz1._PSV hw.acpi.thermal.tz1._PSV: 65,0C root@casa:/root # I look for the temperature at the moment: root@casa:/root # sysctl -a | grep temperature acpi_tz1: temperature 67.0C: decreasing clock speed from 500 MHz to 250 MHz acpi_tz1: temperature 67.0C: decreasing clock speed from 250 MHz to 125 MHz hw.acpi.thermal.tz0.temperature: 73,0C hw.acpi.thermal.tz1.temperature: 72,0C dev.cpu.0.temperature: 75,0C dev.cpu.1.temperature: 75,0C root@casa:/root # I try compile one port ... : ... while compile I look the temperature: root@casa:/root # sysctl -a | grep temperature acpi_tz1: temperature 67.0C: decreasing clock speed from 500 MHz to 250 MHz acpi_tz1: temperature 67.0C: decreasing clock speed from 250 MHz to 125 MHz hw.acpi.thermal.tz0.temperature: 95,0C hw.acpi.thermal.tz1.temperature: 94,0C dev.cpu.0.temperature: 92,0C dev.cpu.1.temperature: 92,0C root@casa:/root # I break the compilation because if hw.acpi.thermal.tz%d.temperature ( of ACPI_THERMAL(4) ) = 100C the FreeBSD shutdown automacally. Or downgrade to 8.x On 8.x I get the same problem. Thanks, see you. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
with ACPI=on, 9.1-RELEASE shutdown automatically
Hi to all, About this email subject, on acer Aspire 5634WLMi machine and 9.1-RELEASE OS, FreeBSD shutdown the machine automatically in few minuts. How can I debug the reason of the problem ? Thanks, see you ! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: with ACPI=on, 9.1-RELEASE shutdown automatically
On Fri, 10 May 2013 12:34:14 +0200 Xavier xavierfreebsdquesti...@gmail.com wrote: Hi to all, About this email subject, on acer Aspire 5634WLMi machine and 9.1-RELEASE OS, FreeBSD shutdown the machine automatically in few minuts. In freebsd-es a similar problem was reported some months ago. The cause is fan switch off after startup menu and rising temperature. It looks like ec controller problem (Acer doesn't provide documentation about Embedded Controller, all is done by try and error and can damage the laptop) How can I debug the reason of the problem ? A not so good wokaround is down the temperature where cpu Hz is adjusted: #sysctl hw.acpi.thermal.user_override=1 #sysctl hw.acpi.thermal.tz0._PSV=65C #sysctl hw.acpi.thermal.user_override=0 Or downgrade to 8.x Thanks, see you ! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org --- --- Eduardo Morras emorr...@yahoo.es ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Virtual Box service vboxheadless shutdown problems.
I have recently setup a FreeBSD server to run virtual box, and a couple of FreeBSD jails. Performance is running great, but upon getting my UPS setup with NUT, and running some reboot tests to verify that everything is shutting down and starting up properly I ran into an issue. The /usr/local/etc/rc.d/vboxheadless script is not shutting down the VM properly, which in turn is causing other services to not stop properly. I have set the following options in my rc.conf file vboxnet_enable=YES vboxheadless_enable=YES vboxheadless_machines=HomeServer vboxheadless_user=dweimer vboxheadless_stop=acpipowerbutton vboxheadless_delay=0 issuing service vboxheadless stop, does correctly shutdown the VM cleanly, and of course service vboxheadless start starts everything OK. But when running a shutdown command the shutdown process hangs, until it gets a 90 sec watchdog timeout on the vboxheadless stop command. The VNC console to the VM, never shows any attempt for the VM to shutdown. The windows VM, also doesn't show any events in the log as if it tried to shutdown. Has anyone else ran into this? Or have any idea what to check to find out more information as to what is happening to stop the shutdown process from running correctly? -- Thanks, Dean E. Weimer http://www.dweimer.net/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: why sync during shutdown when sync already done?
On Wed, 14 Nov 2012 19:32:46 -0700, Gary Aitken wrote: It's my understanding that the sequence of numbers one sees output when shutdown is issued reflect writes of cached items. Is that correct? If so, why does: sync shutdown -r now still show cached items being written? Issuing the sync command simply tells the OS to sync any modified file I/O buffers (cache) that aren't written yet. It does not imply that the OS will do it _exactly now_, and even more, that it will _have done_ it when the command returns. So if you call sync(), the kernel will be instructed to perform the syncing operation. But keep in mind that the actual device drivers (e. g. for the hard disk in question) may delay the transfer to the disk, but tell the kernel that the operation has been completed. This minimal time window can probably be ignored, but from my understanding, syncing is a multi-staged process. The shutdown sync seems to have a specific timeout that makes sure things get written definitely. That's why even the famous # sync ; sync ; sync ; reboot sequence would have the same effect. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: shutdown -p doesn't power-off USB
For me it's even worse. http://forums.freebsd.org/showthread.php?t=29700 It occurs after the first world rebuilding and I can't solve it since months. And only occurs since 9.0 is out. 9 RC3 worked fine. However the fresh install from the 9.0 stable disk also works fine until building and installing kernel and world from src. The kernel is GENERIC and I run mergemaster properly every time it's needed. All my computers having this issue are on ZFS root and all work properly except the shutdown and reboot. Mage On 03/31/2012 17:38, Jens Schweikhardt wrote: hello world\n I'm running 9-STABLE/amd64 and for a few months now, whenever I shut down with shutdown -p now, the USB devices still have power. This is most visible on the USB keyboard, where *all* LEDs are turned on and stay on. The MB is an ASUS P5Q3 Deluxe. The USB related sysctls are: # sysctl -aw|grep -i usb descrUSB1008A Flash Disk/descr device usb hw.pci.usb_early_takeover: 1 hw.usb.no_shutdown_wait: 0 hw.usb.no_boot_wait: 0 hw.usb.debug: 0 hw.usb.usb_lang_mask: 255 hw.usb.usb_lang_id: 9 hw.usb.template: 0 hw.usb.power_timeout: 30 hw.usb.no_pf: 0 hw.usb.no_cs_fail: 0 dev.uhci.0.%desc: Intel 82801JI (ICH10) USB controller USB-D dev.uhci.0.%location: slot=26 function=0 handle=\_SB_.PCI0.USB4 dev.uhci.1.%desc: Intel 82801JI (ICH10) USB controller USB-E dev.uhci.1.%location: slot=26 function=1 handle=\_SB_.PCI0.USB5 dev.uhci.2.%desc: Intel 82801JI (ICH10) USB controller USB-F dev.uhci.2.%location: slot=26 function=2 handle=\_SB_.PCI0.USB6 dev.uhci.3.%desc: Intel 82801JI (ICH10) USB controller USB-A dev.uhci.3.%location: slot=29 function=0 handle=\_SB_.PCI0.USB0 dev.uhci.4.%desc: Intel 82801JI (ICH10) USB controller USB-B dev.uhci.4.%location: slot=29 function=1 handle=\_SB_.PCI0.USB1 dev.uhci.5.%desc: Intel 82801JI (ICH10) USB controller USB-C dev.uhci.5.%location: slot=29 function=2 handle=\_SB_.PCI0.USB2 dev.usbus.0.%desc: Intel 82801JI (ICH10) USB controller USB-D dev.usbus.0.%driver: usbus dev.usbus.0.%parent: uhci0 dev.usbus.1.%desc: Intel 82801JI (ICH10) USB controller USB-E dev.usbus.1.%driver: usbus dev.usbus.1.%parent: uhci1 dev.usbus.2.%desc: Intel 82801JI (ICH10) USB controller USB-F dev.usbus.2.%driver: usbus dev.usbus.2.%parent: uhci2 dev.usbus.3.%desc: Intel 82801JI (ICH10) USB 2.0 controller USB-B dev.usbus.3.%driver: usbus dev.usbus.3.%parent: ehci0 dev.usbus.4.%driver: usbus dev.usbus.4.%parent: xhci0 dev.usbus.5.%desc: Intel 82801JI (ICH10) USB controller USB-A dev.usbus.5.%driver: usbus dev.usbus.5.%parent: uhci3 dev.usbus.6.%desc: Intel 82801JI (ICH10) USB controller USB-B dev.usbus.6.%driver: usbus dev.usbus.6.%parent: uhci4 dev.usbus.7.%desc: Intel 82801JI (ICH10) USB controller USB-C dev.usbus.7.%driver: usbus dev.usbus.7.%parent: uhci5 dev.usbus.8.%desc: Intel 82801JI (ICH10) USB 2.0 controller USB-A dev.usbus.8.%driver: usbus dev.usbus.8.%parent: ehci1 dev.ehci.0.%desc: Intel 82801JI (ICH10) USB 2.0 controller USB-B dev.ehci.0.%location: slot=26 function=7 handle=\_SB_.PCI0.USBE dev.ehci.1.%desc: Intel 82801JI (ICH10) USB 2.0 controller USB-A dev.ehci.1.%location: slot=29 function=7 handle=\_SB_.PCI0.EUSB dev.xhci.0.%desc: XHCI (generic) USB 3.0 controller dev.uhub.0.%parent: usbus0 dev.uhub.1.%parent: usbus1 dev.uhub.2.%parent: usbus2 dev.uhub.3.%parent: usbus3 dev.uhub.4.%parent: usbus4 dev.uhub.5.%parent: usbus5 dev.uhub.6.%parent: usbus6 dev.uhub.7.%parent: usbus7 dev.uhub.8.%parent: usbus8 dev.ums.0.%desc: Logitech USB Receiver, class 0/0, rev 2.00/22.00, addr 2 dev.uhid.0.%desc: Logitech USB Receiver, class 0/0, rev 2.00/22.00, addr 2 Any help appreciated in telling me how to turn off USB power with shutdown. Regards, Jens ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: shutdown -p doesn't power-off USB
On Sat, 31 Mar 2012 17:38:11 +0200, Jens Schweikhardt wrote: I'm running 9-STABLE/amd64 and for a few months now, whenever I shut down with shutdown -p now, the USB devices still have power. This is most visible on the USB keyboard, where *all* LEDs are turned on and stay on. That's not a bug, it's a feature. :-) Many mainboards allow switching-on per keyboard. There's typically a toggle in the board's CMOS setup. Maybe there's also an option to turn USB power completely off. However, USB powered on seems to be the default as soon as the machine's power supply is on line. The MB is an ASUS P5Q3 Deluxe. Also check its documentation, maybe USB power is mentioned? Any help appreciated in telling me how to turn off USB power with shutdown. I don't think this is any option in the OS. You should check this per hardware. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
shutdown -p doesn't power-off USB
hello world\n I'm running 9-STABLE/amd64 and for a few months now, whenever I shut down with shutdown -p now, the USB devices still have power. This is most visible on the USB keyboard, where *all* LEDs are turned on and stay on. The MB is an ASUS P5Q3 Deluxe. The USB related sysctls are: # sysctl -aw|grep -i usb descrUSB1008A Flash Disk/descr device usb hw.pci.usb_early_takeover: 1 hw.usb.no_shutdown_wait: 0 hw.usb.no_boot_wait: 0 hw.usb.debug: 0 hw.usb.usb_lang_mask: 255 hw.usb.usb_lang_id: 9 hw.usb.template: 0 hw.usb.power_timeout: 30 hw.usb.no_pf: 0 hw.usb.no_cs_fail: 0 dev.uhci.0.%desc: Intel 82801JI (ICH10) USB controller USB-D dev.uhci.0.%location: slot=26 function=0 handle=\_SB_.PCI0.USB4 dev.uhci.1.%desc: Intel 82801JI (ICH10) USB controller USB-E dev.uhci.1.%location: slot=26 function=1 handle=\_SB_.PCI0.USB5 dev.uhci.2.%desc: Intel 82801JI (ICH10) USB controller USB-F dev.uhci.2.%location: slot=26 function=2 handle=\_SB_.PCI0.USB6 dev.uhci.3.%desc: Intel 82801JI (ICH10) USB controller USB-A dev.uhci.3.%location: slot=29 function=0 handle=\_SB_.PCI0.USB0 dev.uhci.4.%desc: Intel 82801JI (ICH10) USB controller USB-B dev.uhci.4.%location: slot=29 function=1 handle=\_SB_.PCI0.USB1 dev.uhci.5.%desc: Intel 82801JI (ICH10) USB controller USB-C dev.uhci.5.%location: slot=29 function=2 handle=\_SB_.PCI0.USB2 dev.usbus.0.%desc: Intel 82801JI (ICH10) USB controller USB-D dev.usbus.0.%driver: usbus dev.usbus.0.%parent: uhci0 dev.usbus.1.%desc: Intel 82801JI (ICH10) USB controller USB-E dev.usbus.1.%driver: usbus dev.usbus.1.%parent: uhci1 dev.usbus.2.%desc: Intel 82801JI (ICH10) USB controller USB-F dev.usbus.2.%driver: usbus dev.usbus.2.%parent: uhci2 dev.usbus.3.%desc: Intel 82801JI (ICH10) USB 2.0 controller USB-B dev.usbus.3.%driver: usbus dev.usbus.3.%parent: ehci0 dev.usbus.4.%driver: usbus dev.usbus.4.%parent: xhci0 dev.usbus.5.%desc: Intel 82801JI (ICH10) USB controller USB-A dev.usbus.5.%driver: usbus dev.usbus.5.%parent: uhci3 dev.usbus.6.%desc: Intel 82801JI (ICH10) USB controller USB-B dev.usbus.6.%driver: usbus dev.usbus.6.%parent: uhci4 dev.usbus.7.%desc: Intel 82801JI (ICH10) USB controller USB-C dev.usbus.7.%driver: usbus dev.usbus.7.%parent: uhci5 dev.usbus.8.%desc: Intel 82801JI (ICH10) USB 2.0 controller USB-A dev.usbus.8.%driver: usbus dev.usbus.8.%parent: ehci1 dev.ehci.0.%desc: Intel 82801JI (ICH10) USB 2.0 controller USB-B dev.ehci.0.%location: slot=26 function=7 handle=\_SB_.PCI0.USBE dev.ehci.1.%desc: Intel 82801JI (ICH10) USB 2.0 controller USB-A dev.ehci.1.%location: slot=29 function=7 handle=\_SB_.PCI0.EUSB dev.xhci.0.%desc: XHCI (generic) USB 3.0 controller dev.uhub.0.%parent: usbus0 dev.uhub.1.%parent: usbus1 dev.uhub.2.%parent: usbus2 dev.uhub.3.%parent: usbus3 dev.uhub.4.%parent: usbus4 dev.uhub.5.%parent: usbus5 dev.uhub.6.%parent: usbus6 dev.uhub.7.%parent: usbus7 dev.uhub.8.%parent: usbus8 dev.ums.0.%desc: Logitech USB Receiver, class 0/0, rev 2.00/22.00, addr 2 dev.uhid.0.%desc: Logitech USB Receiver, class 0/0, rev 2.00/22.00, addr 2 Any help appreciated in telling me how to turn off USB power with shutdown. Regards, Jens -- Jens Schweikhardt http://www.schweikhardt.net/ SIGSIG -- signature too long (core dumped) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: shutdown -p doesn't power-off USB
That would be something in the BIOS settings, probably... On Sat, Mar 31, 2012 at 8:38 AM, Jens Schweikhardt schwe...@schweikhardt.net wrote: hello world\n I'm running 9-STABLE/amd64 and for a few months now, whenever I shut down with shutdown -p now, the USB devices still have power. This is most visible on the USB keyboard, where *all* LEDs are turned on and stay on. The MB is an ASUS P5Q3 Deluxe. The USB related sysctls are: # sysctl -aw|grep -i usb descrUSB1008A Flash Disk/descr device usb hw.pci.usb_early_takeover: 1 hw.usb.no_shutdown_wait: 0 hw.usb.no_boot_wait: 0 hw.usb.debug: 0 hw.usb.usb_lang_mask: 255 hw.usb.usb_lang_id: 9 hw.usb.template: 0 hw.usb.power_timeout: 30 hw.usb.no_pf: 0 hw.usb.no_cs_fail: 0 dev.uhci.0.%desc: Intel 82801JI (ICH10) USB controller USB-D dev.uhci.0.%location: slot=26 function=0 handle=\_SB_.PCI0.USB4 dev.uhci.1.%desc: Intel 82801JI (ICH10) USB controller USB-E dev.uhci.1.%location: slot=26 function=1 handle=\_SB_.PCI0.USB5 dev.uhci.2.%desc: Intel 82801JI (ICH10) USB controller USB-F dev.uhci.2.%location: slot=26 function=2 handle=\_SB_.PCI0.USB6 dev.uhci.3.%desc: Intel 82801JI (ICH10) USB controller USB-A dev.uhci.3.%location: slot=29 function=0 handle=\_SB_.PCI0.USB0 dev.uhci.4.%desc: Intel 82801JI (ICH10) USB controller USB-B dev.uhci.4.%location: slot=29 function=1 handle=\_SB_.PCI0.USB1 dev.uhci.5.%desc: Intel 82801JI (ICH10) USB controller USB-C dev.uhci.5.%location: slot=29 function=2 handle=\_SB_.PCI0.USB2 dev.usbus.0.%desc: Intel 82801JI (ICH10) USB controller USB-D dev.usbus.0.%driver: usbus dev.usbus.0.%parent: uhci0 dev.usbus.1.%desc: Intel 82801JI (ICH10) USB controller USB-E dev.usbus.1.%driver: usbus dev.usbus.1.%parent: uhci1 dev.usbus.2.%desc: Intel 82801JI (ICH10) USB controller USB-F dev.usbus.2.%driver: usbus dev.usbus.2.%parent: uhci2 dev.usbus.3.%desc: Intel 82801JI (ICH10) USB 2.0 controller USB-B dev.usbus.3.%driver: usbus dev.usbus.3.%parent: ehci0 dev.usbus.4.%driver: usbus dev.usbus.4.%parent: xhci0 dev.usbus.5.%desc: Intel 82801JI (ICH10) USB controller USB-A dev.usbus.5.%driver: usbus dev.usbus.5.%parent: uhci3 dev.usbus.6.%desc: Intel 82801JI (ICH10) USB controller USB-B dev.usbus.6.%driver: usbus dev.usbus.6.%parent: uhci4 dev.usbus.7.%desc: Intel 82801JI (ICH10) USB controller USB-C dev.usbus.7.%driver: usbus dev.usbus.7.%parent: uhci5 dev.usbus.8.%desc: Intel 82801JI (ICH10) USB 2.0 controller USB-A dev.usbus.8.%driver: usbus dev.usbus.8.%parent: ehci1 dev.ehci.0.%desc: Intel 82801JI (ICH10) USB 2.0 controller USB-B dev.ehci.0.%location: slot=26 function=7 handle=\_SB_.PCI0.USBE dev.ehci.1.%desc: Intel 82801JI (ICH10) USB 2.0 controller USB-A dev.ehci.1.%location: slot=29 function=7 handle=\_SB_.PCI0.EUSB dev.xhci.0.%desc: XHCI (generic) USB 3.0 controller dev.uhub.0.%parent: usbus0 dev.uhub.1.%parent: usbus1 dev.uhub.2.%parent: usbus2 dev.uhub.3.%parent: usbus3 dev.uhub.4.%parent: usbus4 dev.uhub.5.%parent: usbus5 dev.uhub.6.%parent: usbus6 dev.uhub.7.%parent: usbus7 dev.uhub.8.%parent: usbus8 dev.ums.0.%desc: Logitech USB Receiver, class 0/0, rev 2.00/22.00, addr 2 dev.uhid.0.%desc: Logitech USB Receiver, class 0/0, rev 2.00/22.00, addr 2 Any help appreciated in telling me how to turn off USB power with shutdown. Regards, Jens -- Jens Schweikhardt http://www.schweikhardt.net/ SIGSIG -- signature too long (core dumped) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Invitation to Efficient Plant Shutdown Turnaround Forum 2012 - Kuala Lumpur
20 - 21 March 2012, The Royale Chulan Hotel, Kuala Lumpur A Regional TAR Management Forum - APAC Dear Energy Peer, “How should we handle forced outages?” - Avoid a heart rending sight of smouldering our plants with spiralling smoke. We're spending years to plan TAR. We definitely know how challenging it is. Attend and learn from our TAR peers (who used to face the same challenges as we do) on how to spearhead our most expensive project of the year towards EXCELLENCE and conquer the challenges: 1. Implementing World Class HSE Standards 2. Forced Outages – How to Handle Unplanned Situations Like an Expert 3. Dealing Overcoming Uncertainties During a Planned Shutdown 4. Analysing Effectiveness of Turnaround for Future Improvement 5. Planning Mobilising Large Workforce Resources 6. Controlling the Shutdown Turnaround Budget 7. Assessing Plant Readiness for Shutdown 8. Leadership Behaviour that Shapes the Turnaround and Business Results 9. Lively Discussion with TAR Experts - the experienced real experts 10. Developing Maintaining a Detailed Support Plan Lucky Draw! 2 units of Apple iPads pre-loaded with Turnaround Management System Checklists to be given away. Download agenda now! Forward this to your concerned colleagues also. Best, Kyle Law T: 603 2141 5357 E: kyle@fleminggulf.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Input file for shutdown warning?
On Mon, May 16, 2011 at 05:38:21PM -0700, Alexander Lardner wrote: Hello, Is it possible to do something like this: shutdown -p now /root/somefile How would I do that, or is it even possible? Thanks, Alex Use wall(1) # wall somefile shutdown -p now Regards, -- Frank Contact info: http://www.shute.org.uk/misc/contact.html pgp2j4O9HESsj.pgp Description: PGP signature
Input file for shutdown warning?
Hello, Is it possible to do something like this: shutdown -p now /root/somefile How would I do that, or is it even possible? Thanks, Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Input file for shutdown warning?
On Mon, 16 May 2011 17:38:21 -0700 Alexander Lardner linuxtu...@gmail.com wrote: Hello, Is it possible to do something like this: shutdown -p now /root/somefile How would I do that, or is it even possible? According to the man page it is. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Input file for shutdown warning?
On 17 May 2011 01:24:56 - John Levine jo...@iecc.com wrote: In article 20110517021633.26b47...@gumby.homeunix.com you write: On Mon, 16 May 2011 17:38:21 -0700 Alexander Lardner linuxtu...@gmail.com wrote: Hello, Is it possible to do something like this: shutdown -p now /root/somefile # shutdown - -p now /root/somefile shutdown -p now - /root/somefile ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Input file for shutdown warning?
In article 20110517021633.26b47...@gumby.homeunix.com you write: On Mon, 16 May 2011 17:38:21 -0700 Alexander Lardner linuxtu...@gmail.com wrote: Hello, Is it possible to do something like this: shutdown -p now /root/somefile # shutdown - -p now /root/somefile If you had read the man page, you would already know that. R's, John ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: shutdown computer after the halt command
On 02/08/2011 01:26 AM, Eitan Adler wrote: if I use the *halt* command I just see the system is halted press any key to reboot How can I fix this? shutdown -p now don't use halt directly Thanks works as expected ... Regards, alokat ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
shutdown computer after the halt command
Hi, if I use the *halt* command I just see the system is halted press any key to reboot How can I fix this? * Halt* should cut off my laptop. Regards, alokat ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: shutdown computer after the halt command
On Tue Feb 8 11, Alokat wrote: Hi, if I use the *halt* command I just see the system is halted press any key to reboot How can I fix this? * Halt* should cut off my laptop. try 'shutdown -p now' Regards, alokat -- a13x ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: shutdown computer after the halt command
On Tue, 2011-02-08 at 01:06 +0100, Alokat wrote: Hi, if I use the *halt* command I just see the system is halted press any key to reboot How can I fix this? halt -p NOTE: May require ACPI support loaded into the kernel. -- Devin * Halt* should cut off my laptop. Regards, alokat ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: shutdown computer after the halt command
if I use the *halt* command I just see the system is halted press any key to reboot How can I fix this? shutdown -p now don't use halt directly -- Eitan Adler ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: shutdown computer after the halt command
On Mon, 2011-02-07 at 19:26 -0500, Eitan Adler wrote: if I use the *halt* command I just see the system is halted press any key to reboot How can I fix this? shutdown -p now don't use halt directly There's no technical reason to avoid using halt directly other than the fact that shutdown sends a message to connected users while halt does not. -- Devin P.S. I welcome the rebuttle as a learning experience if the above is not 100% accurate and true (but be-warned... I went around the office polling _really_ old UNIX hands before making the above statement). ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: shutdown computer after the halt command
On Mon, 2011-02-07 at 19:26 -0600, Adam Vande More wrote: On Mon, Feb 7, 2011 at 7:13 PM, Devin Teske dte...@vicor.com wrote: There's no technical reason to avoid using halt directly other than the fact that shutdown sends a message to connected users while halt does not. -- Devin P.S. I welcome the rebuttle as a learning experience if the above is not 100% accurate and true (but be-warned... I went around the office polling _really_ old UNIX hands before making the above statement). I used to believe that until I was shown I was wrong. The easiest way to see you're wrong is to drop to ttyv0 then do one of each like a reboot then a shutdown -r now. In the latter case, you'll notice /etc/rc.d/ and /usr/local/etc/rc.d/ stop scripts being processed but not so in the former. In both types of shutdowns, everything *should* exit cleanly but processes are terminated with different signals and certain types of applications really need the full rc stop script to end cleanly like HAST and CARP for example. shutdown -r/p is a really good habit to form. FWIW, someone also stated reboot on Linux behaves like shutdown -r now so that I sure contributes to the confusion. Thank you very much for the explanation! Yes, I (we) had completely forgotten about the shutdown scripts. Of course, many of us still remember the days when it standard fare to sync; sync; halt. -- Devin -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: shutdown computer after the halt command
Allow me to split hairs here. I was taught sync;sync;sync;halt. One for the father, one for the son, one for the holy spirit. This, of course, in the days when I/O was slow enough that sync didn't have time to finish before the halt, so doing it three times ensured your file system shut down cleanly. Dave On 02/07/11 17:38, Devin Teske wrote: On Mon, 2011-02-07 at 19:26 -0600, Adam Vande More wrote: On Mon, Feb 7, 2011 at 7:13 PM, Devin Teskedte...@vicor.com wrote: There's no technical reason to avoid using halt directly other than the fact that shutdown sends a message to connected users while halt does not. -- Devin P.S. I welcome the rebuttle as a learning experience if the above is not 100% accurate and true (but be-warned... I went around the office polling _really_ old UNIX hands before making the above statement). I used to believe that until I was shown I was wrong. The easiest way to see you're wrong is to drop to ttyv0 then do one of each like a reboot then a shutdown -r now. In the latter case, you'll notice /etc/rc.d/ and /usr/local/etc/rc.d/ stop scripts being processed but not so in the former. In both types of shutdowns, everything *should* exit cleanly but processes are terminated with different signals and certain types of applications really need the full rc stop script to end cleanly like HAST and CARP for example. shutdown -r/p is a really good habit to form. FWIW, someone also stated reboot on Linux behaves like shutdown -r now so that I sure contributes to the confusion. Thank you very much for the explanation! Yes, I (we) had completely forgotten about the shutdown scripts. Of course, many of us still remember the days when it standard fare to sync; sync; halt. -- Devin -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org -- Dave Robison Sales Solution Architect II FIS Banking Solutions 510/621-2089 (w) 530/518-5194 (c) 510/621-2020 (f) da...@vicor.com david.robi...@fisglobal.com _ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. _ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: shutdown computer after the halt command
On Mon, 07 Feb 2011 17:38:50 -0800, Devin Teske dte...@vicor.com wrote: Of course, many of us still remember the days when it standard fare to sync; sync; halt. Erm... what about sync; sync; init 0? :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: shutdown computer after the halt command
On Mon, Feb 7, 2011 at 7:13 PM, Devin Teske dte...@vicor.com wrote: There's no technical reason to avoid using halt directly other than the fact that shutdown sends a message to connected users while halt does not. -- Devin P.S. I welcome the rebuttle as a learning experience if the above is not 100% accurate and true (but be-warned... I went around the office polling _really_ old UNIX hands before making the above statement). I used to believe that until I was shown I was wrong. The easiest way to see you're wrong is to drop to ttyv0 then do one of each like a reboot then a shutdown -r now. In the latter case, you'll notice /etc/rc.d/ and /usr/local/etc/rc.d/ stop scripts being processed but not so in the former. In both types of shutdowns, everything *should* exit cleanly but processes are terminated with different signals and certain types of applications really need the full rc stop script to end cleanly like HAST and CARP for example. shutdown -r/p is a really good habit to form. FWIW, someone also stated reboot on Linux behaves like shutdown -r now so that I sure contributes to the confusion. -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: shutdown computer after the halt command
I used to believe that until I was shown I was wrong. The easiest way to see you're wrong is to drop to ttyv0 then do one of each like a reboot then a shutdown -r now. In the latter case, you'll notice /etc/rc.d/ and /usr/local/etc/rc.d/ stop scripts being processed but not so in the former. Uh, no. shutdown or halt signals init, and init runs /etc/rc.shutdown which runs all the shutdown scripts. The only extra work that shutdown does is to blat lots of warnings onto the ttys. Read the man pages for shutdown, halt, and init if you believe otherwise. Regards, John Levine, jo...@iecc.com, Primary Perpetrator of The Internet for Dummies, Please consider the environment before reading this e-mail. http://jl.ly ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: shutdown computer after the halt command
On Mon, Feb 7, 2011 at 8:54 PM, John Levine jo...@iecc.com wrote: I used to believe that until I was shown I was wrong. The easiest way to see you're wrong is to drop to ttyv0 then do one of each like a reboot then a shutdown -r now. In the latter case, you'll notice /etc/rc.d/ and /usr/local/etc/rc.d/ stop scripts being processed but not so in the former. Uh, no. shutdown or halt signals init, and init runs /etc/rc.shutdown which runs all the shutdown scripts. The only extra work that shutdown does is to blat lots of warnings onto the ttys. Read the man pages for shutdown, halt, and init if you believe otherwise.http://jl.ly Yes please do so as that's not what it says at all although I think could certainly be a worded better. It's quite easy to see you're wrong, just follow the steps I outlined above. If you are correct, reboot(8) should print things like: Stopping sshd. to the console. It doesn't and shutdown(8) does so the proof is right there. The reboot man page only hints at it though unfortunately which caused my initial confusion(in addition to the permissions mismatch between the two). Normally, the shutdown(8) utility is used when the system needs to be halted or restarted, giving users advance warning of their impending doom and cleanly terminating specific programs. You can also reference init.c if you still think you're correct. In addition, please read carefully through this thread and then examine your arguments vs what is reality and then we can all be on the same page. http://lists.freebsd.org/pipermail/freebsd-stable/2010-December/060519.html -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: shutdown computer after the halt command
It's quite easy to see you're wrong, just follow the steps I outlined above. If you are correct, reboot(8) should print things like: Stopping sshd. to the console. Sigh. I shut down my FreeBSD 8.1 laptop all the time with halt -p, and I can assure you it prints all those messages. You can also reference init.c if you still think you're correct. No thanks, I've already read the man page for init, including this paragraph: When shutting down the machine, init will try to run the /etc/rc.shutdown script. This script can be used to cleanly terminate specific programs such as innd (the InterNetNews server). If this script does not termi- nate within 120 seconds, init will terminate it. The timeout can be con- figured via the sysctl(8) variable kern.init_shutdown_timeout. If you're unfamiliar with rc.shutdown, it also has a man page. Perhaps your copy of FreeBSD was installed incorrectly, or it's been so long since you tried halt or reboot that you forgot what happened. Regards, John Levine, jo...@iecc.com, Primary Perpetrator of The Internet for Dummies, Please consider the environment before reading this e-mail. http://jl.ly ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: shutdown computer after the halt command
On Mon, Feb 7, 2011 at 9:31 PM, John R. Levine jo...@iecc.com wrote: It's quite easy to see you're wrong, just follow the steps I outlined above. If you are correct, reboot(8) should print things like: Stopping sshd. to the console. Sigh. I shut down my FreeBSD 8.1 laptop all the time with halt -p, and I can assure you it prints all those messages. Are you hitting the bottle hard tonight? It does no such thing. You can also reference init.c if you still think you're correct. No thanks, I've already read the man page for init, including this paragraph: When shutting down the machine, init will try to run the /etc/rc.shutdown script. This script can be used to cleanly terminate specific programs such as innd (the InterNetNews server). If this script does not termi- nate within 120 seconds, init will terminate it. The timeout can be con- figured via the sysctl(8) variable kern.init_shutdown_timeout. Exactly, reboot(8) doesn't call init, shutdown(8) does. See reboot.c, shutdown.c -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: shutdown computer after the halt command
On Mon, Feb 7, 2011 at 7:31 PM, John R. Levine jo...@iecc.com wrote: It's quite easy to see you're wrong, just follow the steps I outlined above. If you are correct, reboot(8) should print things like: Stopping sshd. to the console. Sigh. I shut down my FreeBSD 8.1 laptop all the time with halt -p, and I can assure you it prints all those messages. Well, that's not what everyone else sees. You can also reference init.c if you still think you're correct. No thanks, I've already read the man page for init, including this paragraph: That man page hasn't been more than minorly tweaked in over 10 years, according to cvsweb. Perhaps your copy of FreeBSD was installed incorrectly, or it's been so long since you tried halt or reboot that you forgot what happened. Just did - it kills all process and moves to the syncing disks stage. Nothing rc related is touched. -- Rob Farmer ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: shutdown computer after the halt command
Hmmn, I looked at the code and by golly you're right, halt/reboot doesn't poke init. Nonetheless, I really do see a lot of foo stopping messages when I use halt, presumably because the SIGTERM that halt/reboot sends has the same effect (if not the same ordering) as the ones that the various rc.d scripts send. Looks like init 0 would be tidier than halt -p, and in the finest Unix tradition, is one less character to type. Regards, John Levine, jo...@iecc.com, Primary Perpetrator of The Internet for Dummies, Please consider the environment before reading this e-mail. http://jl.ly ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 8.1-STABLE amd 64 crash during shutdown
On Mon, Jan 3, 2011 at 5:06 PM, Janos Dohanics w...@3dresearch.com wrote: My system crashed during shutdown, so I tried to get a crash dump, but I don't seem to be able to do so: Dumping 1224 MB: (stops at 1177) Fatal trap 12: page fault while in kernel mode cpuid = 1, apic id = 01 fault virtual address = 0x1 fault code = supervisor read instruction, page not present instruction pointer: 0x20:0x1 uname -opr FreeBSD 8.1-STABLE amd64 I'd appreciate your advice... Just a wild guess: Does your system crash if it is booted with ACPI disabled? And is your swap partition big enough to create the dump? -- Janos Dohanics w...@3dresearch.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
FreeBSD 8.1-STABLE amd 64 crash during shutdown
My system crashed during shutdown, so I tried to get a crash dump, but I don't seem to be able to do so: Dumping 1224 MB: (stops at 1177) Fatal trap 12: page fault while in kernel mode cpuid = 1, apic id = 01 fault virtual address = 0x1 fault code= supervisor read instruction, page not present instruction pointer: 0x20:0x1 uname -opr FreeBSD 8.1-STABLE amd64 I'd appreciate your advice... -- Janos Dohanics w...@3dresearch.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: How to prevent system to launch interactive fsck after improper shutdown and reboot?
On Wed, 15 Sep 2010 17:11:30 -0400 (EDT), d...@safeport.com wrote: I have had two systems die with bad disks. Personally, I never had trouble with bad disks, but with defective file systems (origin unknown), and follow-up trouble caused by background fsck that prevented me many years from accessing my data. Going the old fashioned way brought everything back. Long story short: A present .snapshot from the 1st background fsck (which was introduced as default in 5.0, as far as I remember) caused fsck from working as expected; after removing this file, I got all the missing data back. Luckily, the problem didn't seem to be related to actual disk failure, as SMART data didn't give a hint about that. I did work with a 1:1 dd copy anyway. Modern disks die silently which I think is too bad. You usally see messages in dmesg / console that indicate disk trouble. In mos cases, those messages say that the disk is already dying - it's too late for repair. So time for backup and replacement. Seems that this is the result of continuing bigger and cheaper disks... If this is happening and you have data you want to recover you might try booting in single user move and using fsck manually on each slice. The fsck program operates on partitions, not on slices. Terminology, dear Watson. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
How to prevent system to launch interactive fsck after improper shutdown and reboot?
Almost every time after improper shutdown (poweroff) and reboot I get into interactive fsck. I am being asked whole bunch of questions to which I just have to answer Y (what are my other options?) Why drop user into interactive fsck if there is not much choice anyways? Is there a way to set it up the way it doesn't drop into interactive mode? Like answer 'Y' to all questions? Yuri ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: How to prevent system to launch interactive fsck after improper shutdown and reboot?
Almost every time after improper shutdown (poweroff) and reboot I get into interactive fsck. I am being asked whole bunch of questions to which I just have to answer Y (what are my other options?) Why drop user into interactive fsck if there is not much choice anyways? Is there a way to set it up the way it doesn't drop into interactive mode? Like answer 'Y' to all questions? Yuri I think this might do your trick: fsck_y_enable=NO # Set to YES to do fsck -y if the initial preen fails. fsck_y_flags= # Additional flags for fsck -y The reason for this to get interactively is because this might messup with your filesystem, and you are the one responsible for your filesystem, not us or the autmated system. So in case you want to play with that, that's entirely up to you. In addition, I can imagine that companies (been there done it) do not want to fsck -y by default, this because of the mentioned potential corruption and dataloss. Thanks remko p.s. This was found within 5 seconds in /etc/defaults/rc.conf. -- /\ Best regards, | re...@freebsd.org \ / Remko Lodder | re...@efnet Xhttp://www.evilcoder.org/ | / \ ASCII Ribbon Campaign | Against HTML Mail and News ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: How to prevent system to launch interactive fsck after improper shutdown and reboot?
El día Wednesday, September 15, 2010 a las 09:41:54AM +0300, Yuri escribió: Almost every time after improper shutdown (poweroff) and reboot I get into interactive fsck. I am being asked whole bunch of questions to which I just have to answer Y (what are my other options?) Why drop user into interactive fsck if there is not much choice anyways? Is there a way to set it up the way it doesn't drop into interactive mode? Like answer 'Y' to all questions? Yes, just do: $ echo 16i[q]sa[ln0=aln100%Pln100/snlbx]sbA0D4D465452snlb xq | dc $ man rc.conf | col -b | fgrep fsck_ In general one should avoid unclean shutdowns. I even after such event go into single user mode and run fsck(8) by hand. HIH matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e g...@unixarea.de - w http://www.unixarea.de/ Solidarity with the zionistic pirates of Israel? Not in my name! ¿Solidaridad con los piratas sionistas de Israel? ¡No en mi nombre! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: How to prevent system to launch interactive fsck after improper shutdown and reboot?
On 15-9-2010 8:53, Matthias Apitz wrote: echo 16i[q]sa[ln0=aln100%Pln100/snlbx]sbA0D4D465452snlb xq | dc LOL, only worked with quotes, btw ;-) Peter -- http://www.boosten.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: How to prevent system to launch interactive fsck after improper shutdown and reboot?
On Wed, Sep 15, 2010 at 1:59 AM, Peter Boosten pe...@boosten.org wrote: On 15-9-2010 8:53, Matthias Apitz wrote: echo 16i[q]sa[ln0=aln100%Pln100/snlbx]sbA0D4D465452snlb xq | dc LOL, only worked with quotes, btw ;-) Depends on the shell, I guess he's a bash user. -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: How to prevent system to launch interactive fsck after improper shutdown and reboot?
El día Wednesday, September 15, 2010 a las 08:59:07AM +0200, Peter Boosten escribió: On 15-9-2010 8:53, Matthias Apitz wrote: echo 16i[q]sa[ln0=aln100%Pln100/snlbx]sbA0D4D465452snlb xq | dc LOL, only worked with quotes, btw ;-) no, $ sh $ echo 16i[q]sa[ln0=aln100%Pln100/snlbx]sbA0D4D465452snlb xq | dc RTFM $ bash g...@current:/usr/home/guru echo 16i[q]sa[ln0=aln100%Pln100/snlbx]sbA0D4D465452snlb xq | dc RTFM which shell you used? matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e g...@unixarea.de - w http://www.unixarea.de/ Solidarity with the zionistic pirates of Israel? Not in my name! ¿Solidaridad con los piratas sionistas de Israel? ¡No en mi nombre! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: How to prevent system to launch interactive fsck after improper shutdown and reboot?
On 15-9-2010 9:07, Matthias Apitz wrote: $ sh $ echo 16i[q]sa[ln0=aln100%Pln100/snlbx]sbA0D4D465452snlb xq | dc RTFM $ bash g...@current:/usr/home/guru echo 16i[q]sa[ln0=aln100%Pln100/snlbx]sbA0D4D465452snlb xq | dc RTFM which shell you used? zsh. Peter -- http://www.boosten.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: How to prevent system to launch interactive fsck after improper shutdown and reboot?
On Wed, Sep 15, 2010 at 2:07 AM, Matthias Apitz g...@unixarea.de wrote: El día Wednesday, September 15, 2010 a las 08:59:07AM +0200, Peter Boosten escribió: On 15-9-2010 8:53, Matthias Apitz wrote: echo 16i[q]sa[ln0=aln100%Pln100/snlbx]sbA0D4D465452snlb xq | dc LOL, only worked with quotes, btw ;-) no, $ sh $ echo 16i[q]sa[ln0=aln100%Pln100/snlbx]sbA0D4D465452snlb xq | dc RTFM $ bash g...@current:/usr/home/guru echo 16i[q]sa[ln0=aln100%Pln100/snlbx]sbA0D4D465452snlb xq | dc RTFM which shell you used? it doesn't work in zsh, csh, tcsh, I didn't try sh, it didn't even occur to me since I so rarely use it as an interactive shell. -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: How to prevent system to launch interactive fsck after improper shutdown and reboot?
On Wed, 15 Sep 2010 08:47:38 +0200, Remko Lodder re...@elvandar.org wrote: Almost every time after improper shutdown (poweroff) and reboot I get into interactive fsck. I am being asked whole bunch of questions to which I just have to answer Y (what are my other options?) Why drop user into interactive fsck if there is not much choice anyways? Is there a way to set it up the way it doesn't drop into interactive mode? Like answer 'Y' to all questions? Yuri I think this might do your trick: fsck_y_enable=NO # Set to YES to do fsck -y if the initial preen fails. fsck_y_flags= # Additional flags for fsck -y The reason for this to get interactively is because this might messup with your filesystem, and you are the one responsible for your filesystem, not us or the autmated system. So in case you want to play with that, that's entirely up to you. In addition, I can imagine that companies (been there done it) do not want to fsck -y by default, this because of the mentioned potential corruption and dataloss. Very important point. As an addition, allow me to mention background_fsck=YES as an entry in /etc/rc.conf. This will let the system boot up and perform fsck checks while the system is running - running on a maybe defective or inconsistent file system. This is dangerous, but possible. It utilizes a snapshot mechanism which can cause further trouble (lost / emptyinodes and disappearing subtrees of files). Personally, if fsck requires YOUR attention, there's usually a reason for this. The reason is possible data loss or file system corruption where YOU take the responsibility of decision, not fsck. By default, fsck does not do damaging, but under strange circumstances, it can happen. For example, if you want to do a special kind of data recovery or forensic analysis on a file system, you potentially DO NOT WANT fsck to assume y for all the questions because that can make your job harder. A common additional y flag is -f (means fsck -yf) to force all operations suggested by fsck and confirming them. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: How to prevent system to launch interactive fsck after improper shutdown and reboot?
On 09/15/10 09:47, Remko Lodder wrote: I think this might do your trick: fsck_y_enable=NO # Set to YES to do fsck -y if the initial preen fails. fsck_y_flags= # Additional flags for fsck -y The reason for this to get interactively is because this might messup with your filesystem, and you are the one responsible for your filesystem, not us or the autmated system. So in case you want to play with that, that's entirely up to you. In addition, I can imagine that companies (been there done it) do not want to fsck -y by default, this because of the mentioned potential corruption and dataloss. Thanks remko p.s. This was found within 5 seconds in /etc/defaults/rc.conf. Thanks Remko! I never had spare 5 secs for this :-), and now when I left my computer to friends (not computer savvy) they got into this trap. There is no database... I think installer better asks this question during installation since many users just run a desktop and -y is pretty much ok for them. Thank you again, Yuri ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: How to prevent system to launch interactive fsck after improper shutdown and reboot?
On Wed, Sep 15, 2010 at 12:00 AM, Yuri y...@rawbw.com wrote: Thanks Remko! I never had spare 5 secs for this :-), and now when I left my computer to friends (not computer savvy) they got into this trap. There is no database... I think installer better asks this question during installation since many users just run a desktop and -y is pretty much ok for them. Train your friends to shut the machine down by pressing (not holding down!) the power button. On any modern machine ACPI should trigger a clean shutdown/poweroff. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: How to prevent system to launch interactive fsck after improper shutdown and reboot?
On Wed, 15 Sep 2010, Polytropon wrote: On Wed, 15 Sep 2010 08:47:38 +0200, Remko Lodder re...@elvandar.org wrote: Almost every time after improper shutdown (poweroff) and reboot I get into interactive fsck. I am being asked whole bunch of questions to which I just have to answer Y (what are my other options?) Why drop user into interactive fsck if there is not much choice anyways? Is there a way to set it up the way it doesn't drop into interactive mode? Like answer 'Y' to all questions? Yuri I think this might do your trick: fsck_y_enable=NO # Set to YES to do fsck -y if the initial preen fails. fsck_y_flags= # Additional flags for fsck -y The reason for this to get interactively is because this might messup with your filesystem, and you are the one responsible for your filesystem, not us or the autmated system. So in case you want to play with that, that's entirely up to you. In addition, I can imagine that companies (been there done it) do not want to fsck -y by default, this because of the mentioned potential corruption and dataloss. Very important point. As an addition, allow me to mention background_fsck=YES as an entry in /etc/rc.conf. This will let the system boot up and perform fsck checks while the system is running - running on a maybe defective or inconsistent file system. This is dangerous, but possible. It utilizes a snapshot mechanism which can cause further trouble (lost / emptyinodes and disappearing subtrees of files). Personally, if fsck requires YOUR attention, there's usually a reason for this. The reason is possible data loss or file system corruption where YOU take the responsibility of decision, not fsck. By default, fsck does not do damaging, but under strange circumstances, it can happen. For example, if you want to do a special kind of data recovery or forensic analysis on a file system, you potentially DO NOT WANT fsck to assume y for all the questions because that can make your job harder. A common additional y flag is -f (means fsck -yf) to force all operations suggested by fsck and confirming them. I have had two systems die with bad disks. This email contains great information and spot-on advice from my experience. When I was ready to give up on my last system I did a -yf in single user mode and was able to get most of my data because the bad sectors were in /usr/local which had many missing files and directories. Modern disks die silently which I think is too bad. If this is happening and you have data you want to recover you might try booting in single user move and using fsck manually on each slice. If you are lucky, your errors will be in /tmp or /var. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
syncer hemorrhages numbers on shutdown then panics
I just did a 'new huge disk' procedure (aka dump 0aLf - | restore - for each label). I have a script for automating it, and it usually seems to work, but not today! Silent failures/corruptions do not make me comfortable, especially coming from my backup tools (yes, no errors seen in log). System seems to work, but it won't shutdown! syncher spits out random numbers for 10 minutes or more then panics. Should I start over? Why didn't dump/restore unambiguously copy my working disk to my new one? I didn't see any expicit errors... Also, X won't start, complaining about inability to write something for the keymap into /tmp; probably part of the same problem. Stranger still, an rsync -n from one disk to the other seems to agree that the two match! Thanks, Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: syncer hemorrhages numbers on shutdown then panics
On Mon, 5 Jul 2010, Steve Franks wrote: I just did a 'new huge disk' procedure (aka dump 0aLf - | restore - for each label). I have a script for automating it, and it usually seems to work, but not today! Silent failures/corruptions do not make me comfortable, especially coming from my backup tools (yes, no errors seen in log). System seems to work, but it won't shutdown! syncher spits out random numbers for 10 minutes or more then panics. Should I start over? Why didn't dump/restore unambiguously copy my working disk to my new one? I didn't see any expicit errors... Also, X won't start, complaining about inability to write something for the keymap into /tmp; probably part of the same problem. Maybe missing permissions on /tmp? In my case, when I don't bother to copy /tmp, create a new /tmp on the target, then forget to set permissions on it. Wouldn't think that would affect sync, but when you image a system odd things are possible. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Atheros AR8131 Ethernet hangs shutdown
CyberLeo Kitsana cyber...@cyberleo.net wrote: ... Alas, this box lacks obvious serial ports. If you don't mind taking it apart, there's a fair chance of finding a 3- or 9-pin SIO header on the circuit board. It may be TTL level rather than RS232, however. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Atheros AR8131 Ethernet hangs shutdown
On 06/07/2010 08:03 AM, Warren Block wrote: On Mon, 7 Jun 2010, CyberLeo Kitsana wrote: I recently had the chance to play with a Foxconn NetBox-nT330i. It's based off an Atom 330 CPU and an nForce MCP79 chipset. All aspects of this device appear to function quite well with 8.1-BETA1, and it's diminutive stature is quite cute. The only issue I have encountered with it thus far is a seeming propensity for it to lock up on shutdown or reboot if the Atheros AR8131 ethernet adapter is not connected to anything. It gets as far as displaying the 'Uptime' line, then hangs; however, when connected, it will display the uptime message, then indicate that the alc0 interface is going UP and DOWN, then continue. If it's like the alc setup on an Acer Aspire One D250, the 10/100 alc chip is used with a 10/100/1000 Atheros PHY. Don't remember the exact symptoms, but it only worked right after manually setting the media to 100baseTX. That was on a gigabit network, but might also help with no cable connected. Rebuilding the kernel without the alc device ought to also work, but is less elegant. I'm fairly certain it's gigabit the whole way, as I get transfer rates greater than 12 megabytes per second. Unfortunately, forcing the phy to 100baseTX/full-duplex does not alter the symptoms at all, and just makes transfers slower. On one of the tests, issuing a shutdown -p after unplugging the ethernet cord caused it to panic and reboot at the point it usually freezes, and thereafter freeze during startup when running netif; I wasn't able to copy down the panic info, though, as the reboot happened within half a second. Alas, this box lacks obvious serial ports. I may investigate building the kernel without the alc device, though, and see if unloading the kld prior to shutdown allows the system to continue past that point. Thanks for the suggestions! -- Fuzzy love, -CyberLeo Technical Administrator CyberLeo.Net Webhosting http://www.CyberLeo.Net cyber...@cyberleo.net Furry Peace! - http://.fur.com/peace/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Atheros AR8131 Ethernet hangs shutdown
Hi! I recently had the chance to play with a Foxconn NetBox-nT330i. It's based off an Atom 330 CPU and an nForce MCP79 chipset. All aspects of this device appear to function quite well with 8.1-BETA1, and it's diminutive stature is quite cute. The only issue I have encountered with it thus far is a seeming propensity for it to lock up on shutdown or reboot if the Atheros AR8131 ethernet adapter is not connected to anything. It gets as far as displaying the 'Uptime' line, then hangs; however, when connected, it will display the uptime message, then indicate that the alc0 interface is going UP and DOWN, then continue. What sort of information would be the most helpful to collect to assist in tracking down the cause of this behaviour? If there is a better mailing list with which to consult, that too would be helpful. Thank you. -- Fuzzy love, -CyberLeo Technical Administrator CyberLeo.Net Webhosting http://www.CyberLeo.Net cyber...@cyberleo.net Furry Peace! - http://.fur.com/peace/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Atheros AR8131 Ethernet hangs shutdown
On Mon, 7 Jun 2010, CyberLeo Kitsana wrote: I recently had the chance to play with a Foxconn NetBox-nT330i. It's based off an Atom 330 CPU and an nForce MCP79 chipset. All aspects of this device appear to function quite well with 8.1-BETA1, and it's diminutive stature is quite cute. The only issue I have encountered with it thus far is a seeming propensity for it to lock up on shutdown or reboot if the Atheros AR8131 ethernet adapter is not connected to anything. It gets as far as displaying the 'Uptime' line, then hangs; however, when connected, it will display the uptime message, then indicate that the alc0 interface is going UP and DOWN, then continue. If it's like the alc setup on an Acer Aspire One D250, the 10/100 alc chip is used with a 10/100/1000 Atheros PHY. Don't remember the exact symptoms, but it only worked right after manually setting the media to 100baseTX. That was on a gigabit network, but might also help with no cable connected. Rebuilding the kernel without the alc device ought to also work, but is less elegant. -Warren Block * Rapid City, South Dakota USA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Automatic shutdown with devd.
On Tue, 1 Jun 2010, David DEMELIER wrote: 2010/6/1 Ian Smith smi...@nimnet.asn.au: In freebsd-questions Digest, Vol 313, Issue 4, Message: 26 On Tue, 1 Jun 2010 10:55:08 +0200 David DEMELIER demelier.da...@gmail.com wrote: [..] Is there a way to make this conditional to do only if the laptop is not charging, AC plugged in ? Your script can check whether the AC power is on with: AC=`sysctl -n hw.acpi.acline` if [ $AC = 1 ]; then exit 0 # or whatever, when on AC power elif [ $AC = 0 ]; then : # do whatever when on battery else : # AC/Battery state unknown .. fi You could try just logging all state changes for a while; from critical charging to charging to high to discharging to critical discharging, I think that's the lot .. you can also check hw.acpi.battery.life etc. Okay I will try a script like this one. Let us know how it goes; it's clearer now from below why you need this. However, your system should do an 'emergency suspend' on critical low battery anyway .. usually set at 1% capacity but some BIOS will let you adjust that (see acpiconf -i0). Only if suspend/resume works of course. It would be great if suspend/resume would works yes ! For the moment it's not the case : http://www.freebsd.org/cgi/query-pr.cgi?pr=i386/146715 Ah yes. I guess you might have to try the freebsd-acpi list about that, after reading the ACPI debugging section of the Handbook, providing your dmesg and probably an acpidump of your ASL as shown there. I don't know the current status of suspend/resume on amd64, nor anything about your HP Probook 4510s. The freebsd-mobile list might be a better place to start, at least to ask whether anyone else shares your problem? cheers, Ian___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Automatic shutdown with devd.
Hi,
I recently asked to make an automatic shutdown when I excess a
specific percent. I ran devd with -Dd flags to run in background and
when the battery was at a critical state it said :
Processing event '!system=ACPI subsystem=CMBAT type=\_SB_.BAT0 notify=0x80'
Pushing table
setting system=ACPI
setting subsystem=CMBAT
setting type=\_SB_.BAT0
setting notify=0x80
Then I tried (for testing) something like this in my /etc/devd.conf
notify 10 {
match system ACPI;
match subsystem CMBAT;
match notify 0x80;
action logger LETGOSHUTDOWN;
};
And then I can see the following output in /var/log/messages :
Jun 1 10:48:54 Melon power_profile: changed to 'performance'
Jun 1 10:48:56 Melon root: LETGOSHUTDOWN
Jun 1 10:49:12 Melon root: LETGOSHUTDOWN
Jun 1 10:51:06 Melon last message repeated 2 times
It works, but the problem is that it makes this even the cable is
plugged ! i.e : the computer was not powered on so with 3% of
remaining time but AC plugged in after booting it (always with the AC
plugged in) these messages appears too. I guess the ACPI/CMBAT do not
care if there is an AC plugged in or not.
Is there a way to make this conditional to do only if the laptop is
not charging, AC plugged in ?
With king regards.
--
Demelier David
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Automatic shutdown with devd.
In freebsd-questions Digest, Vol 313, Issue 4, Message: 26
On Tue, 1 Jun 2010 10:55:08 +0200 David DEMELIER demelier.da...@gmail.com
wrote:
I recently asked to make an automatic shutdown when I excess a
specific percent. I ran devd with -Dd flags to run in background and
when the battery was at a critical state it said :
Processing event '!system=ACPI subsystem=CMBAT type=\_SB_.BAT0 notify=0x80'
Pushing table
setting system=ACPI
setting subsystem=CMBAT
setting type=\_SB_.BAT0
setting notify=0x80
You should be aware that notify 0x80 for CMBAT indicates 'BST' or
Battery State Change; you'll get these on shifting to any new state.
You can check the new state with 'sysctl -n hw.acpi.battery.state'.
'acpiconf -i0' shows a translation between state masks and names.
Then I tried (for testing) something like this in my /etc/devd.conf
notify 10 {
match system ACPI;
match subsystem CMBAT;
match notify 0x80;
action logger LETGOSHUTDOWN;
};
And then I can see the following output in /var/log/messages :
Jun 1 10:48:54 Melon power_profile: changed to 'performance'
Reflecting your AC line state changing from Battery to AC. devd.conf
and /etc/rc.d/power_profile have good clues for handling devd notifies.
Jun 1 10:48:56 Melon root: LETGOSHUTDOWN
Jun 1 10:49:12 Melon root: LETGOSHUTDOWN
Jun 1 10:51:06 Melon last message repeated 2 times
It works, but the problem is that it makes this even the cable is
plugged ! i.e : the computer was not powered on so with 3% of
remaining time but AC plugged in after booting it (always with the AC
plugged in) these messages appears too. I guess the ACPI/CMBAT do not
care if there is an AC plugged in or not.
See /sys/dev/acpica/acpi_cmbat.c for the gory details.
Yes, ACAD and CMBAT are independent subsystems, so rather than an inline
action like logger .. here, you might follow the examples to run your
own script, passing the notify to that (if you may also want to check
for notify 0x81, BIF battery info changes, though these occur rarely)
Is there a way to make this conditional to do only if the laptop is
not charging, AC plugged in ?
Your script can check whether the AC power is on with:
AC=`sysctl -n hw.acpi.acline`
if [ $AC = 1 ]; then
exit 0 # or whatever, when on AC power
elif [ $AC = 0 ]; then
: # do whatever when on battery
else
: # AC/Battery state unknown ..
fi
You could try just logging all state changes for a while; from critical
charging to charging to high to discharging to critical discharging, I
think that's the lot .. you can also check hw.acpi.battery.life etc.
However, your system should do an 'emergency suspend' on critical low
battery anyway .. usually set at 1% capacity but some BIOS will let you
adjust that (see acpiconf -i0). Only if suspend/resume works of course.
cheers, Ian
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Automatic shutdown with devd.
2010/6/1 Ian Smith smi...@nimnet.asn.au:
In freebsd-questions Digest, Vol 313, Issue 4, Message: 26
On Tue, 1 Jun 2010 10:55:08 +0200 David DEMELIER demelier.da...@gmail.com
wrote:
I recently asked to make an automatic shutdown when I excess a
specific percent. I ran devd with -Dd flags to run in background and
when the battery was at a critical state it said :
Processing event '!system=ACPI subsystem=CMBAT type=\_SB_.BAT0 notify=0x80'
Pushing table
setting system=ACPI
setting subsystem=CMBAT
setting type=\_SB_.BAT0
setting notify=0x80
You should be aware that notify 0x80 for CMBAT indicates 'BST' or
Battery State Change; you'll get these on shifting to any new state.
You can check the new state with 'sysctl -n hw.acpi.battery.state'.
'acpiconf -i0' shows a translation between state masks and names.
Then I tried (for testing) something like this in my /etc/devd.conf
notify 10 {
match system ACPI;
match subsystem CMBAT;
match notify 0x80;
action logger LETGOSHUTDOWN;
};
And then I can see the following output in /var/log/messages :
Jun 1 10:48:54 Melon power_profile: changed to 'performance'
Reflecting your AC line state changing from Battery to AC. devd.conf
and /etc/rc.d/power_profile have good clues for handling devd notifies.
Jun 1 10:48:56 Melon root: LETGOSHUTDOWN
Jun 1 10:49:12 Melon root: LETGOSHUTDOWN
Jun 1 10:51:06 Melon last message repeated 2 times
It works, but the problem is that it makes this even the cable is
plugged ! i.e : the computer was not powered on so with 3% of
remaining time but AC plugged in after booting it (always with the AC
plugged in) these messages appears too. I guess the ACPI/CMBAT do not
care if there is an AC plugged in or not.
See /sys/dev/acpica/acpi_cmbat.c for the gory details.
Yes, ACAD and CMBAT are independent subsystems, so rather than an inline
action like logger .. here, you might follow the examples to run your
own script, passing the notify to that (if you may also want to check
for notify 0x81, BIF battery info changes, though these occur rarely)
So I will check deeper.
Is there a way to make this conditional to do only if the laptop is
not charging, AC plugged in ?
Your script can check whether the AC power is on with:
AC=`sysctl -n hw.acpi.acline`
if [ $AC = 1 ]; then
exit 0 # or whatever, when on AC power
elif [ $AC = 0 ]; then
: # do whatever when on battery
else
: # AC/Battery state unknown ..
fi
You could try just logging all state changes for a while; from critical
charging to charging to high to discharging to critical discharging, I
think that's the lot .. you can also check hw.acpi.battery.life etc.
Okay I will try a script like this one.
However, your system should do an 'emergency suspend' on critical low
battery anyway .. usually set at 1% capacity but some BIOS will let you
adjust that (see acpiconf -i0). Only if suspend/resume works of course.
It would be great if suspend/resume would works yes ! For the moment
it's not the case :
http://www.freebsd.org/cgi/query-pr.cgi?pr=i386/146715
Thanks for your answer ;-)
--
Demelier David
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
server gnome disallow normal user to shutdown
If a FreeBSD8.0/Gnome system is a server, with many individual users, I don't want a normal user to be able to do a restart or shutdown or hibernate etc... Now any user has the possibility to do that via System / Shutdown How to disallow that globally? (except for e.g. the users in the group wheel) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: server gnome disallow normal user to shutdown
On Mon, Mar 29, 2010 at 4:55 AM, n dhert ndhert...@gmail.com wrote: If a FreeBSD8.0/Gnome system is a server, with many individual users, I don't want a normal user to be able to do a restart or shutdown or hibernate etc... Now any user has the possibility to do that via System / Shutdown How to disallow that globally? (except for e.g. the users in the group wheel) I think the option doesn't work even for wheel users. I mean it's there but in my system it just logs the user out. Anyway you can disble the menu option with gnome configuration. http://www.freebsd.org/gnome/ and google things like this customize gnome desktop menus Best, Alejandro Imass ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Shutdown
I have completely lost the ability to shutdown/reboot/logout... I've found a few pages on this issue, and nothing seems to resolve the issue. I'm in wheel, operator groups, hal, dbus, gnome_enable all set... consolekit showing a token, proc mounted... and still nothing... what else could be wrong? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Shutdown
On Mon, 1 Feb 2010, Jeff Molofee wrote: I have completely lost the ability to shutdown/reboot/logout... I've found a few pages on this issue, and nothing seems to resolve the issue. I'm in wheel, operator groups, hal, dbus, gnome_enable all set... consolekit showing a token, proc mounted... and still nothing... what else could be wrong? How are you trying to trigger a shutdown, and in what environment? There are PolicyKit settings you need: http://groups.google.com/group/comp.unix.bsd.freebsd.misc/msg/0d049accfb7fa387?dmode=source There was that recent policykit/polkit port upgrade, too. -Warren Block * Rapid City, South Dakota USA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Shutdown
Hi, On 02 February 2010 am 10:18:28 Jeff Molofee wrote: I have completely lost the ability to shutdown/reboot/logout... I've found a few pages on this issue, and nothing seems to resolve the issue. I'm in wheel, operator groups, hal, dbus, gnome_enable all set... consolekit showing a token, proc mounted... and still nothing... what else could be wrong? what happens when you enter shutdown -p now in a console? There should be some message? Erich ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
No History after shutdown -h on FBSD 8 or 9
Aloha, Is there a reason the history no longer stays in memory on FreeBSD 8 9? Reko Turja sent me a work around for a reboot: shutdown -r +1 logout or shutdown -h +1 logout Both of the above work to save the history in a tcsh shell. We used to be able to use: shutdown -h now Is this not going to be possible from FreeBSD 8 onward? Thanks... ~Al Plant - Honolulu, Hawaii - Phone: 808-284-2740 + http://hawaiidakine.com + http://freebsdinfo.org + + http://aloha50.net - Supporting - FreeBSD 6.* - 7.* - 8.* + email: n...@hdk5.net All that's really worth doing is what we do for others.- Lewis Carrol ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
geli disk marked as dirty on normal shutdown/reboot
Hi List, # uname -a FreeBSD the.palaceofretention.ca 7.1-RELEASE-p6 FreeBSD 7.1-RELEASE-p6 #0: Tue Jun 9 16:26:47 UTC 2009 r...@i386-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC i386 I have a geli backed ufs file system: ===fstab=== # ad14.eli esata /dev/ufs/E1TB /edisks/esata0 ufs rw,noauto2 2 I use a passphrase to attach it: # geli attach ad14 Enter passphrase: ** The provider shows up as ad14.eli as expected. The file system on it has a label of E1TB (as seen above). The command: # mount /dev/ufs/E1TB usually works fine. The problem is that if I restart the system normally, the file system on the provider ad14.eli, when reattached, is marked as dirty and I get the usual operation not permitted error. I have to run: # fsck -t ufs /dev/ad14.eli before I can mount it again. This is repeatable and occurs for more than just the one geli provider I use in this example. Am I missing something with respect to properly attaching a geli device? Do I need the '-d' option to detach at last close? Thanks for any help. Vinny ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: geli disk marked as dirty on normal shutdown/reboot
On Mon, Aug 31, 2009 at 8:05 PM, Vinny vinny-mail-01+f.questions20090...@palaceofretention.cavinny-mail-01%2bf.questions20090...@palaceofretention.ca wrote: Hi List, # uname -a FreeBSD the.palaceofretention.ca 7.1-RELEASE-p6 FreeBSD 7.1-RELEASE-p6 #0: Tue Jun 9 16:26:47 UTC 2009 r...@i386-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC i386 I have a geli backed ufs file system: ===fstab=== # ad14.eli esata /dev/ufs/E1TB /edisks/esata0 ufs rw,noauto2 2 I use a passphrase to attach it: # geli attach ad14 Enter passphrase: ** The provider shows up as ad14.eli as expected. The file system on it has a label of E1TB (as seen above). The command: # mount /dev/ufs/E1TB usually works fine. The problem is that if I restart the system normally, the file system on the provider ad14.eli, when reattached, is marked as dirty and I get the usual operation not permitted error. I have to run: # fsck -t ufs /dev/ad14.eli before I can mount it again. This is repeatable and occurs for more than just the one geli provider I use in this example. Am I missing something with respect to properly attaching a geli device? Do I need the '-d' option to detach at last close? Thanks for any help. Vinny ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org Usually I just umount before close. I don't get the need to fsck then. -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: geli disk marked as dirty on normal shutdown/reboot
On Mon, 31 Aug 2009 21:22:14 -0500, Adam Vande More amvandem...@gmail.com wrote: Usually I just umount before close. I don't get the need to fsck then. You could add the umount command to /etc/rc.shutdown.local so the system would automatically umount the partition, even if you reboot. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: geli disk marked as dirty on normal shutdown/reboot
Polytropon wrote: On Mon, 31 Aug 2009 21:22:14 -0500, Adam Vande More amvandem...@gmail.com wrote: Usually I just umount before close. I don't get the need to fsck then. Does this mean you observe the same behaviour? I.e. a geli-backed file system mounted and listed in the fstab is not properly unmounted at shutdown? You could add the umount command to /etc/rc.shutdown.local so the system would automatically umount the partition, even if you reboot. It is my understanding that file systems listed in the /etc/fstab file are unmounted at system shutdown. Is this correct? If not, that would be a pretty big WTF?, if you ask me. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: gmirror per partition. Was: Re: gmirror gm0 destroyed on shutdown; GPT corrupt
On Wed, Jul 01, 2009 at 10:00:54PM +0200, Wojciech Puchar wrote: It's better to use gmirror per partition. Like this? # gmirror label -vb round-robin root /dev/da0p2 gmirror: Can't store metadata on /dev/da0p2: Operation not permitted. isn't that partition accessed by other process or mounted? should it not be mounted? Sorry, I was just following the handbook, but I now understand it is incorrect when it comes to ia64. many thanks anton ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 928 8233 Fax: +44 (0)117 929 4423 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: gmirror per partition. Was: Re: gmirror gm0 destroyed on shutdown; GPT corrupt
# gmirror label -vb round-robin root /dev/da0p2 gmirror: Can't store metadata on /dev/da0p2: Operation not permitted. isn't that partition accessed by other process or mounted? should it not be mounted? yes it should not, no matter what architecture. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
gmirror per partition. Was: Re: gmirror gm0 destroyed on shutdown; GPT corrupt
On Thu, Jun 25, 2009 at 09:41:13AM -0700, Marcel Moolenaar wrote: On Jun 25, 2009, at 4:02 AM, Anton Shterenlikht wrote: dev_taste(DEV,mirror/gm0) g_part_taste(PART,mirror/gm0) GEOM: mirror/gm0: the secondary GPT table is corrupt or invalid. GEOM: mirror/gm0: using the primary only -- recovery suggested. ^^^ You created the mirror after the GPT, which means you destroyed the GPT backup header. gmirror uses the last sector on the disk for metadata and that by itself is a cause for various problems. It's better to use gmirror per partition. Like this? # gmirror label -vb round-robin root /dev/da0p2 gmirror: Can't store metadata on /dev/da0p2: Operation not permitted. # I've read some boot disk gmirror examples, e.g. http://people.freebsd.org/~rse/mirror however, all examples I've seen are for i386, talking about MBR, fdisk and bsdlabel, so these are not directly applicable to ia64. Application of gvinum for boot disk on ia64 is not clear either. It seems gvinum section of the handbook, 21.9, is also based on i386. Please advise many thanks anton -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 928 8233 Fax: +44 (0)117 929 4423 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: gmirror per partition. Was: Re: gmirror gm0 destroyed on shutdown; GPT corrupt
It's better to use gmirror per partition. Like this? # gmirror label -vb round-robin root /dev/da0p2 gmirror: Can't store metadata on /dev/da0p2: Operation not permitted. isn't that partition accessed by other process or mounted? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: gmirror gm0 destroyed on shutdown; GPT corrupt
Hi, On 28.06.2009, at 10:49, Pawel Jakub Dawidek wrote: I for one never put mirror on already partitioned disk. Although it is sometimes safe to use the last sector. Gjournal already looks for UFS and if UFS is in place, it figures out if the last sector is in use - it isn't if partition size is not multiple of UFS block size. does this actually also mean that gmirror used on a partition (eg mirroring two partitions of two different disks) is not recommended and is going to write its metadata always on the last sector of the disk, instead of the last sector of the partition? regards, Lorenzo ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: gmirror gm0 destroyed on shutdown; GPT corrupt
On Thu, Jun 25, 2009 at 09:41:13AM -0700, Marcel Moolenaar wrote: On Jun 25, 2009, at 4:02 AM, Anton Shterenlikht wrote: dev_taste(DEV,mirror/gm0) g_part_taste(PART,mirror/gm0) GEOM: mirror/gm0: the secondary GPT table is corrupt or invalid. GEOM: mirror/gm0: using the primary only -- recovery suggested. ^^^ You created the mirror after the GPT, which means you destroyed the GPT backup header. gmirror uses the last sector on the disk for metadata and that by itself is a cause for various problems. So, gmirror cannot be used on ia64 to mirror the boot disk? Because on ia64 the last sector always contains secondary GPT. I take it the RAID1 section, 19.4, in FBSD user manual, was written with i386 or alpha architecture in mind. It's better to use gmirror per partition. how? Is it in the manual? any link? #echo 'geom_mirror_load=YES' /boot/loader.conf Is /boot a symlink for /efi/boot? yes, lrwxr-xr-x 1 root wheel 8 Jun 25 10:44 boot - efi/boot And when the system is rebooted, there is no /dev/mirror anymore. You could run into a race condition between GPT and gmirror and GPT winning (again the result of gmirror using the last sector on a disk for metadata). Alternatively, make sure gmirror got loaded at boot. # kldstat Id Refs AddressSize Name 13 0xe400 ff9c08 kernel 21 0xe4ffa000 3c830geom_mirror.ko # It's not that I desperately need to mirror a boot disk, it just that gmirror looked so easy in the manual, I wanted to give it a go. Perhaps I can just do a block copy to the second disk, say once a day, and have it as a backup. Could you also possibly comment on gvinum on ia64? many thanks anton -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 928 8233 Fax: +44 (0)117 929 4423 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: gmirror gm0 destroyed on shutdown; GPT corrupt
On Sat, Jun 27, 2009 at 06:20:49PM -0700, Marcel Moolenaar wrote: Using the last sector is not only flawed because it creates a race condition, it's flawed in the assumption that you can always make a geom part of a mirror by storing meta-data on the geom without causing corruption. This whole idea of using the last sector was so that a fully partitioned disk with data could be turned into a mirrored disk. A neat idea, but hardly the basis for a generic mirroring implementation when it silently corrupts a disk. This wasn't the idea:) People started putting gmirror on top of partitioned disk, because it was easier/simpler/faster than creating mirror, partitioning and copying the data. I for one never put mirror on already partitioned disk. Although it is sometimes safe to use the last sector. Gjournal already looks for UFS and if UFS is in place, it figures out if the last sector is in use - it isn't if partition size is not multiple of UFS block size. I think it's better to change gmirror to use the first sector on the provider. This never creates a race condition and as such, you don't need to invent a priority scheme, that has it's own set of flaws on top of it. The only downside is that it's not easy to make a fully partitioned and populated disk part of a mirror: one would need to move the data forward one sector to free the first sector. This we can actually do by inserting a GEOM that does it while I/O is still ongoing. The good thing is: we need a class that does exactly this for implementing the move verb in gpart. There were two reasons to use the last sector instead of first: 1. You want to be able to boot from gmirror. If all your data will be moved forward your boot sectors and kernel will be harder to find. 2. For recovery reasons you may want to turn off gmirror and still be able to access your data. Note that gmirror can handle the case where disk, slice and partition share the same last sector - it simply stores provider size in its metadata, so once it gets disk for tasting it detects its too big and ignores it, then slice will be given for tasting, but it also has larger size than expected and will be ignored as well. Finally partition will be tasted and gmirror configured. -- Pawel Jakub Dawidek http://www.wheel.pl p...@freebsd.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! pgpXtFT4O58hK.pgp Description: PGP signature
Re: gmirror gm0 destroyed on shutdown; GPT corrupt
2009/6/28 Marcel Moolenaar xcl...@mac.com: Using the last sector is not only flawed because it creates a race condition, it's flawed in the assumption that you can always make a geom part of a mirror by storing meta-data on the geom without causing corruption. This whole idea of using the last sector was so that a fully partitioned disk with data could be turned into a mirrored disk. A neat idea, but hardly the basis for a generic mirroring implementation when it silently corrupts a disk. I think it's better to change gmirror to use the first sector on the provider. Yes, it would be cleaner to implement but it would also make the mirrored devices unbootable. But maybe the class of users needing the functionality is smaller now. This never creates a race condition and as such, you don't need to invent a priority scheme, that has it's own set of flaws on top of it. The only downside is that it's not easy to make a fully partitioned and populated disk part of a mirror: one would need to move the data forward one sector to free the first sector. This we can actually do by inserting a GEOM that does it while I/O is still ongoing. The good thing is: we need a class that does exactly this for implementing the move verb in gpart. Looks too complicated and fragile. Maybe there's a need for metadata-less automatic mirrors in some way, by storing the configuration somewhere else, possibly in /etc. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: gmirror gm0 destroyed on shutdown; GPT corrupt
Ivan Voras wrote: Yes, it would be cleaner to implement but it would also make the mirrored devices unbootable. But maybe the class of users needing the functionality is smaller now. Most dedicated server providers can't afford to use hardware RAID systems because that would drastically increase the price of a single system; yet many customers want mirroring. Looks too complicated and fragile. Maybe there's a need for metadata-less automatic mirrors in some way, by storing the configuration somewhere else, possibly in /etc. This might be dangerous in some cases. Imagine booting with two drives swapped; such a configuration might lead to data corruption on a volume which was enumerated incorrectly or swapped. -- Kamigishi Rei KREI-RIPE ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: gmirror gm0 destroyed on shutdown; GPT corrupt
On Jun 27, 2009, at 4:15 AM, Ivan Voras wrote: Marcel Moolenaar wrote: On Jun 25, 2009, at 4:02 AM, Anton Shterenlikht wrote: dev_taste(DEV,mirror/gm0) g_part_taste(PART,mirror/gm0) GEOM: mirror/gm0: the secondary GPT table is corrupt or invalid. GEOM: mirror/gm0: using the primary only -- recovery suggested. ^^^ You created the mirror after the GPT, which means you destroyed the GPT backup header. gmirror uses the last sector on the disk for metadata and that by itself is a cause for various problems. It's better to use gmirror per partition. Or create the GPT partition inside the gmirror device - then the GPT backup table will be at last_sector-1, but... You could run into a race condition between GPT and gmirror and GPT winning (again the result of gmirror using the last sector on a disk for metadata). unfortunately this could still happen, and will lead to the same error if GPT is tasted first, since it is embedded in the first sector and will assume the whole drive is available to GPT, and will then proceed to not find its backup data in the last sector. It looks to me like GEOM classes should have a priority field for tasting. Any objections to that idea? Using the last sector is not only flawed because it creates a race condition, it's flawed in the assumption that you can always make a geom part of a mirror by storing meta-data on the geom without causing corruption. This whole idea of using the last sector was so that a fully partitioned disk with data could be turned into a mirrored disk. A neat idea, but hardly the basis for a generic mirroring implementation when it silently corrupts a disk. I think it's better to change gmirror to use the first sector on the provider. This never creates a race condition and as such, you don't need to invent a priority scheme, that has it's own set of flaws on top of it. The only downside is that it's not easy to make a fully partitioned and populated disk part of a mirror: one would need to move the data forward one sector to free the first sector. This we can actually do by inserting a GEOM that does it while I/O is still ongoing. The good thing is: we need a class that does exactly this for implementing the move verb in gpart. In other words: Solving the problem that putting the metadata in the first sector creates, can and will be re-used in implementing the gpart move partition feature. I doubt anyone will complain that the creation of a mirror brings with it a few hours of disk activity that does not inhibit normal operation... -- Marcel Moolenaar xcl...@mac.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
gmirror gm0 destroyed on shutdown; GPT corrupt
/4a43468b228d030c) g_mirror_taste(MIRROR, ufsid/4a43468c8715f453) g_detach(0xe000108fd100) g_destroy_consumer(0xe000108fd100) g_destroy_geom(0xe000108f8100(mirror:taste)) dev_taste(DEV,ufsid/4a43468c8715f453) g_part_taste(PART,ufsid/4a43468c8715f453) g_wither_geom(0xe00010724a00(ufsid/4a43468c8715f453)) g_label_taste(LABEL, ufsid/4a43468c8715f453) g_detach(0xe000106ea680) g_destroy_consumer(0xe000106ea680) g_destroy_geom(0xe00010724a00(ufsid/4a43468c8715f453)) g_detach(0xe000108fd000) g_destroy_consumer(0xe000108fd000) g_destroy_geom(0xe0001081dc00(ufsid/4a43468b228d030c)) g_detach(0xe00010739280) g_destroy_consumer(0xe00010739280) g_destroy_geom(0xe00010724800(ufsid/4a43468cf6208bf0)) g_detach(0xe000106eb880) g_destroy_consumer(0xe000106eb880) g_destroy_geom(0xe00010724600(ufsid/4a43468a267a63a6)) g_detach(0xe00010738000) g_destroy_consumer(0xe00010738000) g_destroy_geom(0xe000108f8200(mirror/gm0p6)) g_detach(0xe000106a4900) g_destroy_consumer(0xe000106a4900) g_destroy_geom(0xe00010724e00(mirror/gm0p5)) g_detach(0xe000108fc700) g_destroy_consumer(0xe000108fc700) g_destroy_geom(0xe00010762a00(mirror/gm0p4)) g_detach(0xe000108fc480) g_destroy_consumer(0xe000108fc480) g_destroy_geom(0xe0001075ed00(mirror/gm0p3)) g_detach(0xe000108fc200) g_destroy_consumer(0xe000108fc200) g_destroy_geom(0xe0001072c800(mirror/gm0p2)) g_detach(0xe00010739c80) g_destroy_consumer(0xe00010739c80) g_destroy_geom(0xe00010763a00(mirror/gm0p1)) # ls -al /dev/mirror/ total 1 dr-xr-xr-x 2 root wheel 512 Jun 25 11:16 . dr-xr-xr-x 9 root wheel 512 Jun 25 11:22 .. crw-r- 1 root operator0, 105 Jun 25 11:16 gm0 crw-r- 1 root operator0, 116 Jun 25 11:16 gm0p1 crw-r- 1 root operator0, 117 Jun 25 11:16 gm0p2 crw-r- 1 root operator0, 118 Jun 25 11:16 gm0p3 crw-r- 1 root operator0, 119 Jun 25 11:16 gm0p4 crw-r- 1 root operator0, 120 Jun 25 11:16 gm0p5 crw-r- 1 root operator0, 121 Jun 25 11:16 gm0p6 # #echo 'geom_mirror_load=YES' /boot/loader.conf # cat /boot/loader.conf vfs.root.mountfrom=ufs:/dev/da0p2 geom_mirror_load=YES # On shutdown I see on console: [skip] g_detach(0xe000106c7000) g_destroy_consumer(0xe000106c7000) g_destroy_geom(0xe000106c3200(mirror/gm0p2)) g_destroy_geom(0xe00010828200(mirror/gm0)) g_post_event_x(0xe4c33e70, 0xe000106c6d80, 2, 0) g_wither_geom(0xe000106efa00(gm0.sync)) GEOM_MIRROR: Device gm0 destroyed. ^ g_wither_geom(0xe00010826900(gm0)) g_detach(0xe000106c6d80) g_destroy_consumer(0xe000106c6d80) g_destroy_geom(0xe000106efa00(gm0.sync)) g_destroy_geom(0xe00010826900(gm0)) And when the system is rebooted, there is no /dev/mirror anymore. Please advise many thanks -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 928 8233 Fax: +44 (0)117 929 4423 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: gmirror gm0 destroyed on shutdown; GPT corrupt
On Jun 25, 2009, at 4:02 AM, Anton Shterenlikht wrote: dev_taste(DEV,mirror/gm0) g_part_taste(PART,mirror/gm0) GEOM: mirror/gm0: the secondary GPT table is corrupt or invalid. GEOM: mirror/gm0: using the primary only -- recovery suggested. ^^^ You created the mirror after the GPT, which means you destroyed the GPT backup header. gmirror uses the last sector on the disk for metadata and that by itself is a cause for various problems. It's better to use gmirror per partition. #echo 'geom_mirror_load=YES' /boot/loader.conf Is /boot a symlink for /efi/boot? GEOM_MIRROR: Device gm0 destroyed. ^ This is normal. And when the system is rebooted, there is no /dev/mirror anymore. You could run into a race condition between GPT and gmirror and GPT winning (again the result of gmirror using the last sector on a disk for metadata). Alternatively, make sure gmirror got loaded at boot. FYI, -- Marcel Moolenaar xcl...@mac.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
No shutdown reboot
I am running FreeBSD 7.2 - stable and update regularly. Following a recent update, I am now unable to shutdown or reboot my compute= r using reboot, shutdown -r now, halt -p or shutdown -p now. This has always worked before. Instead of shutting down or rebooting, the computer appears to halt, and st= ops with the uptime message. There are no error messages. Cheers DuncanB _ Área de Clientes Clix – Toda a gestão dos seus servi�= �os online! http://cliente.clix.pt/. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
shutdown -p does not power off
Hi all: My problem is that I type shutdown -p now command, and system hang after uptime show on screen. I must press reset or press power sw 4 sec to poweroff. But reboot command works fine for me. I found it caused when hald_enable set to YES in rc.conf, if hald_enable set to NO everything works fine. hald is required for my desktop environment. Any suggestions ? My kernel version is FreeBSD 7.1-RELEASE #5 amd64. Thanks, Dsewnr Lu ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
FreeBSD 8.0-CUURENT/amd64 coredumps when shutdown
Hello. I have a difficult problem and apart from possible hardware problems I need to track down problems. My lab's box is a Intel Q6600 driven box with a ASUS P5K-Deluxe WiFi mainboard (Intel P35 chipset, ICH9, 8GB DDR2-800 RAM). Symptomatics: Whenever I shutdown or reboot the box, it dumps a core! This happens only if the box is in multiuser mode. First I suspected the new 'drm' code, but disabling every module loading and even with X11-free environment the box dies when shutting down or reboot. The weir thing is: I realised this faulty behaviour before the upgrade to FreeBSD 6.0-CURRENT/amd64 I did last week when the box ran FreeBSD 7.1-STABLE/amd64. Whenever I left a Xsession, the box died. Whenever I rebootet it, the box died. I already checked cabling and SMART logs of the harddrives making sure there is no issue with lost blocks or similar. Then I tried testing memory, but also with no success finding an issue. A weird behaviour is: whenever I load drm.ko module on that box (remember, P35/ICH9/Q6600, that means NO AGP!) agp.ko gets also loaded. None of the other 8.0-CURRENT/amd64 boxes with PCIe hardware show that behaviour (most of them are older). Well, I saw this strange crashing-behaviour prior to that of my desk's box on one of our DELL PowerEdge 1950 III server days before. That box is running FreeBSD 8.0-CURRENT/amd64 on two 4-core XEONs. Whenever I rebootet that box, I got a coredump. That vanished now with the mature of the 8.0-CURRENT sourcs, but it occurs now for the desktop box. I can not provide a sophisticated core or a screendump of the log message since I need the box by the end of the week due to some conference prapartions (so all of the debugging stuff has been disabled), but I will provide more by next week if this issue seems not familiar to someone. By the way, BIOS of the board is 1101 - newest on market for that mobo. I'm open for some hints and tips tracking down the issue ... A dmesg output is provided. Regards, Oliver Copyright (c) 1992-2009 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 8.0-CURRENT #2 r189870: Mon Mar 16 09:03:05 UTC 2009 r...@telesto.geoinf.fu-berlin.de:/usr/obj/usr/src/sys/TELESTO Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Core(TM)2 Quad CPUQ6600 @ 2.40GHz (3013.58-MHz K8-class CPU) Origin = GenuineIntel Id = 0x6fb Stepping = 11 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0xe3bdSSE3,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM AMD Features=0x20100800SYSCALL,NX,LM AMD Features2=0x1LAHF TSC: P-state invariant Cores per package: 4 usable memory = 8579391488 (8181 MB) avail memory = 8283136000 (7899 MB) ACPI APIC Table: A_M_I_ OEMAPIC FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 ioapic0 Version 2.0 irqs 0-23 on motherboard kbd1 at kbdmux0 netsmb_dev: loaded cryptosoft0: software crypto on motherboard acpi0: A_M_I_ OEMXSDT on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of 0, a (3) failed acpi0: reservation of 10, cff0 (3) failed Timecounter ACPI-safe frequency 3579545 Hz quality 850 acpi_timer0: 24-bit timer at 3.579545MHz port 0x808-0x80b on acpi0 acpi_hpet0: High Precision Event Timer iomem 0xfed0-0xfed003ff on acpi0 Timecounter HPET frequency 14318180 Hz quality 900 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pcib1: ACPI PCI-PCI bridge irq 16 at device 1.0 on pci0 pci1: ACPI PCI bus on pcib1 vgapci0: VGA-compatible display port 0xb000-0xb0ff mem 0xd000-0xdfff,0xfe8e-0xfe8e irq 16 at device 0.0 on pci1 hdac0: ATI RV730 High Definition Audio Controller mem 0xfe8fc000-0xfe8f irq 17 at device 0.1 on pci1 hdac0: HDA Driver Revision: 20090226_0129 hdac0: [ITHREAD] uhci0: Intel 82801I (ICH9) USB controller port 0xa800-0xa81f irq 16 at device 26.0 on pci0 uhci0: [ITHREAD] uhci0: LegSup = 0x0f30 usbus0: Intel 82801I (ICH9) USB controller on uhci0 uhci1: Intel 82801I (ICH9) USB controller port 0xa880-0xa89f irq 21 at device 26.1 on pci0 uhci1: [ITHREAD] uhci1: LegSup = 0x0f30 usbus1: Intel 82801I (ICH9) USB controller on uhci1 uhci2: Intel 82801I (ICH9) USB controller port 0xac00-0xac1f irq 18 at device 26.2 on pci0 uhci2: [ITHREAD] uhci2: LegSup = 0x0f30 usbus2: Intel 82801I (ICH9) USB controller on uhci2 ehci0: Intel 82801I (ICH9) USB 2.0 controller mem 0xfe7ffc00-0xfe7f irq 18 at device 26.7 on pci0 ehci0: [ITHREAD] usbus3: EHCI version 1.0 usbus3: Intel 82801I (ICH9) USB 2.0 controller on ehci0 hdac1: Intel 82801I High Definition Audio Controller mem 0xfe7f8000
Suddenly shutdown -p now produces a reboot
I have a Server with Squid, 7.0-RELEASE-p4 FreeBSD, squid-3.0.11, that has been running fine for the last six months, at least. It is shutdown every night at 7 PM via cron. Now suddenly the machine is rebooting instead, and I've made no changes whatsoever. I'm wondering if this is a symptom of a coming hardware failure or if I can do something to get the normal behaviour back. I did have a similar problem when I first put the machine into production, then it was clear from /var/log/messages that squid did not have enough time to shutdown and I solved it by changeing the parameter rcshutdown_timeout=90 i rc.conf. Here's a piece of /var/log/messages --- snip Jan 1 19:05:00 server01 shutdown: power-down by root: Jan 1 19:05:33 server01 squid[823]: Squid Parent: child process 826 exited with status 0 Jan 1 19:05:34 server01 named[718]: stopping command channel on 127.0.0.1#953 Jan 1 19:05:34 server01 named[718]: stopping command channel on ::1#953 Jan 1 19:05:34 server01 named[718]: exiting Jan 1 19:05:36 server01 syslogd: exiting on signal 15 Jan 1 19:07:29 server01 syslogd: kernel boot file is /boot/kernel/kernel Jan 1 19:07:29 server01 kernel: Copyright (c) 1992-2008 The FreeBSD Project. Jan 1 19:07:29 server01 kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1 989, 1991, 1992, 1993, 1994 Jan 1 19:07:29 server01 kernel: The Regents of the University of California. All rights reserved. --- snip Thanks /Leslie ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Suddenly shutdown -p now produces a reboot
Leslie Jensen wrote: I have a Server with Squid, 7.0-RELEASE-p4 FreeBSD, squid-3.0.11, that has been running fine for the last six months, at least. It is shutdown every night at 7 PM via cron. Now suddenly the machine is rebooting instead, and I've made no changes whatsoever. I'm wondering if this is a symptom of a coming hardware failure or if I can do something to get the normal behaviour back. I did have a similar problem when I first put the machine into production, then it was clear from /var/log/messages that squid did not have enough time to shutdown and I solved it by changeing the parameter rcshutdown_timeout=90 i rc.conf. Here's a piece of /var/log/messages --- snip Jan 1 19:05:00 server01 shutdown: power-down by root: Jan 1 19:05:33 server01 squid[823]: Squid Parent: child process 826 exited with status 0 Jan 1 19:05:34 server01 named[718]: stopping command channel on 127.0.0.1#953 Jan 1 19:05:34 server01 named[718]: stopping command channel on ::1#953 Jan 1 19:05:34 server01 named[718]: exiting Jan 1 19:05:36 server01 syslogd: exiting on signal 15 Jan 1 19:07:29 server01 syslogd: kernel boot file is /boot/kernel/kernel Jan 1 19:07:29 server01 kernel: Copyright (c) 1992-2008 The FreeBSD Project. Jan 1 19:07:29 server01 kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1 989, 1991, 1992, 1993, 1994 Jan 1 19:07:29 server01 kernel: The Regents of the University of California. All rights reserved. --- snip Thanks /Leslie Leslie, I've got a gateway (talking pc mfg, not role) that does that. It's always rebooted on a request to shutdown. A fix, if I remember it right, that didn't last long was to go into BIOS and toggle the BIOS power management features. IIRC, it was set to disable, and I enabled it. Since then, i haven't really used that gateway anymore. You have to consider that some PCI devices can power-on a box (think: Remote Wakeup [which is done over the LAN]). The times that it does actually do it, don't bother me, i'll get around to forcing it down with a power button or power cord when it bugs me enough that it's still powered on. :) -- Tim Judd I will top-post when I feel like it. For those who are so demanding everyone bottom-post, You'll just have to forgive others when they choose to top-post. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: [6.3] Assigning shutdown to eg. Syst?
On Mon, Dec 22, 2008 at 03:31:27PM +0100, Gilles wrote: Hello I'd like to make it easier for my dad to shutdown a server. Instead of having him plug a keyboard, log on as root (with a complicated password) and finally type shutdown -h now, is it possible to assign this command to some unused key like eg. Syst? Even better, send this command only if the key is hit eg. three times within 2 seconds? Thank you. What I'd do is use sudo to enable him to shutdown. Then I'd add this to /etc/rc.local: kbdcontrol -f 10 sudo shutdown -h now So, pressing F10 hitting return will shut the machine down. Regards, -- Frank Contact info: http://www.shute.org.uk/misc/contact.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: [6.3] Assigning shutdown to eg. Syst?
The only other thing being in group operator lets you run,
apart from what you've added into /etc/devfs.{conf,rules} is
/sbin/mksnap_ffs ..
In a default devfs config, it grants read permission to
the disk devices (presumably to enable running dump(8)).
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: [6.3] Assigning shutdown to eg. Syst?
On Tue, 23 Dec 2008, per...@pluto.rain.com wrote:
The only other thing being in group operator lets you run,
apart from what you've added into /etc/devfs.{conf,rules} is
/sbin/mksnap_ffs ..
In a default devfs config, it grants read permission to
the disk devices (presumably to enable running dump(8)).
True, so if Gilles' dad really wants to run dump, he most likely can.
The .snap directory in the root of a (mounted) file system to be dumped
has owner root, group operator, mode 0770 - paraphrasing from dump(8) -
and then he'd need mount and write permissions on the dump destination.
Doesn't sound too risky if Gilles trusts him enough to run shutdown :)
cheers, Ian
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: [6.3] Assigning shutdown to eg. Syst?
On Tuesday 23 December 2008, Ian Smith wrote: Doesn't sound too risky if Gilles trusts him enough to run shutdown :) For a desktop there's no logic in restricting the shutdown command to only trusted users anyway. An untrusted user can't be prevented from shutting down by pulling the plug, far better to let (and encourage) him use shutdown instead -- Mike Clarke ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
[6.3] Assigning shutdown to eg. Syst?
Hello I'd like to make it easier for my dad to shutdown a server. Instead of having him plug a keyboard, log on as root (with a complicated password) and finally type shutdown -h now, is it possible to assign this command to some unused key like eg. Syst? Even better, send this command only if the key is hit eg. three times within 2 seconds? Thank you. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: [6.3] Assigning shutdown to eg. Syst?
On Mon, 22 Dec 2008 15:31:27 +0100, Gilles gilles.gana...@free.fr wrote: Hello I'd like to make it easier for my dad to shutdown a server. Instead of having him plug a keyboard, log on as root (with a complicated password) and finally type shutdown -h now, is it possible to assign this command to some unused key like eg. Syst? Even better, send this command only if the key is hit eg. three times within 2 seconds? I have a similar setting, but it requires X, WindowMaker and a Sun Type 6 USB keyboard. :-) Short explaination: I have assigned the command xterm -class SHUTDOWN -fg black -bg red -e shutdown -p now ; read DUMMY to the key combination Ctrl+Alt+(I) - the switch off or moon key on the top right. This combination is impossible to press accidentally. (Without Ctrl and Alt, this key closes the X session and leads back to xdm for login.) You could add a clickable menu entry or desktop icon with this command, but make sure it's not accidentally clicked. :-) If your father is already logged in, he could shutdown -p now (or using an alias) from an xterm. He needs to be in the wheel (or at least operator?) group for this. What about pressing the power button on the machine itself, it should perform a shutdown -p now (shut down and power off). By tht eay, the key you're refering to is named System Request, or SysRq. -- Polytropon From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: [6.3] Assigning shutdown to eg. Syst?
On Mon, 22 Dec 2008 16:09:02 +0100, Polytropon free...@edvax.de wrote: I have a similar setting, but it requires X, WindowMaker and a Sun Type 6 USB keyboard. :-) Thanks for the input, but this server is text-only. I'll try to find how FreeBSD is configured so that ALT-CTRL-DEL maps to reboot, and add my own keyboard key to shut it down. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: [6.3] Assigning shutdown to eg. Syst?
In the last episode (Dec 22), Gilles said: On Mon, 22 Dec 2008 16:09:02 +0100, Polytropon free...@edvax.de wrote: I have a similar setting, but it requires X, WindowMaker and a Sun Type 6 USB keyboard. :-) Thanks for the input, but this server is text-only. I'll try to find how FreeBSD is configured so that ALT-CTRL-DEL maps to reboot, and add my own keyboard key to shut it down. See the kbdcontrol(1) manpage; the -d and -l options are what you need. The keyboard(4) manpage sort of describes the layout of the keymap file. The full list of actions isn't documented anywhere, but all you need is 'boot'. -- Dan Nelson dnel...@allantgroup.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: [6.3] Assigning shutdown to eg. Syst?
On Mon, Dec 22, 2008 at 9:31 AM, Gilles gilles.gana...@free.fr wrote: Hello I'd like to make it easier for my dad to shutdown a server. Instead of having him plug a keyboard, log on as root (with a complicated password) and finally type shutdown -h now, is it possible to assign this command to some unused key like eg. Syst? Even better, send this command only if the key is hit eg. three times within 2 seconds? You could add him to the operator group, which would not require him to be root. -- Glen Barber ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: [6.3] Assigning shutdown to eg. Syst?
On Mon, 22 Dec 2008 20:53:39 +0100 Gilles gilles.gana...@free.fr wrote: On Mon, 22 Dec 2008 16:09:02 +0100, Polytropon free...@edvax.de wrote: I have a similar setting, but it requires X, WindowMaker and a Sun Type 6 USB keyboard. :-) :) Thanks for the input, but this server is text-only. I'll try to find how FreeBSD is configured so that ALT-CTRL-DEL maps to reboot, and add my own keyboard key to shut it down. Or let your dad login with his own account and password. Just add him to the operator group so that he can run /sbin/shutdown. If he's shy, write him a little script that does 'shutdown -p now [comment ..]' Shutdown is cleaner than reboot, runs 'stop' rc.d scripts for all active daemons, and leaves a nice log entry in messages, including any comment. cheers, Ian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: [6.3] Assigning shutdown to eg. Syst?
Ian Smith writes: Or let your dad login with his own account and password. Just add him to the operator group so that he can run /sbin/shutdown. If that's the only priveledged command he needs ... is there a reason sudo isn't a better answer? Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
