Re: backspace shows ^? in serial communications
thanks for your answer. you know, i have a freebsd box (something like router) which i connect to it by putty or other terminal programs (cu,...). this router has a serial card and i have a c program to open and manage serial ports. now when i run this c program and connect to the third freebsd box, backspace shows ^?. now i don't know where is problem and for which system terminal settings should be checked. from you explanation i think that i should check serial settings in c program in the router box. am i right? please let me know what should i do to this program (c program in router box) show backspace correctly when i connect by different serial programs to router box and run it. thanks On Wed, Feb 6, 2013 at 10:20 AM, Polytropon free...@edvax.de wrote: On Wed, 6 Feb 2013 09:44:37 +0330, s m wrote: hi all i have a problem with backspace in serial communications. i have a freebsd8.2 box with a serial card on it. when i connect to other freebsd box via serial port backspace does not act as i expected. backspace shows ^? on screen. i searched alot and find out that stty has two parameters -erase and erase2- to identify erase characters in terminal and they should be set correctly. i set erase and erase2 to ^? by stty erase \^? and stty erase2 \^? commands but nothing happened. please let me know how i can fix it. i know it is simple issue but i really do not know how to do that. If I remember correctly, ^? is delete, ^H is backspace. You should check your terminal emulator if it outputs ^? instead of ^H when you press the backspace key. FreeBSD's default configuration handles keys correctly (if you have the proper terminal emulation set, e. g. vt100 or vt220 for your serial line), so there's probably something wrong with the settings of the terminal program you're using. For comparison: % echo $TERM xterm % stty -a speed 9600 baud; 24 rows; 80 columns; lflags: icanon isig iexten echo echoe echok echoke -echonl echoctl -echoprt -altwerase -noflsh -tostop -flusho -pendin -nokerninfo -extproc iflags: -istrip icrnl -inlcr -igncr ixon -ixoff -ixany -imaxbel -ignbrk -brkint -inpck -ignpar -parmrk oflags: opost onlcr -ocrnl tab3 -onocr -onlret cflags: cread cs8 parenb -parodd hupcl -clocal -cstopb -crtscts -dsrflow -dtrflow -mdmbuf cchars: discard = ^O; dsusp = ^Y; eof = ^D; eol = undef; eol2 = undef; erase = ^H; erase2 = ^H; intr = ^C; kill = ^U; lnext = ^V; min = 1; quit = ^\; reprint = ^R; start = ^Q; status = ^T; stop = ^S; susp = ^Z; time = 0; werase = ^W; And: % echo $TERM cons25l1 % stty -a speed 9600 baud; 25 rows; 80 columns; lflags: icanon isig iexten echo echoe -echok echoke -echonl echoctl -echoprt -altwerase -noflsh -tostop -flusho -pendin -nokerninfo -extproc iflags: -istrip icrnl -inlcr -igncr ixon -ixoff ixany imaxbel -ignbrk brkint -inpck -ignpar -parmrk oflags: opost onlcr -ocrnl tab0 -onocr -onlret cflags: cread cs8 -parenb -parodd hupcl -clocal -cstopb -crtscts -dsrflow -dtrflow -mdmbuf cchars: discard = ^O; dsusp = ^Y; eof = ^D; eol = undef; eol2 = undef; erase = ^H; erase2 = ^H; intr = ^C; kill = ^U; lnext = ^V; min = 1; quit = ^\; reprint = ^R; start = ^Q; status = ^T; stop = ^S; susp = ^Z; time = 0; werase = ^W; If you want the system's C shell to treat ^? (delete) as it should be treated (perform delete instead of backspace or nothing), add those to your .cshrc: bindkey ^? delete-char # for console bindkey ^[[3~ delete-char # for xterm Note that this only affects the C shell. -- 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: backspace shows ^? in serial communications
From owner-freebsd-questi...@freebsd.org Wed Feb 6 00:19:04 2013
Date: Wed, 6 Feb 2013 09:44:37 +0330
Subject: backspace shows ^? in serial communications
From: s m sam.gh1...@gmail.com
To: freebsd-questions freebsd-questions@freebsd.org
hi all
i have a problem with backspace in serial communications. i have a
freebsd8.2 box with a serial card on it. when i connect to other freebsd
box via serial port backspace does not act as i expected. backspace shows
^? on screen. i searched alot and find out that stty has two parameters
-erase and erase2- to identify erase characters in terminal and they should
be set correctly. i set erase and erase2 to ^? by stty erase \^? and
stty erase2 \^? commands but nothing happened.
please let me know how i can fix it. i know it is simple issue but i really
do not know how to do that.
stty erase {press the backspace key}
Then hit the enter/return key
___
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 is bacula-client looking for libz.so.5 on 9-STABLE
Den 06.02.2013 00:03, skrev Per olof Ljungmark: Hi, Upgraded a system from 8.3 to 9-STABLE and did make delete-old-libs afterwards. System has around thirty ports installed and all except bacula-client upgraded gracefully. Why does it want libz.so.5 when libz.so.6 is present? I'm pretty sure I'm missing the obvious here... Linking bacula-fd ... /usr/ports/sysutils/bacula-client/work/bacula-5.2.12/libtool --silent --tag=CXX --mode=link /usr/bin/c++ -L/usr/local/lib -L../lib -L../findlib -o bacula-fd filed.o authenticate.o acl.o backup.o estimate.o fd_plugins.o accurate.o filed_conf.o heartbeat.o job.o pythonfd.o restore.o status.o verify.o verify_vol.o xattr.o-lz -lbacfind -lbacpy -lbaccfg -lbac -lm -lpthread -lintl -lwrap /usr/local/lib/libintl.so /usr/local/lib/libiconv.so -Wl,-rpath -Wl,/usr/local/lib /usr/bin/ld: warning: libz.so.5, needed by /usr/local/lib/libbac.so, not found (try using -rpath or -rpath-link) 'libbac.so' is installed by bacula-server; try to rebuild this port first! Use 'sysutils/libchk' or pkg_libchk (from bsdadminscripts) to find other broken ports. -- Herbert ___ 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
VirtualBox 4.1.22 and Bridged Network problems
Hello :-) I cannot get Bridged Network setup in VBox 4.1.22 on my 9.1RC3 AMD64 - I get no traffic to the host interface at all. Did anyone noticed this or related problems? I have tried to watch the host interface with WireShark. I have disabled local firewall. I have set net.inet.ip.forwarding=1. Still can't get the bridged connection working :-( Any hints appreciated :-) Tomek -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ 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: VirtualBox 4.1.22 and Bridged Network problems
This was brought up a few weeks/months ago and I seem to recall that setting the interface in *promiscuous* mode (monitoring) in the Host configuration (read, in your hypervisor) was mandatory. See if that helps. On Feb 6, 2013, at 3:03 PM, CeDeROM cede...@tlen.pl wrote: Hello :-) I cannot get Bridged Network setup in VBox 4.1.22 on my 9.1RC3 AMD64 - I get no traffic to the host interface at all. Did anyone noticed this or related problems? I have tried to watch the host interface with WireShark. I have disabled local firewall. I have set net.inet.ip.forwarding=1. Still can't get the bridged connection working :-( Any hints appreciated :-) Tomek -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ 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
about pfctl
I have a freebsd box and pf Works on it. I wish to see use of data for each ip address. When i execute pfctl -t tablename -vT showI can see usages of these ips. Pfctl lists all of ips. But how can i filter it for each ip address ? because i want to insert these data for each ip into a mysql table. ___ 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: VirtualBox 4.1.22 and Bridged Network problems
Le Wed, 6 Feb 2013 15:03:36 +0100, CeDeROM cede...@tlen.pl a écrit : Hello, I cannot get Bridged Network setup in VBox 4.1.22 on my 9.1RC3 AMD64 - I get no traffic to the host interface at all. Did anyone noticed this or related problems? Works fine here (9.1-STABLE/amd64, virtual box 4.2.6). Be sure that the virbualbox kernel modules are in sync with your kernel (ie rebuilt virtualbox-ose-kmod). Regards. ___ 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
sysctl security.jail.* descriptions
Where do I find the descriptions of what these jail MIBs do? security.jail.param.allow.mount.zfs: 0 security.jail.param.allow.mount.procfs: 0 security.jail.param.allow.mount.nullfs: 0 security.jail.param.allow.mount.devfs: 0 security.jail.param.allow.mount.: 0 security.jail.param.allow.socket_af: 0 security.jail.param.allow.quotas: 0 security.jail.param.allow.chflags: 0 security.jail.param.allow.raw_sockets: 0 security.jail.param.allow.sysvipc: 0 security.jail.param.allow.set_hostname: 0 security.jail.param.ip6.saddrsel: 0 security.jail.param.ip6.: 0 security.jail.param.ip4.saddrsel: 0 security.jail.param.ip4.: 0 security.jail.param.cpuset.id: 0 security.jail.param.host.hostid: 0 security.jail.param.host.hostuuid: 64 security.jail.param.host.domainname: 256 security.jail.param.host.hostname: 256 security.jail.param.host.: 0 security.jail.param.children.max: 0 security.jail.param.children.cur: 0 security.jail.param.dying: 0 security.jail.param.persist: 0 security.jail.param.devfs_ruleset: 0 security.jail.param.enforce_statfs: 0 security.jail.param.securelevel: 0 security.jail.param.path: 1024 security.jail.param.name: 256 security.jail.param.parent: 0 security.jail.param.jid: 0 security.jail.devfs_ruleset: 0 security.jail.enforce_statfs: 2 security.jail.mount_zfs_allowed: 0 security.jail.mount_procfs_allowed: 0 security.jail.mount_nullfs_allowed: 0 security.jail.mount_devfs_allowed: 0 security.jail.mount_allowed: 0 security.jail.chflags_allowed: 0 security.jail.allow_raw_sockets: 0 security.jail.sysvipc_allowed: 0 security.jail.socket_unixiproute_only: 1 security.jail.set_hostname_allowed: 1 security.jail.jail_max_af_ips: 255 security.jail.jailed: 0 ___ 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: sysctl security.jail.* descriptions
# sysctl -d security.jail.socket_unixiproute_only security.jail.socket_unixiproute_only: Processes in jail are limited to creating UNIX/IP/route sockets only On Feb 6, 2013, at 4:02 PM, Fbsd8 fb...@a1poweruser.com wrote: Where do I find the descriptions of what these jail MIBs do? security.jail.param.allow.mount.zfs: 0 security.jail.param.allow.mount.procfs: 0 security.jail.param.allow.mount.nullfs: 0 security.jail.param.allow.mount.devfs: 0 security.jail.param.allow.mount.: 0 security.jail.param.allow.socket_af: 0 security.jail.param.allow.quotas: 0 security.jail.param.allow.chflags: 0 security.jail.param.allow.raw_sockets: 0 security.jail.param.allow.sysvipc: 0 security.jail.param.allow.set_hostname: 0 security.jail.param.ip6.saddrsel: 0 security.jail.param.ip6.: 0 security.jail.param.ip4.saddrsel: 0 security.jail.param.ip4.: 0 security.jail.param.cpuset.id: 0 security.jail.param.host.hostid: 0 security.jail.param.host.hostuuid: 64 security.jail.param.host.domainname: 256 security.jail.param.host.hostname: 256 security.jail.param.host.: 0 security.jail.param.children.max: 0 security.jail.param.children.cur: 0 security.jail.param.dying: 0 security.jail.param.persist: 0 security.jail.param.devfs_ruleset: 0 security.jail.param.enforce_statfs: 0 security.jail.param.securelevel: 0 security.jail.param.path: 1024 security.jail.param.name: 256 security.jail.param.parent: 0 security.jail.param.jid: 0 security.jail.devfs_ruleset: 0 security.jail.enforce_statfs: 2 security.jail.mount_zfs_allowed: 0 security.jail.mount_procfs_allowed: 0 security.jail.mount_nullfs_allowed: 0 security.jail.mount_devfs_allowed: 0 security.jail.mount_allowed: 0 security.jail.chflags_allowed: 0 security.jail.allow_raw_sockets: 0 security.jail.sysvipc_allowed: 0 security.jail.socket_unixiproute_only: 1 security.jail.set_hostname_allowed: 1 security.jail.jail_max_af_ips: 255 security.jail.jailed: 0 ___ 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: sysctl security.jail.* descriptions
On Feb 6, 2013 7:02 AM, Fbsd8 fb...@a1poweruser.com wrote: Where do I find the descriptions of what these jail MIBs do? security.jail.param.allow.mount.zfs: 0 security.jail.param.allow.mount.procfs: 0 security.jail.param.allow.mount.nullfs: 0 security.jail.param.allow.mount.devfs: 0 security.jail.param.allow.mount.: 0 security.jail.param.allow.socket_af: 0 security.jail.param.allow.quotas: 0 security.jail.param.allow.chflags: 0 security.jail.param.allow.raw_sockets: 0 security.jail.param.allow.sysvipc: 0 security.jail.param.allow.set_hostname: 0 security.jail.param.ip6.saddrsel: 0 security.jail.param.ip6.: 0 security.jail.param.ip4.saddrsel: 0 security.jail.param.ip4.: 0 security.jail.param.cpuset.id: 0 security.jail.param.host.hostid: 0 security.jail.param.host.hostuuid: 64 security.jail.param.host.domainname: 256 security.jail.param.host.hostname: 256 security.jail.param.host.: 0 security.jail.param.children.max: 0 security.jail.param.children.cur: 0 security.jail.param.dying: 0 security.jail.param.persist: 0 security.jail.param.devfs_ruleset: 0 security.jail.param.enforce_statfs: 0 security.jail.param.securelevel: 0 security.jail.param.path: 1024 security.jail.param.name: 256 security.jail.param.parent: 0 security.jail.param.jid: 0 security.jail.devfs_ruleset: 0 security.jail.enforce_statfs: 2 security.jail.mount_zfs_allowed: 0 security.jail.mount_procfs_allowed: 0 security.jail.mount_nullfs_allowed: 0 security.jail.mount_devfs_allowed: 0 security.jail.mount_allowed: 0 security.jail.chflags_allowed: 0 security.jail.allow_raw_sockets: 0 security.jail.sysvipc_allowed: 0 security.jail.socket_unixiproute_only: 1 security.jail.set_hostname_allowed: 1 security.jail.jail_max_af_ips: 255 security.jail.jailed: 0 ___ 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 Did you try the man page? Also there is often interesting comments in /usr/src Hope that helps. Waitman Gobble San Jose California ___ 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: sysctl security.jail.* descriptions
Waitman Gobble wrote: On Feb 6, 2013 7:02 AM, Fbsd8 fb...@a1poweruser.com wrote: Where do I find the descriptions of what these jail MIBs do? security.jail.param.allow.mount.zfs: 0 security.jail.param.allow.mount.procfs: 0 security.jail.param.allow.mount.nullfs: 0 security.jail.param.allow.mount.devfs: 0 security.jail.param.allow.mount.: 0 security.jail.param.allow.socket_af: 0 security.jail.param.allow.quotas: 0 security.jail.param.allow.chflags: 0 security.jail.param.allow.raw_sockets: 0 security.jail.param.allow.sysvipc: 0 security.jail.param.allow.set_hostname: 0 security.jail.param.ip6.saddrsel: 0 security.jail.param.ip6.: 0 security.jail.param.ip4.saddrsel: 0 security.jail.param.ip4.: 0 security.jail.param.cpuset.id: 0 security.jail.param.host.hostid: 0 security.jail.param.host.hostuuid: 64 security.jail.param.host.domainname: 256 security.jail.param.host.hostname: 256 security.jail.param.host.: 0 security.jail.param.children.max: 0 security.jail.param.children.cur: 0 security.jail.param.dying: 0 security.jail.param.persist: 0 security.jail.param.devfs_ruleset: 0 security.jail.param.enforce_statfs: 0 security.jail.param.securelevel: 0 security.jail.param.path: 1024 security.jail.param.name: 256 security.jail.param.parent: 0 security.jail.param.jid: 0 security.jail.devfs_ruleset: 0 security.jail.enforce_statfs: 2 security.jail.mount_zfs_allowed: 0 security.jail.mount_procfs_allowed: 0 security.jail.mount_nullfs_allowed: 0 security.jail.mount_devfs_allowed: 0 security.jail.mount_allowed: 0 security.jail.chflags_allowed: 0 security.jail.allow_raw_sockets: 0 security.jail.sysvipc_allowed: 0 security.jail.socket_unixiproute_only: 1 security.jail.set_hostname_allowed: 1 security.jail.jail_max_af_ips: 255 security.jail.jailed: 0 Did you try the man page? Also there is often interesting comments in /usr/src Hope that helps. Waitman Gobble San Jose California There are no man pages for any MIBs ___ 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: sysctl security.jail.* descriptions
On Feb 6, 2013 7:17 AM, Fbsd8 fb...@a1poweruser.com wrote: Waitman Gobble wrote: On Feb 6, 2013 7:02 AM, Fbsd8 fb...@a1poweruser.com wrote: Where do I find the descriptions of what these jail MIBs do? security.jail.param.allow.mount.zfs: 0 security.jail.param.allow.mount.procfs: 0 security.jail.param.allow.mount.nullfs: 0 security.jail.param.allow.mount.devfs: 0 security.jail.param.allow.mount.: 0 security.jail.param.allow.socket_af: 0 security.jail.param.allow.quotas: 0 security.jail.param.allow.chflags: 0 security.jail.param.allow.raw_sockets: 0 security.jail.param.allow.sysvipc: 0 security.jail.param.allow.set_hostname: 0 security.jail.param.ip6.saddrsel: 0 security.jail.param.ip6.: 0 security.jail.param.ip4.saddrsel: 0 security.jail.param.ip4.: 0 security.jail.param.cpuset.id: 0 security.jail.param.host.hostid: 0 security.jail.param.host.hostuuid: 64 security.jail.param.host.domainname: 256 security.jail.param.host.hostname: 256 security.jail.param.host.: 0 security.jail.param.children.max: 0 security.jail.param.children.cur: 0 security.jail.param.dying: 0 security.jail.param.persist: 0 security.jail.param.devfs_ruleset: 0 security.jail.param.enforce_statfs: 0 security.jail.param.securelevel: 0 security.jail.param.path: 1024 security.jail.param.name: 256 security.jail.param.parent: 0 security.jail.param.jid: 0 security.jail.devfs_ruleset: 0 security.jail.enforce_statfs: 2 security.jail.mount_zfs_allowed: 0 security.jail.mount_procfs_allowed: 0 security.jail.mount_nullfs_allowed: 0 security.jail.mount_devfs_allowed: 0 security.jail.mount_allowed: 0 security.jail.chflags_allowed: 0 security.jail.allow_raw_sockets: 0 security.jail.sysvipc_allowed: 0 security.jail.socket_unixiproute_only: 1 security.jail.set_hostname_allowed: 1 security.jail.jail_max_af_ips: 255 security.jail.jailed: 0 Did you try the man page? Also there is often interesting comments in /usr/src Hope that helps. Waitman Gobble San Jose California There are no man pages for any MIBs Sorry, but im not at a computer now to check, but I believe it would be in the «jail» man page. Hopefully that's the right 411. Waitman ___ 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: sysctl security.jail.* descriptions
Waitman Gobble wrote: On Feb 6, 2013 7:17 AM, Fbsd8 fb...@a1poweruser.com wrote: Waitman Gobble wrote: On Feb 6, 2013 7:02 AM, Fbsd8 fb...@a1poweruser.com wrote: Where do I find the descriptions of what these jail MIBs do? security.jail.param.allow.mount.zfs: 0 security.jail.param.allow.mount.procfs: 0 security.jail.param.allow.mount.nullfs: 0 security.jail.param.allow.mount.devfs: 0 security.jail.param.allow.mount.: 0 security.jail.param.allow.socket_af: 0 security.jail.param.allow.quotas: 0 security.jail.param.allow.chflags: 0 security.jail.param.allow.raw_sockets: 0 security.jail.param.allow.sysvipc: 0 security.jail.param.allow.set_hostname: 0 security.jail.param.ip6.saddrsel: 0 security.jail.param.ip6.: 0 security.jail.param.ip4.saddrsel: 0 security.jail.param.ip4.: 0 security.jail.param.cpuset.id: 0 security.jail.param.host.hostid: 0 security.jail.param.host.hostuuid: 64 security.jail.param.host.domainname: 256 security.jail.param.host.hostname: 256 security.jail.param.host.: 0 security.jail.param.children.max: 0 security.jail.param.children.cur: 0 security.jail.param.dying: 0 security.jail.param.persist: 0 security.jail.param.devfs_ruleset: 0 security.jail.param.enforce_statfs: 0 security.jail.param.securelevel: 0 security.jail.param.path: 1024 security.jail.param.name: 256 security.jail.param.parent: 0 security.jail.param.jid: 0 security.jail.devfs_ruleset: 0 security.jail.enforce_statfs: 2 security.jail.mount_zfs_allowed: 0 security.jail.mount_procfs_allowed: 0 security.jail.mount_nullfs_allowed: 0 security.jail.mount_devfs_allowed: 0 security.jail.mount_allowed: 0 security.jail.chflags_allowed: 0 security.jail.allow_raw_sockets: 0 security.jail.sysvipc_allowed: 0 security.jail.socket_unixiproute_only: 1 security.jail.set_hostname_allowed: 1 security.jail.jail_max_af_ips: 255 security.jail.jailed: 0 Did you try the man page? Also there is often interesting comments in /usr/src Hope that helps. Waitman Gobble San Jose California There are no man pages for any MIBs Sorry, but im not at a computer now to check, but I believe it would be in the «jail» man page. Hopefully that's the right 411. Waitman man jail only talks about these few MIBs security.jail.mount_zfs_allowed: 0 security.jail.mount_procfs_allowed: 0 security.jail.mount_nullfs_allowed: 0 security.jail.mount_devfs_allowed: 0 security.jail.mount_allowed: 0 security.jail.chflags_allowed: 0 security.jail.allow_raw_sockets: 0 security.jail.sysvipc_allowed: 0 security.jail.socket_unixiproute_only: 1 security.jail.set_hostname_allowed: 1 security.jail.jail_max_af_ips: 255 security.jail.jailed: 0 which are set from the host only. What about the other security.jail.param.* MIBs where are they documented at? ___ 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
setting MIBs on a per jail bases
Is there a way to set these MIBs on a per jail bases? allow.mount.nullfs allow.raw_sockets cpuset.id securelevel ___ 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: setting MIBs on a per jail bases
Running 8.3 here and the answer is no. On Feb 6, 2013, at 5:39 PM, Fbsd8 fb...@a1poweruser.com wrote: Is there a way to set these MIBs on a per jail bases? allow.mount.nullfs allow.raw_sockets cpuset.id securelevel ___ 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: setting MIBs on a per jail bases
Fleuriot Damien wrote: Running 8.3 here and the answer is no. On Feb 6, 2013, at 5:39 PM, Fbsd8 fb...@a1poweruser.com wrote: Is there a way to set these MIBs on a per jail bases? allow.mount.nullfs allow.raw_sockets cpuset.id securelevel Rereading the man jail for 9.1 talks about securelevel as a jail parammeter. So correct me if I an wrong. All the security.jail.param.* MIBs are set in rc.conf or /etc/jail.conf file on a per jail bases by changing the word parm to the jailname? ___ 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: sysctl security.jail.* descriptions
Fbsd8 wrote: Waitman Gobble wrote: On Feb 6, 2013 7:17 AM, Fbsd8 fb...@a1poweruser.com wrote: Waitman Gobble wrote: On Feb 6, 2013 7:02 AM, Fbsd8 fb...@a1poweruser.com wrote: Where do I find the descriptions of what these jail MIBs do? security.jail.param.allow.mount.zfs: 0 security.jail.param.allow.mount.procfs: 0 security.jail.param.allow.mount.nullfs: 0 security.jail.param.allow.mount.devfs: 0 security.jail.param.allow.mount.: 0 security.jail.param.allow.socket_af: 0 security.jail.param.allow.quotas: 0 security.jail.param.allow.chflags: 0 security.jail.param.allow.raw_sockets: 0 security.jail.param.allow.sysvipc: 0 security.jail.param.allow.set_hostname: 0 security.jail.param.ip6.saddrsel: 0 security.jail.param.ip6.: 0 security.jail.param.ip4.saddrsel: 0 security.jail.param.ip4.: 0 security.jail.param.cpuset.id: 0 security.jail.param.host.hostid: 0 security.jail.param.host.hostuuid: 64 security.jail.param.host.domainname: 256 security.jail.param.host.hostname: 256 security.jail.param.host.: 0 security.jail.param.children.max: 0 security.jail.param.children.cur: 0 security.jail.param.dying: 0 security.jail.param.persist: 0 security.jail.param.devfs_ruleset: 0 security.jail.param.enforce_statfs: 0 security.jail.param.securelevel: 0 security.jail.param.path: 1024 security.jail.param.name: 256 security.jail.param.parent: 0 security.jail.param.jid: 0 security.jail.devfs_ruleset: 0 security.jail.enforce_statfs: 2 security.jail.mount_zfs_allowed: 0 security.jail.mount_procfs_allowed: 0 security.jail.mount_nullfs_allowed: 0 security.jail.mount_devfs_allowed: 0 security.jail.mount_allowed: 0 security.jail.chflags_allowed: 0 security.jail.allow_raw_sockets: 0 security.jail.sysvipc_allowed: 0 security.jail.socket_unixiproute_only: 1 security.jail.set_hostname_allowed: 1 security.jail.jail_max_af_ips: 255 security.jail.jailed: 0 Did you try the man page? Also there is often interesting comments in /usr/src Hope that helps. Waitman Gobble San Jose California There are no man pages for any MIBs Sorry, but im not at a computer now to check, but I believe it would be in the «jail» man page. Hopefully that's the right 411. Waitman man jail only talks about these few MIBs security.jail.mount_zfs_allowed: 0 security.jail.mount_procfs_allowed: 0 security.jail.mount_nullfs_allowed: 0 security.jail.mount_devfs_allowed: 0 security.jail.mount_allowed: 0 security.jail.chflags_allowed: 0 security.jail.allow_raw_sockets: 0 security.jail.sysvipc_allowed: 0 security.jail.socket_unixiproute_only: 1 security.jail.set_hostname_allowed: 1 security.jail.jail_max_af_ips: 255 security.jail.jailed: 0 which are set from the host only. What about the other security.jail.param.* MIBs where are they documented at? Rereading the man jail for 9.1 talks about securelevel as a jail parammeter. So correct me if I an wrong. All the security.jail.param.* MIBs are set in rc.conf or /etc/jail.conf file on a per jail bases by changing the word parm to the jailname? ___ 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: setting MIBs on a per jail bases
On Feb 6, 2013, at 5:57 PM, Fbsd8 fb...@a1poweruser.com wrote: Fleuriot Damien wrote: Running 8.3 here and the answer is no. On Feb 6, 2013, at 5:39 PM, Fbsd8 fb...@a1poweruser.com wrote: Is there a way to set these MIBs on a per jail bases? allow.mount.nullfs allow.raw_sockets cpuset.id securelevel Rereading the man jail for 9.1 talks about securelevel as a jail parammeter. So correct me if I an wrong. All the security.jail.param.* MIBs are set in rc.conf or /etc/jail.conf file on a per jail bases by changing the word parm to the jailname? I'm afraid I wouldn't know, I don't have a single 9.x box here. Does the man mention the secure level as a PER JAIL parameter, or as a systemwide parameter applied only to jails ? ___ 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: VirtualBox 4.1.22 and Bridged Network problems
I have built 4.2.6 and its working again! Thank you! :-) -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ 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
Restricting Periodic Scripts
I have a FreeBSD ZFS file server with tens of millions of files stored on it. But, the daily periodic scripts like /etc/periodic/security/110.neggrpperm and /etc/periodic/weekly/310.locate take hours iterating through those folders, and I just don't need them to be scanned. I see that I can edit /etc/locate.rc to fix the behavior for /etc/periodic/weekly/310.locate but I don't see a way to exclude folders from other scripts like /etc/periodic/security/110.neggrpperm from scanning them. Is there any way to prune out folders that I don't want scanned, or should I just disable those jobs? -- Tim Gustafson t...@ucsc.edu 831-459-5354 Baskin Engineering, Room 313A ___ 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 add unused space to an existing install
I have a FreeBSD 8.3 RELEASE box that we recently discovered only has part of the disk being used. This box has four 1TB drives in RAID 5, and df only shows 500MB of disk available. fdisk shows this: # fdisk -p # /dev/mfid0 g c364602 h255 s63 p 1 0xa5 63 1562363771 a 1 When I run the fdisk editor in sysinstall I see this: Disk name: mfid0 FDISK Partition Editor DISK Geometry: 364602 cyls/255 heads/63 sectors = 5857331130 sectors (2860024MB) Offset Size(ST)End Name PType Desc Subtype Flags 0 63 62- 12 unused0 63 1562363771 1562363833 mfid0s1 8freebsd 165 1562363834 4294981702 5857345535- 12 unused0 I want to capture all that unused space and add it to the server. fstab has this: # cat /etc/fstab # DeviceMountpoint FStype Options DumpPass# /dev/mfid0s1b noneswapsw 0 0 /dev/mfid0s1a / ufs rw 1 1 /dev/mfid0s1e /home ufs rw 2 2 /dev/mfid0s1d /tmpufs rw 2 2 /dev/mfid0s1f /usrufs rw 2 2 /dev/mfid0s1g /varufs rw 2 2 /dev/acd0 /cdrom cd9660 ro,noauto 0 0 When I try to create a new slice using fdisk, it doesn't seem to work. If I move to the label editor, I get this: FreeBSD Disklabel Editor Disk: mfid0 Partition name: mfid0s1 Free: 0 blocks (0MB) Part Mount Size Newfs Part Mount Size Newfs - - - - mfid0s1a none 2000MB * mfid0s1d none 65536MB * mfid0s1e none 4096MB * mfid0s1b swap65536MB SWAP mfid0s1f none 10240MB * mfid0s1g none601GB * As you can see mfid0s1g is 601GB, and according to fstab that's /var. Yet df -h shows: # df -h Filesystem SizeUsed Avail Capacity Mounted on /dev/mfid0s1a1.9G726M1.0G41%/ devfs1.0k1.0k 0B 100%/dev /dev/mfid0s1e3.9G 38M3.5G 1%/home /dev/mfid0s1d 62G6.6M 57G 0%/tmp /dev/mfid0s1f9.7G7.5G1.4G84%/usr /dev/mfid0s1g582G 39G496G 7%/var So apparently I'm not creating this new slice? It should be /dev/mfid0s1h, correct? How to I recapture the remaining 2+TB of space that's not being used? -- Paul Schmehl (pa...@utdallas.edu) Senior Information Security Analyst The University of Texas at Dallas http://www.utdallas.edu/infosecurity/ ___ 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: Restricting Periodic Scripts
On Wed, 6 Feb 2013 09:26:17 -0800, Tim Gustafson wrote: I have a FreeBSD ZFS file server with tens of millions of files stored on it. But, the daily periodic scripts like /etc/periodic/security/110.neggrpperm and /etc/periodic/weekly/310.locate take hours iterating through those folders, and I just don't need them to be scanned. I see that I can edit /etc/locate.rc to fix the behavior for /etc/periodic/weekly/310.locate but I don't see a way to exclude folders from other scripts like /etc/periodic/security/110.neggrpperm from scanning them. Is there any way to prune out folders that I don't want scanned, or should I just disable those jobs? You can disable them per /etc/periodic.conf (see examples in /etc/defaults/periodic.conf). To keep the functionality, but restrict it to a smaller amount of files, you could use the system's scripts as templates, make your own derivates (wich inclusion or exclusion rules) and place them in /usr/local/etc/periodic for the system to call them (which it will if they are present). You can add your custom configuration flags to /etc/periodic.conf and have your scripts source that file (like the system's scripts do). -- 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: Restricting Periodic Scripts
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2/6/13 12:26 PM, Tim Gustafson wrote: I have a FreeBSD ZFS file server with tens of millions of files stored on it. But, the daily periodic scripts like /etc/periodic/security/110.neggrpperm and /etc/periodic/weekly/310.locate take hours iterating through those folders, and I just don't need them to be scanned. I see that I can edit /etc/locate.rc to fix the behavior for /etc/periodic/weekly/310.locate but I don't see a way to exclude folders from other scripts like /etc/periodic/security/110.neggrpperm from scanning them. Is there any way to prune out folders that I don't want scanned, or should I just disable those jobs? Hi Tim, Have a look at this posting from 2012: http://forums.freebsd.org/archive/index.php/t-31846.html There is a patch for the script in there, but I didn't check to see if the author ever filed a PR. There's also a workaround that involves using the nosuid mount option, if that is acceptable in your environment. Regards, Greg - -- Greg Larkin http://www.FreeBSD.org/ - The Power To Serve http://www.sourcehosting.net/ - Ready. Set. Code. http://twitter.com/cpucycle/ - Follow you, follow me -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.13 (Darwin) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlESmkAACgkQ0sRouByUApB2kgCfalTZRa5GQlAZjcNXq5qxfA3e 2rwAoLCMoscJYLVuevYLjZGj9qYiIjZD =3yUC -END PGP SIGNATURE- ___ 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 add unused space to an existing install
On Wed, 06 Feb 2013 11:58:56 -0600, Paul Schmehl wrote: When I try to create a new slice using fdisk, it doesn't seem to work. If I move to the label editor, I get this: FreeBSD Disklabel Editor Disk: mfid0 Partition name: mfid0s1 Free: 0 blocks (0MB) Part Mount Size Newfs Part Mount Size Newfs - - - - mfid0s1a none 2000MB * mfid0s1d none 65536MB * mfid0s1e none 4096MB * mfid0s1b swap65536MB SWAP mfid0s1f none 10240MB * mfid0s1g none601GB * As you can see mfid0s1g is 601GB, and according to fstab that's /var. Yet df -h shows: # df -h Filesystem SizeUsed Avail Capacity Mounted on /dev/mfid0s1a1.9G726M1.0G41%/ devfs1.0k1.0k 0B 100%/dev /dev/mfid0s1e3.9G 38M3.5G 1%/home /dev/mfid0s1d 62G6.6M 57G 0%/tmp /dev/mfid0s1f9.7G7.5G1.4G84%/usr /dev/mfid0s1g582G 39G496G 7%/var So apparently I'm not creating this new slice? It should be /dev/mfid0s1h, correct? If you're creating a new slice, that would be mfid0s2, because mfid0s1 is the 1st slice (DOS primary partition) carrying the partitions a, swap, d, e, f, g. If I remember correctly, h is the last partition letter that can be assigned, so this one should be available. Problem: The 1st slice mfid0s1 is already of fixed size, so you cannot add a new partition here without growint that slice first. Attention, that step isn't free of danger and should be done with a backup at hand, just in case, and because you _always_ need a backup. :-) This problem is not a problem if you create a 2nd slice mfid0s2 to use it separately. If you can _really_ create mfid0s2 as a slice, you only need to format it, e. g. newfs -U /dev/mfid0s2 which creates mfid0s2c which in turn is called mfid0s2). You can then assign that new partition (the one covering the whole slice) to a new mountpoint, e. g. /data, /stuff or whatever you want. There are also means to merge this partition into some mountpoint that is already occupied, e. g. /home, maybe via mount -o union including all possibly negative consequences). How to I recapture the remaining 2+TB of space that's not being used? Without wiping the whole disk(s)? -- 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: about pfctl
I have a freebsd box and pf Works on it. I wish to see use of data for each ip address. When i execute pfctl -t tablename -vT showI can see usages of these ips. Pfctl lists all of ips. But how can i filter it for each ip address ? because i want to insert these data for each ip into a mysql table. Sounds like a job for sed(1)... Could you give me an example related to that ? ___ 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 add unused space to an existing install
On Wed, 6 Feb 2013, Polytropon wrote: On Wed, 06 Feb 2013 11:58:56 -0600, Paul Schmehl wrote: When I try to create a new slice using fdisk, it doesn't seem to work. If I move to the label editor, I get this: FreeBSD Disklabel Editor Disk: mfid0 Partition name: mfid0s1 Free: 0 blocks (0MB) Part Mount Size Newfs Part Mount Size Newfs - - - - mfid0s1a none 2000MB * mfid0s1d none 65536MB * mfid0s1e none 4096MB * mfid0s1b swap65536MB SWAP mfid0s1f none 10240MB * mfid0s1g none601GB * As you can see mfid0s1g is 601GB, and according to fstab that's /var. Yet df -h shows: # df -h Filesystem SizeUsed Avail Capacity Mounted on /dev/mfid0s1a1.9G726M1.0G41%/ devfs1.0k1.0k 0B 100%/dev /dev/mfid0s1e3.9G 38M3.5G 1%/home /dev/mfid0s1d 62G6.6M 57G 0%/tmp /dev/mfid0s1f9.7G7.5G1.4G84%/usr /dev/mfid0s1g582G 39G496G 7%/var So apparently I'm not creating this new slice? It should be /dev/mfid0s1h, correct? If you're creating a new slice, that would be mfid0s2, because mfid0s1 is the 1st slice (DOS primary partition) carrying the partitions a, swap, d, e, f, g. If I remember correctly, h is the last partition letter that can be assigned, so this one should be available. Problem: The 1st slice mfid0s1 is already of fixed size, so you cannot add a new partition here without growint that slice first. Attention, that step isn't free of danger and should be done with a backup at hand, just in case, and because you _always_ need a backup. :-) This problem is not a problem if you create a 2nd slice mfid0s2 to use it separately. If you can _really_ create mfid0s2 as a slice, you only need to format it, e. g. newfs -U /dev/mfid0s2 which creates mfid0s2c which in turn is called mfid0s2). You can then assign that new partition (the one covering the whole slice) to a new mountpoint, e. g. /data, /stuff or whatever you want. Yes, but creating FreeBSD partitions inside that slice allows them to be aligned. That may not be a problem on these 1T drives, some 1T drives have 512-byte blocks. Or the slow misaligned speed might be disguised by the slow RAID5 speed... fdisk and bsdlabel always align to fictional CHS values. gpart can align FreeBSD partitions. ___ 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 add unused space to an existing install
-Original Message- From: owner-freebsd-questi...@freebsd.org [mailto:owner-freebsd- questi...@freebsd.org] On Behalf Of Paul Schmehl Sent: Wednesday, February 06, 2013 9:59 AM To: FreeBSD Questions List Subject: How to add unused space to an existing install I have a FreeBSD 8.3 RELEASE box that we recently discovered only has part of the disk being used. This box has four 1TB drives in RAID 5, and df only shows 500MB of disk available. fdisk shows this: # fdisk -p # /dev/mfid0 g c364602 h255 s63 p 1 0xa5 63 1562363771 a 1 When I run the fdisk editor in sysinstall I see this: Disk name: mfid0 FDISK Partition Editor DISK Geometry: 364602 cyls/255 heads/63 sectors = 5857331130 sectors (2860024MB) Offset Size(ST)End Name PType Desc Subtype Flags 0 63 62- 12 unused0 63 1562363771 1562363833 mfid0s1 8freebsd 165 1562363834 4294981702 5857345535- 12 unused0 I want to capture all that unused space and add it to the server. fstab has this: # cat /etc/fstab # Device Mountpoint FStype Options Dump Pass# /dev/mfid0s1b noneswapsw 0 0 /dev/mfid0s1a / ufs rw 1 1 /dev/mfid0s1e /home ufs rw 2 2 /dev/mfid0s1d /tmpufs rw 2 2 /dev/mfid0s1f /usrufs rw 2 2 /dev/mfid0s1g /varufs rw 2 2 /dev/acd0 /cdrom cd9660 ro,noauto 0 0 When I try to create a new slice using fdisk, it doesn't seem to work. Did you try something like: echo p 2 165 * * | sudo fdisk -f- /dev/mfid0 ?? Afterward fdisk -p should show something like... # /dev/mfid0 g c364602 h255 s63 p 1 0xa5 63 1562363771 p 2 0xa5 num num a 1 And then you'll have /dev/mfid0s2 which you can do-with what you like (directly newfs the slice or create BSD partitions underneath that to further sub-divide into as many as 8 smaller units, /dev/mfid0s2[a-h]). If I move to the label editor, I get this: FreeBSD Disklabel Editor Disk: mfid0 Partition name: mfid0s1 Free: 0 blocks (0MB) Part Mount Size Newfs Part Mount Size Newfs - - - - mfid0s1a none 2000MB * mfid0s1d none 65536MB * mfid0s1e none 4096MB * mfid0s1b swap65536MB SWAP mfid0s1f none 10240MB * mfid0s1g none601GB * As you can see mfid0s1g is 601GB, and according to fstab that's /var. Yet df -h shows: # df -h Filesystem SizeUsed Avail Capacity Mounted on /dev/mfid0s1a1.9G726M1.0G41%/ devfs1.0k1.0k 0B 100%/dev /dev/mfid0s1e3.9G 38M3.5G 1%/home /dev/mfid0s1d 62G6.6M 57G 0%/tmp /dev/mfid0s1f9.7G7.5G1.4G84%/usr /dev/mfid0s1g582G 39G496G 7%/var So apparently I'm not creating this new slice? It should be /dev/mfid0s1h, correct? Let's not confuse slices (DOS partitions) with disklabels (BSD partitions). DOS partitions are (maximum 4 per disk): mfid0s1 mfid0s2 mfid0s3 mfid0s4 (according to your fdisk -p output, you're mfid0 disk is currently only using mfid0s1) BSD partitions are (maximum 8 per slice aka DOS partition): mfid0s1a mfid0s1b mfid0s1c mfid0s1d mfid0s1e mfid0s1f mfid0s1g mfid0s1h (according to your sysinstall output, you're mfid0s1 slice has 5 BSD partitions -- a, e, d, f, and g) How to I recapture the remaining 2+TB of space that's not being used? The easiest way to use your extra space is to not adjust one of those 5 BSD partitions, but instead create a new DOS partition (mfid0s2 as previously discussed above). However, if you *really* want to grow an existing BSD partition, this can be done (very carefully). First, you'll want to save the output of disklabel -r mfid0s1 to a text file. Next, you'll have to re-fdisk mfid0 so that the first slice covers the entire disk. Of course, re-mastering the slices does not affect the data, but it _will_ wipe out the BSD partition map (the disklabels; in other words, after using fdisk to adjust the slice size of the first DOS partition, disklabel -r mfid0s1 will no longer return what it had before -- you'll have no disklabels after), so the previous step of backing up the output of disklabel -r ... is paramount. Next, you'll have to restore the disklabel (using disklabel -e mfid0s1 and cross-referencing your backup text file) with one slight adjustment... You're going to use the *exact* values you backed up _EXCEPT_ you're going to make the last label (position-wise -- taking care to note the byte ranges
Re: Restricting Periodic Scripts
I have a FreeBSD ZFS file server with tens of millions of files stored on it. But, the daily periodic scripts like /etc/periodic/security/110.neggrpperm and /etc/periodic/weekly/310.locate take hours iterating through those folders, and I just don't need them to be scanned. I see that I can edit /etc/locate.rc to fix the behavior for /etc/periodic/weekly/310.locate but I don't see a way to exclude folders from other scripts like /etc/periodic/security/110.neggrpperm from scanning them. Is there any way to prune out folders that I don't want scanned, or should I just disable those jobs? Thanks to everyone who replied. I got some helpful suggestions from a few people, which all amounted to either disable the jobs or create your own custom version of those jobs. So for now, I'm just disabling them. I appreciate all the help. Thanks! -- Tim Gustafson t...@ucsc.edu 831-459-5354 Baskin Engineering, Room 313A ___ 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: sysctl security.jail.* descriptions
On 02/06/13 09:59, Fbsd8 wrote: Fbsd8 wrote: Waitman Gobble wrote: On Feb 6, 2013 7:17 AM, Fbsd8 fb...@a1poweruser.com wrote: Waitman Gobble wrote: On Feb 6, 2013 7:02 AM, Fbsd8 fb...@a1poweruser.com wrote: Where do I find the descriptions of what these jail MIBs do? ... security.jail.param.securelevel: 0 security.jail.param.path: 1024 security.jail.param.name: 256 security.jail.param.parent: 0 security.jail.param.jid: 0 ... What about the other security.jail.param.* MIBs where are they documented at? In the jail(8) main page, there's the following tidbit: | Jails have a set a core parameters, and kernel modules can add their | own jail parameters. The current set of available parameters can be | retrieved via ``sysctl -d security.jail.param''. Any parameters not | set will be given default values, often based on the current | environment. The sysctls do not themselves have values. Their useful parts are the associated types and descriptions (as well as their very existence). The descriptions are good for the above-mentioned sysctl -d, and the types are used by jail(8) to know how to set a particular parameter. Rereading the man jail for 9.1 talks about securelevel as a jail parammeter. So correct me if I an wrong. All the security.jail.param.* MIBs are set in rc.conf or /etc/jail.conf file on a per jail bases by changing the word parm to the jailname? There's not always a direct connection between the jail parameters and the current rc.conf values. The jail parameters are what you'd use in a jail.conf(5) file, or in the jail_jailname_parameters rc variable. - Jamie ___ 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
