FreeBSDwiki - User contributions [en]

Users, modifying

2007-12-08T07:50:44Z

LionKimbro: groups

There are many ways to modify existing users on your system, depending on what you want to do; you can even edit the relevant files manually, but beware: the actual files referenced by the system aren't the plaintext editable files, they're compiled database files, so you'll need to use [[pwd_mkdb]] if you try to edit [[ /etc/master.passwd]] directly.

To change a user's shell, use [[chsh]] or [[pw]] '''usermod [username] -s [path to new shell]'''.

To change a user's name, edit [[ /etc/passwd]].

To change a user's login name (account name,) you can edit [[ /etc/passwd]] and [[ /etc/master.passwd]] and recompile them using [[pwd_mkdb]], but another easy (and safe!) way to do it is to add a new user and move the user's files over to the new user and chmod and chown everything to that new user.

To change the user's groups, edit [[/etc/group]]. [http://www.freebsd.org/doc/en/books/handbook/users-groups.html]

[[Category:Common Tasks]]

BIND, managing

2007-11-13T22:44:54Z

LionKimbro: explanation re: increasing SOA serial#

By far the easiest way to manage BIND is via [[webmin]], which is all GUI click and drop-down menus (see image below). But you should at the very least know how to manage it via command line for systems that you cannot set up [[webmin]] on for whatever reason or for those times when webmin fails.

To add records to a zone, you'll need to find that zone's file, edit it to include the record, '''increase your SOA serial number''' (1st parameter on IN SOA line, commonly with comment "; Serial") and reload your server with
rndc reload

If your server is a slave and you want it to retransfer the records from the master:
rndc retransfer

To check the status of your server:
rndc status

For example:

number of zones: 1077
debug level: 0
xfers running: 0
xfers deferred: 0
soa queries in progress: 0
query logging is OFF
recursive clients: 1/0/1000
tcp clients: 0/100
server is up and running

To stop your server:
rndc stop

To flush the DNS cache:
rndc flush

BIND can be a pain to manage properly, and not without reason there are thousands of pages on how to do it written.

* [[http://www.bind9.net/manuals BIND9.net Manuals]]
* bind-users FAQ
* [[http://www.reedmedia.net/books/bind-dns BIND 9 DNS Administration Reference Book]]
* [[http://www.netwidget.net/books/apress/dns/ Pro DNS and BIND]]

And here's a screenshot of Webmin's "Bind 9 Dynamic Server" module (which you'll have to install separately from the webmin.com site; the basic webmin BIND module doesn't do views very well and was designed for BIND 8):

[[Image: bind9webmin.PNG]]

== See also: ==

[[BIND]]

[[BIND (installing)]]

[[BIND (configuring)]]

[[BIND (securing)]]

[[Category:Configuring FreeBSD]]
[[Category:Ports and Packages]]
[[Category:Common Tasks]]
[[Category:DNS]]

Df

2007-06-17T21:22:59Z

LionKimbro: Incorrect df due to held files

[[df]] is acronymic for '''disk free'''.

When this command is used with no parameters, it will display the amount of disk space free on each mounted device in a 512-byte per block count, as well as a percentage.

You may specify either a device path or plain directory path to retrieve the associated mount-point information. Also, the parameter '''-h''' may be used to have the output displayed in 'human-readable' format.

[light@splat ~]$ '''/bin/df'''
Filesystem 1K-blocks Used Avail Capacity Mounted on
/dev/ad0s1a 128990 104110 14562 88% /
/dev/ad0s1f 257998 146 237214 0% /tmp
/dev/ad0s1g 18809884 15014076 2291018 87% /usr
/dev/ad0s1e 257998 236788 572 100% /var
procfs 4 4 0 100% /proc

[light@splat ~]$ '''df /tmp'''
Filesystem 1K-blocks Used Avail Capacity Mounted on
/dev/ad0s1f 257998 146 237214 0% /tmp

[light@splat ~]$ '''df /dev/ad0s1f'''
Filesystem 1K-blocks Used Avail Capacity Mounted on
/dev/ad0s1f 257998 146 237214 0% /tmp

[light@splat ~]$ '''df -h /'''
Filesystem Size Used Avail Capacity Mounted on
/dev/ad0s1a 132M 107M 15M 88% /

== Incorrect df ==

Sometimes, df reports values that are blatantly wrong.

Scenario: MySQL is giving you error 28's, and you find /var is completely full. You delete the 200 MB Apache logs, which should put you well within limits... ...for some reason, df still reports that /var appears is completely full?

The problem is that Apache is still holding on to the log file, even though you deleted.

If you restart apache, (perhaps using [[Apachectl]],) Apache releases the log file, and df shows the value right. MySQL goes back to working.

[[Category:System Commands]]