summaryrefslogtreecommitdiffstats
path: root/sbin
Commit message (Collapse)AuthorAgeFilesLines
* Stop disallowing device nodes to be passed to camcontrol(8) since libcambrucec2010-10-192-12/+1
| | | | | | already allows both device names and nodes to be specified. Reviewed by: avg
* mdoc: drop even more redundant .Pp callsuqs2010-10-193-6/+0
| | | | | | No change in rendered output, less mandoc lint warnings. Tool provided by: Nobuyuki Koganemaru n-kogane at syd.odn.ne.jp
* Log correct connection when canceling half-open connection.pjd2010-10-171-1/+2
| | | | | Submitted by: Mikolaj Golub <to.my.trociny@gmail.com> MFC after: 3 days
* Use one fprintf() instead of two.pjd2010-10-161-2/+1
| | | | MFC after: 3 days
* Clear signal mask before executing a hook.pjd2010-10-161-0/+3
| | | | | Submitted by: Mikolaj Golub <to.my.trociny@gmail.com> MFC after: 3 days
* document logging through bpfluigi2010-10-131-13/+18
|
* Remove stale reference to wtmp(5).ed2010-10-111-2/+2
| | | | Reported by: pluknet
* - Print the nmount(2) provided error message only when it is set.jh2010-10-101-2/+6
| | | | | | | - Ensure that the error message is NUL-terminated before printing it. PR: bin/147482 MFC after: 2 weeks
* Replace strlen(_PATH_DEV) with sizeof(_PATH_DEV) - 1.ae2010-10-099-21/+21
| | | | | | Suggested by: kib Approved by: kib (mentor) MFC after: 5 days
* Allow the kernel to generate more spacy things and still have devdimp2010-10-091-0/+8
| | | | | | | | cope. Skip multiple spaces in a few contexts. PR: 96854 Submitted by: Shin'ya Kumabuchi MFC after: 1 week
* We can't zero out ggio request, as we have some fields in there we initializepjd2010-10-081-1/+0
| | | | | | | once during start-up. Reported by: Mikolaj Golub <to.my.trociny@gmail.com> MFC after: 3 days
* We close the event socketpair early in the mainloop to prevent spaming withpjd2010-10-081-2/+4
| | | | | | | | error messages, so when we clean up after child process, we have to check if the event socketpair is still there. Submitted by: Mikolaj Golub <to.my.trociny@gmail.com> MFC after: 3 days
* mdoc: drop redundant .Pp and .LP callsuqs2010-10-087-16/+0
| | | | They have no effect when coming in pairs, or before .Bl/.Bd
* Clear ggate structures before using them. We don't initialize all the fieldpjd2010-10-071-1/+4
| | | | | | and there can be some garbage from the stack. MFC after: 1 week
* Log error message when we fail to destroy ggate provider.pjd2010-10-071-1/+2
| | | | MFC after: 3 days
* Start the guard thread first, so we can handle signals from the very begining.pjd2010-10-071-3/+7
| | | | | Reported by: Mikolaj Golub <to.my.trociny@gmail.com> MFC after: 1 week
* Don't close local component on exit as we can hang waiting on g_waitidle.pjd2010-10-071-6/+0
| | | | | | | | | I'm unable to reproduce the race described in comment anymore and also the comment is incorrect - localfd represents local component from configuration file, eg. /dev/da0 and not HAST provider. Reported by: Mikolaj Golub <to.my.trociny@gmail.com> MFC after: 1 week
* Decrease report interval to 5 seconds, as this also means we will check forpjd2010-10-041-1/+1
| | | | | | signals every 5 seconds and not every 10 seconds as before. MFC after: 3 days
* hook_check() is now only used to report about long-running hooks, so thepjd2010-10-043-13/+3
| | | | | | argument is redundant, remove it. MFC after: 3 days
* We can't mask ignored signal, so install dummy signal hander for SIGCHLD beforepjd2010-10-041-0/+11
| | | | | | | | | | masking it. This fixes bogus reports about hooks running for too long and other problems related to garbage-collecting child processes. Reported by: Mikolaj Golub <to.my.trociny@gmail.com> MFC after: 3 days
* Fix printing of the "rw" mount option in fstab(5) format (-p option).jh2010-09-301-12/+12
| | | | | | | | | fstab(5) format requires that one of "rw", "rq" or "ro" is always specified. PR: bin/123021 Reviewed by: keramida, rodrigc MFC after: 2 weeks
* Document recently added GPT attributes (bootme, bootonce, bootfailed) andpjd2010-09-281-1/+104
| | | | | | | list other schemes attributes. Reviewed by: simon, rpaulo MFC after: 2 weeks
* Remove superfluous word from "gpart bootcode" usage message.ae2010-09-261-1/+1
| | | | Approved by: kib (mentor)
* Plug memory leak on fork(2) failure.pjd2010-09-261-0/+1
| | | | | Submitted by: Mikolaj Golub <to.my.trociny@gmail.com> MFC after: 3 days
* - Add support for loading passphrase from a file (-J and -j options).pjd2010-09-252-122/+257
| | | | | | | | | | This is especially useful for things like installers, where regular geli prompt can't be used. - Add support for specifing multiple -K or -k options, so there is no need to cat all keyfiles and read them from standard input. Requested by: Kris Moore <kris@pcbsd.org>, thompsa MFC after: 2 weeks
* Reported problem:mckusick2010-09-241-7/+23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Large (60GB) filesystems created using "newfs -U -O 1 -b 65536 -f 8192" show incorrect results from "df" for free and used space when mounted immediately after creation. fsck on the new filesystem (before ever mounting it once) gives a "SUMMARY INFORMATION BAD" error in phase 5. This error hasn't occurred in any runs of fsck immediately after "newfs -U -b 65536 -f 8192" (leaving out the "-O 1" option). Solution: The default UFS1 superblock is located at offset 8K in the filesystem partition; the default UFS2 superblock is located at offset 64K in the filesystem partition. For UFS1 filesystems with a blocksize of 64K, the first alternate superblock resides at 64K which is the the location used for the default UFS2 superblock. By default, the system first checks for a valid superblock at the default location for a UFS2 filoesystem. For a UFS1 filesystem with a blocksize of 64K, there is a valid UFS1 superblock at this location. Thus, even though it is expected to be a backup superblock, the system will use it as its default superblock. So, we have to ensure that all the statistcs on usage are correct in this first alternate superblock as it is the superblock that will actually be used. While tracking down this problem, another limitation of UFS1 became evident. For UFS1, the number of inodes per cylinder group is stored in an int16_t. Thus the maximum number of inodes per cylinder group is limited to 2^15 - 1. This limit can easily be exceeded for block sizes of 32K and above. Thus when building UFS1 filesystems, newfs must limit the number of inodes per cylinder group to 2^15 - 1. Reported by: Guy Helmer<ghelmer@palisadesys.com> Followup by: Bruce Cran <brucec@freebsd.org> PR: 107692 MFC after: 4 weeks
* Implement "force" (-F) option for gpart destroy verb.ae2010-09-242-15/+106
| | | | | | | | | | | | This option doesn't passed to kernel and handled in user-space. With -F option gpart creates new "delete" request for each partition in table. Each request has flags="X" that disables auto-commit feature. Last request is the original "destroy" request. It has own flags and can have disabled or enabled auto-commit feature. If error is occurred when deleting partitions, then new "undo" request is created and all changes will be rolled back. Approved by: kib (mentor)
* - Simplify code by using g_*() API.pjd2010-09-232-83/+62
| | | | | | | | - Don't use u_char and u_int in userland. - Change 'unsigned' to 'unsigned int'. - Update copyright years. MFC after: 1 week
* Update copyright years.pjd2010-09-231-1/+1
| | | | MFC after: 1 week
* Document AES-XTS.pjd2010-09-231-17/+34
| | | | MFC after: 1 week
* - When trashing metadata, repeat overwrite kern.geom.eli.overwrites times.pjd2010-09-231-12/+64
| | | | | | - Flush write cache after each write. MFC after: 1 week
* - Use g_*() API when doing backups.pjd2010-09-231-18/+12
| | | | | | - fsync() created filed. MFC after: 1 week
* Because we first write metadata into new place and then trash old place wepjd2010-09-231-0/+4
| | | | | | | don't want situation where old size is equal to new size, as we will trash newly written metadata. MFC after: 1 week
* - Make use of g_*() API.pjd2010-09-231-18/+13
| | | | | | - Flush cache after writing metadata. MFC after: 1 week
* Simplify code a bit by using g_*() API from libgeom.pjd2010-09-231-19/+10
| | | | MFC after: 1 week
* Switch to sigprocmask(2) API also in the main process and secondary process.pjd2010-09-224-61/+44
| | | | | | | | | This way the primary process inherits signal mask from the main process, which fixes a race where signal is delivered to the primary process before configuring signal mask. Reported by: Mikolaj Golub <to.my.trociny@gmail.com> MFC after: 3 days
* Assert that descriptor numbers are sane.pjd2010-09-221-0/+4
| | | | MFC after: 3 days
* Fix possible deadlock where worker process sends an event to the main processpjd2010-09-222-8/+26
| | | | | | | | | | | while the main process sends control message to the worker process, but worker process hasn't started control thread yet, because it waits for reply from the main process. The fix is to start the control thread before sending any events. Reported and fix suggested by: Mikolaj Golub <to.my.trociny@gmail.com> MFC after: 3 days
* Fix descriptor leaks: when child exits, we have to close control and eventpjd2010-09-223-9/+17
| | | | | | socket pairs. We did that only in one case out of three. MFC after: 3 days
* If we are unable to receive control message is most likely because the mainpjd2010-09-221-1/+2
| | | | | | process died. Instead of entering infinite loop, terminate. MFC after: 3 days
* Sort includes.pjd2010-09-221-1/+1
| | | | MFC after: 3 days
* Add a notice to the man page that batteries should be installed.ed2010-09-211-0/+1
|
* Add a geli resize subcommand to resize encrypted filesystems priorbrian2010-09-202-5/+187
| | | | | | | | | | | | | | | to growing the filesystem. Refuse to attach providers where the metadata provider size is wrong. This makes post-boot attaches behave consistently with pre-boot attaches. Also refuse to restore metadata to a provider of the wrong size without the new -f switch. The new -f switch forces the metadata restoration despite the provider size, and updates the provider size in the restored metadata to the correct value. Helped by: pjd Reviewed by: pjd
* Add __dead2 to functions that we know they are going to exit.pjd2010-09-202-3/+3
| | | | MFC after: 3 days
* Unbreak the build on strong-aligned architectures (arm, ia64).marcel2010-09-201-1/+1
| | | | | | | Casting from (char *) to (struct ufs1_dinode *) changes the alignment requirement of the pointer and GCC does not know that the pointer is adequately aligned (due to malloc(3)), and warns about it. Cast to (void *) first to by-pass the check.
* Fix indent.pjd2010-09-191-7/+7
|
* Revise r197763 which fixes filesystem corruption when extendingbrian2010-09-191-14/+13
| | | | | | | | | | | | into un-zeroed storage. The original patch was questioned by Kirk as it forces the filesystem to do excessive work initialising inodes on first use, and was never MFC'd. This change mimics the newfs(8) approach of zeroing two blocks of inodes for each new cylinder group. Reviewed by: mckusick MFC after: 3 weeks
* nextboot: warn about limitations of /boot/nextboot.conf on ZFSavg2010-09-171-0/+8
| | | | MFC after: 1 week
* Make the format of "Real Memory" and "Virtual Memory" lines morezec2010-09-161-2/+2
| | | | | | consistent with the rest of sysctl vm.vmtotal output. MFC after: 3 days
* Add support for identifying a journaled root filesystem.brian2010-09-161-1/+2
| | | | | | Fix support for identifying the given /dev/vinum/root example. MFC after: 3 weeks
OpenPOWER on IntegriCloud