Re: sysctl security.jail.* descriptions
Jamie Gritton wrote: 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 Yes I read man jail and issued the sysctl -d to get the list of MIBs I posted. So I am still left with no explanation of HOW to code these new jail MIBs in 9.X to enable them on a per jail bases. Any thoughts on how to do 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: sysctl security.jail.* descriptions
On 02/07/13 05:55, Fbsd8 wrote: Jamie Gritton wrote: 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 Yes I read man jail and issued the sysctl -d to get the list of MIBs I posted. So I am still left with no explanation of HOW to code these new jail MIBs in 9.X to enable them on a per jail bases. Any thoughts on how to do that? Well the jail(8) man page is all about setting these parameters. You might also want to take a look at jail.conf(5) which I mentioned. But don't think of them as MIBs anymore - the -d is the only thing you'll have to do directly with the sysctls. - 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
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
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: 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
A couple of new sysctl variables - maybe?
Greetings all, Having been working with various other UNIX variants as well it just occurred to me that in FreeBSD we do not have any simple method for retrieving either the hardware word length (memory bus width) or the kernel's basic word length. Usually these two are of course the same thing, but it is more a best practice convention than an absolute necessity. Anyhow on other systems like SunOS/Solaris there is isainfo -b and on Linux there is getconf LONG_BIT or something to check how many bits there are in the system's default word. Something similar would be nice in FreeBSD as well, though, I think the natural place for retrieving such a value would most likely be using sysctl. Maybe it would be OK to add two new entries to the sysctl tree: hw.wordbits and kern.wordbits, or something similar to the basic sysctl variables. The value should be just one constant number, usually 32 or 64 (= sizeof(long) * 8). This sort of addition to the kernel would make it a lot easier to create scripts which just do the right thing when run in anohter environment Just my 0,02 EUR worth... Cheers, // jau .--- ..- -.- -.- .-.- .-.-.-..- -.- -.- --- -. . -. /Jukka A. Ukkonen, Oxit Ltd, Finland /__ M.Sc. (sw-eng cs)(Phone) +358-500-606-671 / Internet: Jukka.Ukkonen(a)Oxit.Fi /Internet: jau(a)iki.fi v .--- .- ..- ...-.- .. -.- .. .-.-.- ..-. .. + + + + My opinions are mine and mine alone, not my employers. + + + + ___ 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
Get the dev.cpu.0.temperature from sysctl(3)
Hello, I would like to get the dev.cpu.0.temperature node from sysctlbyname(). It seems this node is an opaque type but how to check it and store it to the appropriate variable type ? Cheers, -- David Demelier ___ 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: Get the dev.cpu.0.temperature from sysctl(3)
On Tue, May 03, 2011 at 10:12:33AM +0200, David Demelier wrote:
Hello,
I would like to get the dev.cpu.0.temperature node from sysctlbyname().
It seems this node is an opaque type but how to check it and store it to
the appropriate variable type ?
The best way to determine this is to read the source. I did that some time ago
to fix the temperature display in sysutils/conky.
The sysctl dev.cpu.0.temperature returns an integer, see
/sys/dev/coretemp/coretemp.c (look for the string temperature), and you'll
see:
/*
* Add the temperature MIB to dev.cpu.N.
*/
sc-sc_oid = SYSCTL_ADD_PROC(device_get_sysctl_ctx(pdev),
SYSCTL_CHILDREN(device_get_sysctl_tree(pdev)),
OID_AUTO, temperature,
CTLTYPE_INT | CTLFLAG_RD,
dev, 0, coretemp_get_temp_sysctl, IK,
Current temperature);
If you look at the definition of coretemp_get_temp_sysctl in the same file:
coretemp_get_temp_sysctl(SYSCTL_HANDLER_ARGS)
{
device_t dev = (device_t) arg1;
int temp;
temp = coretemp_get_temp(dev) * 10 + TZ_ZEROC;
return (sysctl_handle_int(oidp, temp, 0, req));
}
So the returned value is an 'int'. Note that TZ_ZEROC is #defined as 2732 at
the beginning of the file. The returned value is therefore the temperature
in Kelvin times ten.
On my machine, it gives e.g.:
sysctl dev.cpu.0.temperature
dev.cpu.0.temperature: 46.0C
If we check the 'raw' return value;
sysctl -b dev.cpu.0.temperature|hd
78 0c 00 00 |x...|
0004
Running this value with the abovementioned algorithm in reverse through a
calculator, we get
(0x0c78-2732)/10 = 46°C
Hope this helps.
Roland
--
R.F.Smith http://www.xs4all.nl/~rsmith/
[plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated]
pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725)
pgpXPbScJFToy.pgp
Description: PGP signature
Re: Get the dev.cpu.0.temperature from sysctl(3)
On 03/05/2011 21:40, Roland Smith wrote:
On Tue, May 03, 2011 at 10:12:33AM +0200, David Demelier wrote:
Hello,
I would like to get the dev.cpu.0.temperature node from sysctlbyname().
It seems this node is an opaque type but how to check it and store it to
the appropriate variable type ?
The best way to determine this is to read the source. I did that some time ago
to fix the temperature display in sysutils/conky.
The sysctl dev.cpu.0.temperature returns an integer, see
/sys/dev/coretemp/coretemp.c (look for the string temperature), and you'll
see:
/*
* Add the temperature MIB to dev.cpu.N.
*/
sc-sc_oid = SYSCTL_ADD_PROC(device_get_sysctl_ctx(pdev),
SYSCTL_CHILDREN(device_get_sysctl_tree(pdev)),
OID_AUTO, temperature,
CTLTYPE_INT | CTLFLAG_RD,
dev, 0, coretemp_get_temp_sysctl, IK,
Current temperature);
If you look at the definition of coretemp_get_temp_sysctl in the same file:
coretemp_get_temp_sysctl(SYSCTL_HANDLER_ARGS)
{
device_t dev = (device_t) arg1;
int temp;
temp = coretemp_get_temp(dev) * 10 + TZ_ZEROC;
return (sysctl_handle_int(oidp,temp, 0, req));
}
So the returned value is an 'int'. Note that TZ_ZEROC is #defined as 2732 at
the beginning of the file. The returned value is therefore the temperature
in Kelvin times ten.
On my machine, it gives e.g.:
sysctl dev.cpu.0.temperature
dev.cpu.0.temperature: 46.0C
If we check the 'raw' return value;
sysctl -b dev.cpu.0.temperature|hd
78 0c 00 00 |x...|
0004
Running this value with the abovementioned algorithm in reverse through a
calculator, we get
(0x0c78-2732)/10 = 46°C
Hope this helps.
Roland
Thanks a lot!
I had a look into the src and I saw the format IK used to register the
sysctl node but I was also surprised that IK was not defined in man
sysctl(9)
But I finally understood that K should means Kelvin :)
Cheers,
--
David Demelier
___
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
trying to sysctl(3) a char value
Hello,
Since I cannot adjust the brightness on my HP Probook because it sucks
I'm writing a small script that can be use instead. I need to sysctl
the following sysctl variables :
hw.acpi.video.lcd0.brightness
hw.acpi.video.lcd0.levels
the -brightness one is easy since it's an integer, but the levels is
possibly a char :
mark...@melon ~ $ sysctl hw.acpi.video.lcd0.brightness
hw.acpi.video.lcd0.brightness: 90
mark...@melon ~ $ sysctl hw.acpi.video.lcd0.levels
hw.acpi.video.lcd0.levels: 100 50 0 5 10 15 20 25 30 33 36 40 43 46 50
55 60 65 70 75 80 83 86 90 93 96 100
How can I store the content of hw.acpi.video.lcd0.levels? This small
code doesn't work :
#include stdio.h
#include stdlib.h
#include sys/types.h
#include sys/sysctl.h
int
main(int argc, char *argv[])
{
char buf[128];
size_t len;
len = sizeof (buf);
if (sysctlbyname(hw.acpi.video.lcd0.levels, buf, len, NULL, 0) ==
-1) {
perror(sysctl);
return -1;
}
printf(levels = %s\n, buf);
}
mark...@melon ~ $ ./a.out
levels = d
Kind 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: trying to sysctl(3) a char value
In the last episode (Nov 24), David DEMELIER said: Since I cannot adjust the brightness on my HP Probook because it sucks I'm writing a small script that can be use instead. I need to sysctl the following sysctl variables : hw.acpi.video.lcd0.brightness hw.acpi.video.lcd0.levels the -brightness one is easy since it's an integer, but the levels is possibly a char : mark...@melon ~ $ sysctl hw.acpi.video.lcd0.brightness hw.acpi.video.lcd0.brightness: 90 mark...@melon ~ $ sysctl hw.acpi.video.lcd0.levels hw.acpi.video.lcd0.levels: 100 50 0 5 10 15 20 25 30 33 36 40 43 46 50 55 60 65 70 75 80 83 86 90 93 96 100 Looking at the source, that sysctl definition is CTLTYPE_OPAQUE with a display format of I, which means that it's just an array of integers. Print each one in a loop. You can also take a look at /usr/src/sbin/sysctl/sysctl.c to see how it printed the numbers. -- 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: trying to sysctl(3) a char value
2010/11/24 Dan Nelson dnel...@allantgroup.com: In the last episode (Nov 24), David DEMELIER said: Since I cannot adjust the brightness on my HP Probook because it sucks I'm writing a small script that can be use instead. I need to sysctl the following sysctl variables : hw.acpi.video.lcd0.brightness hw.acpi.video.lcd0.levels the -brightness one is easy since it's an integer, but the levels is possibly a char : mark...@melon ~ $ sysctl hw.acpi.video.lcd0.brightness hw.acpi.video.lcd0.brightness: 90 mark...@melon ~ $ sysctl hw.acpi.video.lcd0.levels hw.acpi.video.lcd0.levels: 100 50 0 5 10 15 20 25 30 33 36 40 43 46 50 55 60 65 70 75 80 83 86 90 93 96 100 Looking at the source, that sysctl definition is CTLTYPE_OPAQUE with a display format of I, which means that it's just an array of integers. Print each one in a loop. You can also take a look at /usr/src/sbin/sysctl/sysctl.c to see how it printed the numbers. -- Dan Nelson dnel...@allantgroup.com Thank you, it works ! -- 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
BUG: sysctl net.isr.swi_count negative value
Hi, Freebsd-questions. net.isr.swi_count: -1692211928 as I think count can not be negative. in this case it is. Is this a bug or negative value means some special? -- С уважением, Коньков mailto:kes-...@yandex.ru ___ 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: BUG: sysctl net.isr.swi_count negative value
On Sat Nov 13 10, ??? ??? wrote: Hi, Freebsd-questions. net.isr.swi_count: -1692211928 as I think count can not be negative. in this case it is. Is this a bug or negative value means some special? what is the output of 'uname -a'? looks like a 32 bit integer is being used for net.isr.swi_count which you managed to overrun. i'm running HEAD and that sysctl parameter doesn't exist: otaku% sysctl net.isr.swi_count sysctl: unknown oid 'net.isr.swi_count' seems pluknet posted the same one year ago [1] cheers. alex [1] http://markmail.org/message/qc34d5z6uyyet7nx -- ? ?, ??? mailto:kes-...@yandex.ru -- 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
system slow after tuning cpu speed with sysctl
Hi all, I used to change my CPU speed via sysctl: sysctl dev.cpu.0.freq=1650 I did that because that helped me to decrease the CPU temperature, and such speed was enough. This way went well and I did that after logging into the system via ssh. (I have some troubles with `powerd` so I have to use `sysctl` manually.) Yesterday, because `sysctl` often required root permission, I wrote a small script that could help to to change cpu speed via ssh ./my_script.sh 1650 = ssh t...@localhost sysctl dev.cpu.0.freq=1650 (my password goes here) Then I suddenly found that the system was very very slow after the above call, though I ran nothing (except for bash, top). Being afraid that something went wrong, I just moved to the maximum speed: ssh t...@localhost sysctl dev.cpu.0.freq=2200 but this couldn't help. (Using `dmesg` I saw a line Device wasn't configured) Now I can't change my cpu speed anymore: If I switch from 2200 to 1925 (the next lower value), the system would be slowed down and I can't do anything (because it is very very slow). The only way is to reboot. And here is another strange thing: after the FreeBSD sends the last message of its reboot process, the system halts with black-blank screen; then I have to unplug the power supply (an external adapter), unplug the battery, wait for some seconds, plug the battery / power supply before turning the system on. I am using FreeBSD 8.0 (RELEASE) on a laptop with a custom kernel http://viettug.org/attachments/download/349/icy_kernel_20100119.txt The full output of my `sysctl dev.cpu.` /= dev.cpu.0.%desc: ACPI CPU dev.cpu.0.%driver: cpu dev.cpu.0.%location: handle=\_PR_.CPU0 dev.cpu.0.%pnpinfo: _HID=none _UID=0 dev.cpu.0.%parent: acpi0 dev.cpu.0.freq: 2200 dev.cpu.0.freq_levels: 2200/15975 1925/13978 1650/11981 1375/9984 1100/5795 962/5070 825/4346 687/3621 550/2320 481/2030 412/1740 343/1450 275/1160 206/870 137/580 68/290 dev.cpu.0.cx_supported: C1/0 dev.cpu.0.cx_lowest: C1 dev.cpu.0.cx_usage: 100.00% last 500us dev.cpu.1.%desc: ACPI CPU dev.cpu.1.%driver: cpu dev.cpu.1.%location: handle=\_PR_.CPU1 dev.cpu.1.%pnpinfo: _HID=none _UID=0 dev.cpu.1.%parent: acpi0 dev.cpu.1.cx_supported: C1/0 dev.cpu.1.cx_lowest: C1 dev.cpu.1.cx_usage: 100.00% last 500us \= I doubt that there was something failed with my hardware :( Quite disappointed 'til now. Could you give me advice? Thank you for your helps, Regards, -- Anh Ky Huynh ___ 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 kern.geom.debugflags ERROR when using Sysinstall to format HD (FreeBsd 7.2 STABLE)
Hi folks!! Trying to create a new Ufs on a HD using sysinstall. im getting the following error: ERROR: Unable to write data to disk ad10! │ │ │ │To edit the labels on a running system set │ │sysctl kern.geom.debugflags=16 and try again any ideas? Cheers! ___ 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 kern.geom.debugflags ERROR when using Sysinstall to format HD (FreeBsd 7.2 STABLE)
Jeronimo Calvo wrote: Hi folks!! Trying to create a new Ufs on a HD using sysinstall. im getting the following error: ERROR: Unable to write data to disk ad10! │ │ │ │To edit the labels on a running system set │ │sysctl kern.geom.debugflags=16 and try again any ideas? At a guess, I'd say you need to set sysctl kern.geom.debugflags=16 and try again... Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
gnome2 - sysctl
Hello, Sometimes when I send a message with pidgin, or evolution, the application shuts down. Is there an option with sysctl, that would prevent this to happen? I'm running FreeBSD 7.2 stable - gnome2 Regards, Roy. ___ 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 gnome2
Hello, Sometimes when I send a message with pidgin, or evolution, the application shuts down. Is there an option with sysctl, that would prevent this to happen? I'm running FreeBSD 7.2 stable - gnome2 Regards, Roy. ___ 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 gnome2
On Sun, 05 Jul 2009 01:36:33 +0200 Roy Stuivenberg roys1...@gmail.com wrote: Hello, Sometimes when I send a message with pidgin, or evolution, the application shuts down. Is there an option with sysctl, that would prevent this to happen? sysctl is an interface to the kernel, it doesn't know anything about third-party, high-level applications. The behaviour you describe sounds more like a bug than a feature, but if there is a way to turn it off it will be in the gnome or application configuration. ___ 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
calculate RAM for sysctl kern.maxfiles
I need use more 128 000 kern.maxfilesperproc for the process how can i calculate hardware for this purpose (RAM i think)? will use 7.1, 7.2 AMD64 Thanks for help Regards Valentin ___ 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
dmesg: sysctl kern.msgbuf Cannot allocate memory
After searching google and various man pages, I'm not finding out what it actually means, anyone care to shed some light? During boot: dmesg: sysctl kern.msgbuf Cannot allocate memory #sysctl -a |grep msgbuf kern.msgbuf_clear: 0 kern.msgbuf: kern.consmsgbuf_size: 8192 security.bsd.unprivileged_read_msgbuf: 1 -- Over the years I've come to regard you as people I've met. ___ 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
IPFW, KERNEL, sysctl: has no effect changing DUMMYNET.io_fast
Hi, Freebsd-questions. This change sysctl net.inet.ip.dummynet.io_fast=1 has no effect for packet flow, bug man says: Fast mode allows certain packets to bypass dummynet scheduler if packet flow does not exceed pipe's bandwidth flow does not exceed pipe limit, but packet flow latency is affected ipfw pipe 1 config bw 64kbit/s ipfw add 1 pipe 1 all from any to any No any trafic except ping: ping some.lan.machine with rules above ping is about 8ms, without them 1ms Does I understand corrent Fast mode when I ping I do flow less than 64Kbit/s so packet must bypass scheduler and must have latency 1ms? -- С уважением, KES mailto:kes-...@yandex.ru ___ 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 machdep.independent_wallclock
hi...
what is the exact function of this sysctl setting?
I'm guessing it's something to do with Xen, having seen a few
references in Linux for xen.machdep.independent_wallclock.
Have a look here:
http://docs.xensource.com/XenServer/4.0.1/guest/ch04s06.html
yeah, I know that sysctl from linux, but I wasn't quite sure if it is
the same in FreeBSD, since it's known as 'xen.independent_wallclock' in
linux and 'machdep.independent_wallclock' in FreeBSD.
I started reading the C-code of FreeBSD, and from my understanding the
function 'should' be the same, as it's really linked to the clock
handling with XEN in FreeBSD.
but from my understanding it's not completly implemented in 8-CURRENT
(as of 15 jan 2009; see the last lines):
/*
* Write system time back to RTC.
*/
static void
domu_resettodr(void)
{
unsigned long tm;
int s;
dom0_op_t op;
struct shadow_time_info *shadow;
shadow = per_cpu(shadow_time, smp_processor_id());
if (xen_disable_rtc_set)
return;
s = splclock();
tm = time_second;
splx(s);
tm -= tz_minuteswest * 60 + (wall_cmos_clock ? adjkerntz : 0);
if ((xen_start_info-flags SIF_INITDOMAIN)
!independent_wallclock)
{
op.cmd = DOM0_SETTIME;
op.u.settime.secs= tm;
op.u.settime.nsecs = 0;
op.u.settime.system_time = shadow-system_timestamp;
HYPERVISOR_dom0_op(op);
update_wallclock();
} else if (independent_wallclock) {
/* notyet */
;
}
}
is that correct???
greetz
olli
___
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 machdep.independent_wallclock
hi... what is the exact function of this sysctl setting? I couldn't find any documentation on it. greetz olli ___ 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 machdep.independent_wallclock
2009/1/14 Mister Olli mister.o...@googlemail.com hi... what is the exact function of this sysctl setting? I'm guessing it's something to do with Xen, having seen a few references in Linux for xen.machdep.independent_wallclock. Have a look here: http://docs.xensource.com/XenServer/4.0.1/guest/ch04s06.html I couldn't find any documentation on it. greetz olli ___ 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: /var/log/messages logs appear in the output of sysctl -a
Eitan Shefi eit...@mellanox.co.il writes: I run sysctl -a | less why? DES -- Dag-Erling Smørgrav - d...@des.no ___ 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
/var/log/messages logs appear in the output of sysctl -a
I am testing a NIC driver. I found it's logs and /var/log/messages logs in the output of sysctl -a: I run sysctl -a | less, and there I find: kern.devstat.version: 6 kern.devstat.generation: 137 kern.devstat.numdevs: 1 kern.kobj_methodcount: 143 kern.log_wakeups_per_second: 5 kern.msgbuf_clear: 0 kern.msgbuf: ound file system checks in 60 seconds. 118 mtnic0: FW version:2.6.0 mtnic0: Board ID: mtnic0: Using 1 tx rings for port:1 [4096] mtnic0: Using 4 rx rings for port:1 [1024] mtnic0: Using 1 tx rings for port:2 [4096] mtnic0: Using 4 rx rings for port:2 [1024] mtnic0: Initializing MSIX mtnic0: Enabling MSI-X (11 vectors) mtnic0: Board ID:MT_0BD0110004 mtnic0: [ITHREAD] mtnic0: Activating port:1 mtnic0: Ethernet address: 00:02:c9:03:35:20 mtnic0: Activating port:2 mtnic1: Ethernet address: 00:02:c9:03:35:21 mtnic0: [ITHREAD] mtnic0: [ITHREAD] mtnic0: mtnic0: mtnic0: mtnic0: Port 1 - link up mtnic0: [ITHREAD] mtnic0: [ITHREAD] mtnic0: [ITHREAD] Limiting icmp ping response from 300 to 200 packets/sec Limiting icmp ping response from 300 to 200 packets/sec Limiting icmp ping response from 1497 to 200 packets/sec Limiting icmp ping response from 1500 to 200 packets/sec Limiting icmp ping response from 1498 to 200 packets/sec Limiting icmp ping response from 1500 to 200 packets/sec Any idea how can such logs apear in sysctl -a ? Thanks, Eitan ___ 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: /var/log/messages logs appear in the output of sysctl -a
On Wed, 7 Jan 2009 13:30:20 +0200 Eitan Shefi eit...@mellanox.co.il wrote: I am testing a NIC driver. I found it's logs and /var/log/messages logs in the output of sysctl -a: I run sysctl -a | less, and there I find: kern.devstat.version: 6 kern.devstat.generation: 137 kern.devstat.numdevs: 1 kern.kobj_methodcount: 143 kern.log_wakeups_per_second: 5 kern.msgbuf_clear: 0 kern.msgbuf: ound file system checks in 60 seconds. 118 mtnic0: FW version:2.6.0 mtnic0: Board ID: mtnic0: Using 1 tx rings for port:1 [4096] mtnic0: Using 4 rx rings for port:1 [1024] mtnic0: Using 1 tx rings for port:2 [4096] mtnic0: Using 4 rx rings for port:2 [1024] mtnic0: Initializing MSIX mtnic0: Enabling MSI-X (11 vectors) mtnic0: Board ID:MT_0BD0110004 mtnic0: [ITHREAD] mtnic0: Activating port:1 mtnic0: Ethernet address: 00:02:c9:03:35:20 mtnic0: Activating port:2 mtnic1: Ethernet address: 00:02:c9:03:35:21 mtnic0: [ITHREAD] mtnic0: [ITHREAD] mtnic0: mtnic0: mtnic0: mtnic0: Port 1 - link up mtnic0: [ITHREAD] mtnic0: [ITHREAD] mtnic0: [ITHREAD] Limiting icmp ping response from 300 to 200 packets/sec Limiting icmp ping response from 300 to 200 packets/sec Limiting icmp ping response from 1497 to 200 packets/sec Limiting icmp ping response from 1500 to 200 packets/sec Limiting icmp ping response from 1498 to 200 packets/sec Limiting icmp ping response from 1500 to 200 packets/sec Any idea how can such logs apear in sysctl -a ? If you were viewing this as root on the console then you were simply seeing kernel output interleaved with the output from sysctl. --- Gary Jennejohn ___ 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: /var/log/messages logs appear in the output of sysctl -a
On Wed, 7 Jan 2009, 13:14+0100, Gary Jennejohn wrote: On Wed, 7 Jan 2009 13:30:20 +0200 Eitan Shefi eit...@mellanox.co.il wrote: I am testing a NIC driver. I found it's logs and /var/log/messages logs in the output of sysctl -a: I run sysctl -a | less, and there I find: kern.devstat.version: 6 kern.devstat.generation: 137 kern.devstat.numdevs: 1 kern.kobj_methodcount: 143 kern.log_wakeups_per_second: 5 kern.msgbuf_clear: 0 kern.msgbuf: ound file system checks in 60 seconds. 118 mtnic0: FW version:2.6.0 mtnic0: Board ID: mtnic0: Using 1 tx rings for port:1 [4096] mtnic0: Using 4 rx rings for port:1 [1024] mtnic0: Using 1 tx rings for port:2 [4096] mtnic0: Using 4 rx rings for port:2 [1024] mtnic0: Initializing MSIX mtnic0: Enabling MSI-X (11 vectors) mtnic0: Board ID:MT_0BD0110004 mtnic0: [ITHREAD] mtnic0: Activating port:1 mtnic0: Ethernet address: 00:02:c9:03:35:20 mtnic0: Activating port:2 mtnic1: Ethernet address: 00:02:c9:03:35:21 mtnic0: [ITHREAD] mtnic0: [ITHREAD] mtnic0: mtnic0: mtnic0: mtnic0: Port 1 - link up mtnic0: [ITHREAD] mtnic0: [ITHREAD] mtnic0: [ITHREAD] Limiting icmp ping response from 300 to 200 packets/sec Limiting icmp ping response from 300 to 200 packets/sec Limiting icmp ping response from 1497 to 200 packets/sec Limiting icmp ping response from 1500 to 200 packets/sec Limiting icmp ping response from 1498 to 200 packets/sec Limiting icmp ping response from 1500 to 200 packets/sec Any idea how can such logs apear in sysctl -a ? If you were viewing this as root on the console then you were simply seeing kernel output interleaved with the output from sysctl. This is just an output from sysctl kern.msgbuf. -- Maxim Konovalov ___ 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: /var/log/messages logs appear in the output of sysctl -a
You are looking at the kernel message buffer with 'sysctl -a'. (kern.msgbuf). Nothing wrong with that. //Remko -- /\ 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: /var/log/messages logs appear in the output of sysctl -a
On Wednesday 07 January 2009 12:30:20 Eitan Shefi wrote: I am testing a NIC driver. I found it's logs and /var/log/messages logs in the output of sysctl -a: I run sysctl -a | less, and there I find: kern.devstat.version: 6 kern.devstat.generation: 137 kern.devstat.numdevs: 1 kern.kobj_methodcount: 143 kern.log_wakeups_per_second: 5 kern.msgbuf_clear: 0 kern.msgbuf: ound file system checks in 60 seconds. ^ ... Any idea how can such logs apear in sysctl -a ? The kernel message buffer is exported via a sysctl (kern.msgbuf) and as you asked to see all sysctl - this one is included, too. This is not a message for freebsd-hackers@ btw! -- /\ Best regards, | mla...@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mla...@efnet / \ 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: /var/log/messages logs appear in the output of sysctl -a
On Wed, Jan 07, 2009 at 01:30:20PM +0200, Eitan Shefi wrote: I am testing a NIC driver. I found it's logs and /var/log/messages logs in the output of sysctl -a: I run sysctl -a | less, and there I find: [..] kern.msgbuf: ound file system checks in 60 seconds. 118 mtnic0: FW version:2.6.0 mtnic0: Board ID: mtnic0: Using 1 tx rings for port:1 [4096] mtnic0: Using 4 rx rings for port:1 [1024] mtnic0: Using 1 tx rings for port:2 [4096] mtnic0: Using 4 rx rings for port:2 [1024] [..] Any idea how can such logs apear in sysctl -a ? kern.msgbuf dumps so called 'message buf' containing messages printed by the kernel (for example by a NIC driver). It's accessible also via /dev/klog and syslogd uses it as a source for /var/log/messages. -- Mateusz Guzik mjguzik at gmail.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
documentation for sysctl MIB
Hello maillist, I have to small question - Where i can get documentation for description some base sysctl variables? - And, what the diffrence between sysctl hw.machine hw.machine_arch ? For example, i extract i386 installation, but my hardware is EM64T and supporting AMD64 distribution correctly. Both variable get i386 value. One of them must be amd64? Thanks for your time ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: documentation for sysctl MIB
Ole wrote: Hello maillist, I have to small question - Where i can get documentation for description some base sysctl variables? - And, what the diffrence between sysctl hw.machine hw.machine_arch ? try sysctl -d $oid for example: [EMAIL PROTECTED] (10:23:56 ~) 0 $ sysctl -d hw.machine hw.machine_arch hw.machine: Machine class hw.machine_arch: System architecture [EMAIL PROTECTED] (10:24:12 ~) 0 $ sysctl hw.machine hw.machine_arch hw.machine: amd64 hw.machine_arch: amd64 For example, i extract i386 installation, but my hardware is EM64T and supporting AMD64 distribution correctly. Both variable get i386 value. One of them must be amd64? Thanks for your time ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
sysctl kern.msgbuf changed in 7.0?
On my FreeBSD 6 box, sysctl kern.msgbuf shows the same content as dmesg But on FreeBSD 7, kern.msgbuf is empty. Has something changed? Thanks, Skye -- View this message in context: http://www.nabble.com/sysctl-kern.msgbuf-changed-in-7.0--tp19679848p19679848.html Sent from the freebsd-questions mailing list archive at Nabble.com. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
SYSCTL error message upon bootup
For no apparent reason, the following error message has suddenly started showing up when I reboot the machine: sysctl: unknown oid 'net.fibs' I am running FBSD-6.3 presently. Is this error important and if so, what can I do to correct it? Thanks! -- Gerard [EMAIL PROTECTED] All extremists should be taken out and shot. signature.asc Description: PGP signature
Re: SYSCTL error message upon bootup
On Tue, 2 Sep 2008 11:11:20 -0400, Gerard [EMAIL PROTECTED] wrote: For no apparent reason, the following error message has suddenly started showing up when I reboot the machine: sysctl: unknown oid 'net.fibs' I am running FBSD-6.3 presently. Is this error important and if so, what can I do to correct it? On FreeBSD 7, net.fibs is a valid oid. Can you determine when (in the booting process) this message is shown? Maybe you have a setting of net.fibs in /etc/sysctl.conf, or maybe this is a value set by some software package? % sysctl net.fibs net.fibs: 1 In /usr/include/net/route.h, something regarding FIBS is mentioned... -- 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 [EMAIL PROTECTED]
Re: SYSCTL error message upon bootup
On Tue, 2 Sep 2008 11:11:20 -0400 Gerard [EMAIL PROTECTED] wrote: For no apparent reason, the following error message has suddenly started showing up when I reboot the machine: sysctl: unknown oid 'net.fibs' I am running FBSD-6.3 presently. Is this error important and if so, what can I do to correct it? Thanks! Do you have apache? http://groups.google.com/group/mailing.freebsd.ports-bugs/browse_thread/thread/b8f17e78869e738f ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SYSCTL error message upon bootup
On Tue, 2 Sep 2008 17:36:36 +0200 Polytropon [EMAIL PROTECTED] wrote: [snip] On FreeBSD 7, net.fibs is a valid oid. Can you determine when (in the booting process) this message is shown? Maybe you have a setting of net.fibs in /etc/sysctl.conf, or maybe this is a value set by some software package? % sysctl net.fibs net.fibs: 1 In /usr/include/net/route.h, something regarding FIBS is mentioned... I could not find any mention of it in the 'route.h' file, nor is there anything in the 'sysctl.conf' file. The message is displayed just before the 'login' prompt. How can I determine what program is causing this to occur? -- Gerard [EMAIL PROTECTED] I am firm. You are obstinate. He is a pig-headed fool. Katharine Whitehorn signature.asc Description: PGP signature
Re: SYSCTL error message upon bootup
On Tue, 2 Sep 2008 17:15:18 +0100 RW [EMAIL PROTECTED] wrote: Do you have apache? http://groups.google.com/group/mailing.freebsd.ports-bugs/browse_thread/thread/b8f17e78869e738f Yes, and come to think about it, this problem just started happening after I updated it. I assume that the patch listed above will be incorporated into the port shortly. Thanks! -- Gerard [EMAIL PROTECTED] If Karl, instead of writing a lot about Capital, had made a lot of Capital, it would have been much better. Karl Marx's Mother signature.asc Description: PGP signature
Re: SYSCTL error message upon bootup
On Tue, 2 Sep 2008 12:51:13 -0400, Gerard [EMAIL PROTECTED] wrote: I could not find any mention of it in the 'route.h' file, [...] /usr/include/net/route.h, Version 1.65.2.3, line 85: 85:extern u_int rt_numfibs; /* number fo usable routing tables */ That's the only occurance I found. FIBS seems to have something to do with multiple routing tables, a feature that needs to be enabled via a kernel option; I'm not sure if this has been present in FreeBSD 6 already. [...] nor is there anything in the 'sysctl.conf' file. So the setting isn't requested via /etc/rc.d/sysctl at startup (which reads from /etc/sysctl.conf), but from another service. If it was, # /etc/rc.d/sysctl restart would lead to the same error message The message is displayed just before the 'login' prompt. As RW mentioned, Do you have apache?, is there something like Starting additional deamons: apache sysctl: unknown oid 'net.fibs' How can I determine what program is causing this to occur? What's near the error message? Usually the startup notification prior to this message should identify the program that causes this message. -- 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 [EMAIL PROTECTED]
Re: sysctl enabled but HAL non-existant (Reid Linnemann)
I've installed HAL and the same message comes up with the gnome desktop- and this happens in the install of NetBSD that I also have- the HAL problem of not being enabled or installed. I may be wrong in assuming this; but, isn't there some basic compatibility between bsd systems that what would work for freebsd and mounting would also work for netbsd? chmod 0777 /dev/acd0 and chmod 0777 /dev/cd0a allows me to see the icons in konqueror and nautilus. sysctrl v allows me some access but full access is only as root. I did a search for a command line that would help me set up HAL for both desktops. _ Introducing Live Search cashback . It's search that pays you back! http://search.live.com/cashback/?pkw=form=MIJAAF/publ=HMTGL/crea=introsrchcashback___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sysctl enabled but HAL non-existant
Desmond Chapman wrote: The media shows up in konqueror as a normal user but I cannot mount it. there is no reference to hal with an apropos search except for ath_hal. What am I doing wrong? What else do I add to make the cd easily mountable? _ The i’m Talkathon starts 6/24/08. For now, give amongst yourselves. http://www.imtalkathon.com?source=TXT_EML_WLH_LearnMore_GiveAmongst___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Perhaps you're looking for /usr/ports/sysutils/hal. HAL is not part of the FreeBSD base system. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
sysctl enabled but HAL non-existant
The media shows up in konqueror as a normal user but I cannot mount it. there is no reference to hal with an apropos search except for ath_hal. What am I doing wrong? What else do I add to make the cd easily mountable? _ The i’m Talkathon starts 6/24/08. For now, give amongst yourselves. http://www.imtalkathon.com?source=TXT_EML_WLH_LearnMore_GiveAmongst___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
sysctl...
aJTiM writes: I am running FreeBSD 7 beta4. When I start a computer and os loading I got one message which I don't know why and how could I save a problem if it is a problem. Beta 4 works very good and I don't have problems. hw.acpi.cpu.cx_lowest: C1 sysctl: hw.acpi.cpu.cx_lowest: Invalid argument Same here. Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
sysctl...
Hi! I am running FreeBSD 7 beta4. When I start a computer and os loading I got one message which I don't know why and how could I save a problem if it is a problem. Beta 4 works very good and I don't have problems. hw.acpi.cpu.cx_lowest: C1 sysctl: hw.acpi.cpu.cx_lowest: Invalid argument Thanks in advance. -- It just doesn't seem right to go over the river and through the woods to Grandmother's condo. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sysctl...
On Dec 27, 2007 2:20 PM, aJTiM [EMAIL PROTECTED] wrote: Hi! I am running FreeBSD 7 beta4. When I start a computer and os loading I got one message which I don't know why and how could I save a problem if it is a problem. Beta 4 works very good and I don't have problems. hw.acpi.cpu.cx_lowest: C1 sysctl: hw.acpi.cpu.cx_lowest: Invalid argument Thanks in advance. -- It just doesn't seem right to go over the river and through the woods to Grandmother's condo. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] I am not running 7.0, so I am just guessing, but I am assuming you changed that option in /etc/sysctl.conf (or possibly copied your /etc directory from an older machine to the 7.0 machine). That would be the why you are getting that message during boot. The reason the message is appearing at all is most likely because that is not a current sysctl variable/option. I would check the sysctl manuals for that. -- Chad M. Gross ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sysctl...
On Thu, Dec 27, 2007 at 02:28:34PM -0500, Chad Gross wrote: On Dec 27, 2007 2:20 PM, aJTiM [EMAIL PROTECTED] wrote: Hi! I am running FreeBSD 7 beta4. When I start a computer and os loading I got one message which I don't know why and how could I save a problem if it is a problem. Beta 4 works very good and I don't have problems. hw.acpi.cpu.cx_lowest: C1 sysctl: hw.acpi.cpu.cx_lowest: Invalid argument Thanks in advance. -- It just doesn't seem right to go over the river and through the woods to Grandmother's condo. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] I am not running 7.0, so I am just guessing, but I am assuming you changed that option in /etc/sysctl.conf (or possibly copied your /etc directory from an older machine to the 7.0 machine). That would be the why you are getting that message during boot. The reason the message is appearing at all is most likely because that is not a current sysctl variable/option. I would check the sysctl manuals for that. More likely it is just differences in the ACPI support in the BIOS. I see the same message on one of my machines running 6-STABLE. On another machine also running 6-STABLE it instead says: hw.acpi.cpu.cx_lowest: C1 - C1 Neither system has that option referenced in /etc/sysctl.conf Everything seems to work fine so I don't worry about it. -- Insert your favourite quote here. Erik Trulsson [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.2 - STABLE sysctl: hw.acpi.cpu.cx_lowest: Invalid argument
On 9/9/07, Bogdan Potishuk [EMAIL PROTECTED] wrote: George Vanev said the following on 30.08.2007 12:22: Hi, I tried to build a custom kernel, but i get the following error on boot up: hw.acpi.cpu.cx_lowest: C1 sysctl: hw.acpi.cpu.cx_lowest: Invalid argument I have updated the source tree. I tried to compile and install /usr/src/sys/i386/conf/GENERIC and /usr/src/sys/i386/conf/SMP The same error occurs. I have no problem with the precompiled SMP kernel that's initially installed. Any ideas what I did wrong? Look at http://www.freebsd.org/cgi/query-pr.cgi?pr=108581cat= -- Regards, Bogdan --- KeyID: 0x84B8D5142569D30B Fingerprint: 78FC 5C40 07CC D331 148E CC79 84B8 D514 2569 D30B Keyserver: keyserver.pgp.com --- Thanks Bogdan, I already did. It seems the problem is not solved. How can I help the ACPI team to locate the problem - post dmesg? ... or some other info? Regards, George Vanev ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.2 - STABLE sysctl: hw.acpi.cpu.cx_lowest: Invalid argument
George Vanev said the following on 30.08.2007 12:22: Hi, I tried to build a custom kernel, but i get the following error on boot up: hw.acpi.cpu.cx_lowest: C1 sysctl: hw.acpi.cpu.cx_lowest: Invalid argument I have updated the source tree. I tried to compile and install /usr/src/sys/i386/conf/GENERIC and /usr/src/sys/i386/conf/SMP The same error occurs. I have no problem with the precompiled SMP kernel that's initially installed. Any ideas what I did wrong? Look at http://www.freebsd.org/cgi/query-pr.cgi?pr=108581cat= -- Regards, Bogdan --- KeyID: 0x84B8D5142569D30B Fingerprint: 78FC 5C40 07CC D331 148E CC79 84B8 D514 2569 D30B Keyserver: keyserver.pgp.com --- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD 6.2 - STABLE sysctl: hw.acpi.cpu.cx_lowest: Invalid argument
Hi, I tried to build a custom kernel, but i get the following error on boot up: hw.acpi.cpu.cx_lowest: C1 sysctl: hw.acpi.cpu.cx_lowest: Invalid argument I have updated the source tree. I tried to compile and install /usr/src/sys/i386/conf/GENERIC and /usr/src/sys/i386/conf/SMP The same error occurs. I have no problem with the precompiled SMP kernel that's initially installed. Any ideas what I did wrong? Thanks, GeorgeVanev ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD 7.0 sysctl?
Hello, I was able to use this command in 6.x Now when I tried it it doesn't work in 7.0 sysctl kern.threads.max_groups_per_proc=4 What is the similar command in 7.0-CURRENT? I need this to tweak MySQL. -- Regards, -Abdullah Ibn Hamad Al-Marri Arab Portal http://www.WeArab.Net/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 7.0 sysctl?
Hello, I was able to use this command in 6.x Now when I tried it it doesn't work in 7.0 sysctl kern.threads.max_groups_per_proc=4 What is the similar command in 7.0-CURRENT? I need this to tweak MySQL. It has beend removed six month ago with the following notice: [remove] Any reference of the ksegrp structure. This feature was never fully utilised and made things overly complicated. I suggest further discussion on [EMAIL PROTECTED] if you think and can prove that it was really useful. Regards Björn ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 7.0 sysctl?
On Sun, May 27, 2007 at 06:37:43PM +0300, Abdullah Ibn Hamad Al-Marri wrote: Hello, I was able to use this command in 6.x Now when I tried it it doesn't work in 7.0 sysctl kern.threads.max_groups_per_proc=4 What is the similar command in 7.0-CURRENT? I need this to tweak MySQL. If it doesn't exist any longer, how do you know it is required? Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
sysctl invalid argument
Hi list, When reading through my dmesg, I found this sysctl error/message : sysctl : hw.acpi.cpu.cx_lowest : Invalid argument. Now there is no mention what so ever of that option in my /etc/sysctl.conf, so I didn't set it to C1 or anything else that seems to be invalid. So my question is : why (and where) is it set 2 times and why is it the second time with an invalid argument ? Neither the C1 nor the invalid argument seems to be doing any harm to the (good) workings of the system... System : [EMAIL PROTECTED] ~]$ uname -a FreeBSD www.brinckman.info 6.2-STABLE FreeBSD 6.2-STABLE #37: Fri Mar 30 18:41:46 CEST 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/BENI-60 i386 [EMAIL PROTECTED] ~]$ [...] pf enabled Additional routing options: . Starting devd. Configuring keyboard: . Starting ums0 moused: . hw.acpi.cpu.cx_lowest: C1 sysctl: hw.acpi.cpu.cx_lowest : Invalid argument Mounting NFS file systems: [...] Thanks, Beni. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sysctl invalid argument
Beni wrote: Hi list, When reading through my dmesg, I found this sysctl error/message : sysctl : hw.acpi.cpu.cx_lowest : Invalid argument. Now there is no mention what so ever of that option in my /etc/sysctl.conf, so I didn't set it to C1 or anything else that seems to be invalid. So my question is : why (and where) is it set 2 times and why is it the second time with an invalid argument ? Neither the C1 nor the invalid argument seems to be doing any harm to the (good) workings of the system... Check /etc/defaults/rc.conf. HTH, Kevin Kinsey -- Few things are harder to put up with than the annoyance of a good example. -- Mark Twain ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [maybe spam] Re: sysctl invalid argument
On Wednesday 11 April 2007 18:26:20 Kevin Kinsey wrote: Beni wrote: Hi list, When reading through my dmesg, I found this sysctl error/message : sysctl : hw.acpi.cpu.cx_lowest : Invalid argument. Now there is no mention what so ever of that option in my /etc/sysctl.conf, so I didn't set it to C1 or anything else that seems to be invalid. So my question is : why (and where) is it set 2 times and why is it the second time with an invalid argument ? Neither the C1 nor the invalid argument seems to be doing any harm to the (good) workings of the system... Check /etc/defaults/rc.conf. HTH, Kevin Kinsey It seems a bit more complicated than that (to me at least...). I suppose it is related to this : http://monkey.org/freebsd/archive/freebsd-stable/200512/msg00530.html Thanks for the pointer ! Beni. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
some advice on sysctl tuning
Hello all, i have a Server which does mail, and web+mysql+php. I have about 15 vhosts in Apache. Are there some neat sysctl Knobs i can turn to avoid potential Problems? Thanks a lot, David ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
very odd log entries (sysctl)
Hi all, Had a machine lock up recently. When I got into it, I found that /var/log/messages and the dmesg buffer were filled with stuff like this: Dec 1 18:17:14 h19 /kernel: 8 sendspace RW *Handler Int Dec 1 18:17:14 h19 /kernel: 9 recvspace RW *Handler Int Dec 1 18:17:14 h19 /kernel: 10 keepinit RW *Handler Int Dec 1 18:17:14 h19 /kernel: 11 pcblist R *Handler Dec 1 18:17:14 h19 /kernel: 12 delacktime RW *Handler Int Dec 1 18:17:14 h19 /kernel: 100 log_in_vain RW *Handler Int Dec 1 18:17:14 h19 /kernel: 101 blackhole RW *Handler Int Dec 1 18:17:14 h19 /kernel: 102 delayed_ack RW *Handler Int Dec 1 18:17:14 h19 /kernel: 103 insecure_rst RW *Handler Int Dec 1 18:17:14 h19 /kernel: 104 reass RW Node Dec 1 18:17:14 h19 /kernel: 100 maxsegments R *Handler Int Dec 1 18:17:15 h19 /kernel: 101 cursegments R *Handler Int Dec 1 18:17:15 h19 /kernel: 102 overflows R *Handler Int Those seem to correspond to sysctl variables. Any idea why the kernel would start spitting out sysctl mibs to the log? Thanks, Charles ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
what means: sockstat: sysctl(): No such process
hallo list while running [ $(sockstat | grep -c saslauthd) -gt 90 ] /usr/local/etc/rc.d/saslauthd restart via cron (/etc/crontab, as root) (why i do this is of no importance for this question), i get from time to time - about 3-4 times a day, cronjob runs every 11 minutes - the message: sockstat: sysctl(): No such process i do not understand why i get this only sometimes, and what this exactly means. i hope someone can help me and explain this behaviour thanks, reinhard -- What sane person could live in this world and not be crazy? -- Ursula K. LeGuin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: what means: sockstat: sysctl(): No such process
In the last episode (Sep 07), [EMAIL PROTECTED] said: hallo list while running [ $(sockstat | grep -c saslauthd) -gt 90 ] /usr/local/etc/rc.d/saslauthd restart via cron (/etc/crontab, as root) (why i do this is of no importance for this question), i get from time to time - about 3-4 times a day, cronjob runs every 11 minutes - the message: sockstat: sysctl(): No such process i do not understand why i get this only sometimes, and what this exactly means. Sockstat first gets a list of all open sockets, then looks up the command name for each one. If the process has exited before the name is looked up, you get the warning, and sockstat prints ?? as the process name. You can quiet it by redirecting stderr to /dev/null: sockstat 2/dev/null -- Dan Nelson [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: what means: sockstat: sysctl(): No such process
On Fri, 8 Sep 2006 09:18:32 -0500 Dan Nelson [EMAIL PROTECTED] wrote: In the last episode (Sep 07), [EMAIL PROTECTED] said: hallo list while running [ $(sockstat | grep -c saslauthd) -gt 90 ] /usr/local/etc/rc.d/saslauthd restart via cron (/etc/crontab, as root) (why i do this is of no importance for this question), i get from time to time - about 3-4 times a day, cronjob runs every 11 minutes - the message: sockstat: sysctl(): No such process i do not understand why i get this only sometimes, and what this exactly means. Sockstat first gets a list of all open sockets, then looks up the command name for each one. If the process has exited before the name is looked up, you get the warning, and sockstat prints ?? as the process name. You can quiet it by redirecting stderr to /dev/null: sockstat 2/dev/null thank you for explanation. i will quieten it by redirecting stderr as you suggested. ¨reinhard -- Algol-60 surely must be regarded as the most important programming language yet developed. -- T. Cheatham ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: icmp packets - disabling via sysctl, or cisco switch ... ?
On Friday 28 July 2006 06:15, User Freebsd wrote: Two part question here ... first part ... is there a way of just disabling icmp by setting a sysctl, so that a server just doesn't respond to them? No. You can do this using the firewall of your choice ipfw example ipfw add deny icmp from any to any ipfw add allow ip from any to any (not much intelligence in these rules, but this is what you asked for) keep in my mind that ipfw blocks everything by default (**you will be locked out of the box**) so do this locally or follow the instructions in the manual on how to load the ipfw kernel module. There are some things you can do with sysctls and ICMP: [EMAIL PROTECTED]:0:~# sysctl -d net.inet.icmp net.inet.icmp: ICMP net.inet.icmp.maskrepl: Reply to ICMP Address Mask Request packets. net.inet.icmp.stats: net.inet.icmp.icmplim: Maximum number of ICMP responses per second net.inet.icmp.maskfake: Fake reply to ICMP Address Mask Request packets. net.inet.icmp.drop_redirect: Ignore ICMP redirects net.inet.icmp.log_redirect: Log ICMP redirects to the console net.inet.icmp.icmplim_output: Enable rate limiting of ICMP responses net.inet.icmp.reply_src: icmp reply source for non-local packets. net.inet.icmp.reply_from_interface: ICMP reply from incoming interface for non-local packets net.inet.icmp.quotelen: Number of bytes from original packet to quote in ICMP reply net.inet.icmp.bmcastecho: ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: icmp packets - disabling via sysctl, or cisco switch ... ?
On Friday 28 July 2006 06:26, User Freebsd wrote: Just an appendum, but this is what I'm seeing in /var/log/messages right now: Jul 28 00:22:37 io kernel: Limiting icmp unreach response from 6255 to 200 packets/sec Jul 28 00:22:38 io kernel: Limiting icmp unreach response from 6515 to 200 packets/sec Jul 28 00:22:39 io kernel: Limiting icmp unreach response from 6646 to 200 packets/sec ^C And its been going on for several hours now ... :( Yes it is just FreeBSD behaving cleverly and limiting the number of ICMP replies. These two sysctls are of interest: net.inet.icmp.icmplim: Maximum number of ICMP responses per second net.inet.icmp.icmplim_output: Enable rate limiting of ICMP responses Somebody is probably flood pinging your server. You can do several things. 1) block particular (addresses|proto) from your upstream router. This way bad traffic will not reach your box. 2) block particular (addresses|proto) from your box. This way the attacker will not know if your box is up and running. Not much gain, since traffic will load your box anyway. Limit the number of ICMP replies to 5 or 10 per second. Won't help at all with your situation, but it is a good value for normal use. HTH, Nikos ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: icmp packets - disabling via sysctl, or cisco switch ... ?
User Freebsd wrote: Two part question here ... first part ... is there a way of just disabling icmp by setting a sysctl, so that a server just doesn't respond to them? second part ... is there a way of telling a cisco switch to drop all icmp packets, preferrably to all but an exception list, but to everywhere works as well ... Sure, just uninstall TCP/IP. ICMP isn't needed unless you're using TCP/IP. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: icmp packets - disabling via sysctl, or cisco switch ... ?
Bill Moran wrote: User Freebsd wrote: Two part question here ... first part ... is there a way of just disabling icmp by setting a sysctl, so that a server just doesn't respond to them? second part ... is there a way of telling a cisco switch to drop all icmp packets, preferrably to all but an exception list, but to everywhere works as well ... Sure, just uninstall TCP/IP. ICMP isn't needed unless you're using TCP/IP. :-) I was going to express the same idea a bit more politely... Try running tcpdump -nt icmp and paying attention to what is going on; blocking all ICMP traffic on an internet router will completely break PMTU discovery and cause hatred and discontent for normal TCP/IP operations, too. -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
icmp packets - disabling via sysctl, or cisco switch ... ?
Two part question here ... first part ... is there a way of just disabling icmp by setting a sysctl, so that a server just doesn't respond to them? second part ... is there a way of telling a cisco switch to drop all icmp packets, preferrably to all but an exception list, but to everywhere works as well ... I'm running a Cisco 2950-24 ... thanks ... Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . [EMAIL PROTECTED] MSN . [EMAIL PROTECTED] Yahoo . yscrappy Skype: hub.orgICQ . 7615664 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: icmp packets - disabling via sysctl, or cisco switch ... ?
Just an appendum, but this is what I'm seeing in /var/log/messages right now: Jul 28 00:22:37 io kernel: Limiting icmp unreach response from 6255 to 200 packets/sec Jul 28 00:22:38 io kernel: Limiting icmp unreach response from 6515 to 200 packets/sec Jul 28 00:22:39 io kernel: Limiting icmp unreach response from 6646 to 200 packets/sec ^C And its been going on for several hours now ... :( On Fri, 28 Jul 2006, User Freebsd wrote: Two part question here ... first part ... is there a way of just disabling icmp by setting a sysctl, so that a server just doesn't respond to them? second part ... is there a way of telling a cisco switch to drop all icmp packets, preferrably to all but an exception list, but to everywhere works as well ... I'm running a Cisco 2950-24 ... thanks ... Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . [EMAIL PROTECTED] MSN . [EMAIL PROTECTED] Yahoo . yscrappy Skype: hub.orgICQ . 7615664 Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . [EMAIL PROTECTED] MSN . [EMAIL PROTECTED] Yahoo . yscrappy Skype: hub.orgICQ . 7615664 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
is there a sysctl monitor tool ?
Hello I have 2 server . I use FreeBSD6.1 and Freebsd6.0 on them. 1 - Is there any program or command about how much the server use the parameters sysctl values and whether the server exceed the sysctl limits or not ? can you say a command or tool except top, ps, netstat -m ? 2 - While I am looking at system performance with systat command, I sometimes see values in usage of disk over %100 as below, Disks amrd0 pass0 54 ofodintrn 2002 cpu1: time KB/t 16.00 0.00 88 %slo-z 114464 buf2002 cpu3: time tps 251 0 531 tfree 274 dirtybuf MB/s 3.93 0.00 10 desiredvnodes % busy 102 0 83032 numvnodes 25001 freevnodes What cause does this condition ? 3 - On FreeBSD6.1 when I typed netstat -m I saw below values; 173/2827/3000 mbufs in use (current/cache/total) 164/1910/2074/17088 mbuf clusters in use (current/cache/total/max) 164/479 mbuf+clusters out of packet secondary zone in use (current/cache) 0/0/0/0 4k (page size) jumbo clusters in use (current/cache/total/max) 0/0/0/0 9k jumbo clusters in use (current/cache/total/max) 0/0/0/0 16k jumbo clusters in use (current/cache/total/max) 371K/4526K/4898K bytes allocated to network (current/cache/total) 105906/27714/27042 requests for mbufs denied (mbufs/clusters/mbuf+clusters) 0/0/0 requests for jumbo clusters denied (4k/9k/16k) 0/9/4528 sfbufs in use (current/peak/max) 0 requests for sfbufs denied 0 requests for sfbufs delayed 4 requests for I/O initiated by sendfile 109 calls to protocol drain routines What does 105906/27714/27042 requests for mbufs denied (mbufs/clusters/mbuf+clusters) mean ? Thanks ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
adjkerntz[]: sysctl(get_offset): No such file or directory
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I'm seeing a lot of messages like this in my Message log. adjkerntz[]: sysctl(get_offset): No such file or directory I don't think that this is a porblem as I'm not seeing any ill effects, but I'd like to know what this means and why it's happening. Google hasn't produced anything meaningful in this area. Just wondering if anyone out there knows. Machine is an AMD Dual Opteron 246 running FreeBSD 6.1 Stable i386. - -- Rod Person http://www.opensourcebeef.net http://blog.opensourcebeef.net -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFElUcObMknMq8iwDERAudgAJ0WzQBZOn78cOU1o+7NhYLV8PaxSgCfYXWe nURNYzhmIPRcUDqy2DC/OxU= =z6t5 -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: adjkerntz[]: sysctl(get_offset): No such file or directory
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sunday 18 June 2006 8:28 am, Rod Person wrote: Machine is an AMD Dual Opteron 246 running FreeBSD 6.1 Stable i386. Sorry, It's FreeBSD 7.0 Current i386 - it's a dual boot and I got confused :) - -- Rod Person http://www.opensourcebeef.net http://blog.opensourcebeef.net -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFElUv+bMknMq8iwDERAow3AKCRrmdEOdDyalviMJKnNojc8uprPgCfRz6/ YylFH80bXk/nMIykagKge5Y= =Kxzi -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: adjkerntz[]: sysctl(get_offset): No such file or directory
Sun, 18 Jun 2006 08:50:03 -0400, Rod Person wrote: On Sunday 18 June 2006 8:28 am, Rod Person wrote: Machine is an AMD Dual Opteron 246 running FreeBSD 6.1 Stable i386. Sorry, It's FreeBSD 7.0 Current i386 - it's a dual boot and I got confused :) Are you read src/UPDATING? -- Regards, Andrey. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: adjkerntz[]: sysctl(get_offset): No such file or directory
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sunday 18 June 2006 11:01 am, Andrey Slusar wrote: Sun, 18 Jun 2006 08:50:03 -0400, Rod Person wrote: On Sunday 18 June 2006 8:28 am, Rod Person wrote: Machine is an AMD Dual Opteron 246 running FreeBSD 6.1 Stable i386. Sorry, It's FreeBSD 7.0 Current i386 - it's a dual boot and I got confused :) Are you read src/UPDATING? Doing as UPDATING say gives me that error also. - -- Rod Person http://www.opensourcebeef.net http://blog.opensourcebeef.net -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFElbJRbMknMq8iwDERAtZEAJ9Qn8JgPwhYXHfYRfNNSkEAN33cZQCePife COwxPPfOhOvAU61PdJ+qjnw= =hi2E -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
net-snmpd show sysctl: physmem: Cannot allocate memory in log
I'm using net-snmpd with FreeBSD 6.0 and all is working fine but when I start it up it gives me the following error: sysctl: physmem: Cannot allocate memory snmpd seems to be running fine but why is that error showing when it's started? I looked at the sysctl and it's showing the proper amount of memory in the system hw.physmem: 2139033600 -Troy ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
adding new sysctl
Any advice on adding new sysctl to the system ? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
sysctl kern.cp_time: calculating output
Hi all, I have a question regarding the output from sysctl kern.cp_time. I know that the output is in the form of: user nice sys interrupt idle and that the numbers are incremental, but what I don't know is what these numbers and increments mean. If someone could explain this, it is greatly appreciated. Regards, Russell ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
setting sysctl net.inet6.ip6.fw.deny.unknown.extension.headers off crashes R51
Hello List, Now using FreeBSD 6.0-STABLE. If I disable net.inet6.ip6.fw.deny_unknown_exthdrs, then Thinkpad R51 crashes. Has this been fixed in HEAD? using standard ip6fw allow from any to any rules... kldstat Id Refs AddressSize Name 1 16 0xc040 462e4c kernel 21 0xc0863000 1bd9cc w22n50_sys.ko 31 0xc0a21000 590d0acpi.ko 41 0xc26f2000 3000 fdescfs.ko 51 0xc26fe000 6000 linprocfs.ko 61 0xc2751000 15000linux.ko 71 0xc28a2000 3000 snp.ko 81 0xc2b4a000 5000 ip6fw.ko Routing tables Internet6: Destination Gateway Flags Netif Expire ::1 ::1 UH lo0 fe80::%em0/64 link#1UC em0 fe80::211:25ff:fe82:95b5%em0 00:11:25:82:95:b5 UHL lo0 fe80::%lo0/64 fe80::1%lo0 U lo0 fe80::1%lo0 link#4UHL lo0 fe80::%vlan1/64 link#6UCvlan1 fe80::211:25ff:fe82:95b5%vlan100:11:25:82:95:b5 UHL lo0 fe80::%vlan2/64 link#7UCvlan2 fe80::211:25ff:fe82:95b5%vlan200:11:25:82:95:b5 UHL lo0 fe80::%vlan3/64 link#8UCvlan3 fe80::211:25ff:fe82:95b5%vlan300:11:25:82:95:b5 UHL lo0 fe80::%vlan4/64 link#9UCvlan4 fe80::211:25ff:fe82:95b5%vlan400:11:25:82:95:b5 UHL lo0 fe80::%vlan5/64 link#10 UCvlan5 fe80::211:25ff:fe82:95b5%vlan500:11:25:82:95:b5 UHL lo0 fe80::%wo0/64 link#14 UC wo0 fe80::209:5bff:fe54:82a5%wo0 00:09:5b:54:82:a5 UHL lo0 ff01:1::/32 link#1UC em0 ff01:4::/32 ::1 UC lo0 ff01:6::/32 link#6UCvlan1 ff01:7::/32 link#7UCvlan2 ff01:8::/32 link#8UCvlan3 ff01:9::/32 link#9UCvlan4 ff01:a::/32 link#10 UCvlan5 ff01:e::/32 link#14 UC wo0 ff02::%em0/32 link#1UC em0 ff02::%lo0/32 ::1 UC lo0 ff02::%vlan1/32 link#6UCvlan1 ff02::%vlan2/32 link#7UCvlan2 ff02::%vlan3/32 link#8UCvlan3 ff02::%vlan4/32 link#9UCvlan4 ff02::%vlan5/32 link#10 UCvlan5 ff02::%wo0/32 link#14 UC wo0 Routing tables Internet: DestinationGatewayFlagsRefs Use Netif Expire 104link#14UC 00wo0 127.0.0.1 127.0.0.1 UH 02lo0 wo0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 inet 104.129.0.63 netmask 0xff00 broadcast 104.255.255.255 inet6 fe80::209:5bff:fe54:82a5%wo0 prefixlen 64 scopeid 0xe ether 00:09:5b:54:82:a5 media: IEEE 802.11 Wireless Ethernet DS/11Mbps adhoc status: associated ssid olsr.freifunk.net channel 10 bssid 02:09:0b:66:82:a5 stationname foobar-e0 authmode OPEN privacy OFF txpowmax 100 bintval 100 net.wlan.debug had before set been to 1 then this causes the os to freeze: sysctl net.inet6.ip6.fw.deny_unknown_exthdrs1-0 any ideas? ip6fw show 00100407 10596 allow ipv6 from any to any 00200 0 0 allow log ipv6 from any to any 65535 43 1068 deny ipv6 from any to any greetz Wolfgang Lausenbart -- E7AC 1E9B 87D8 5BD2 E2F2 6F4A 3177 ED68 8185 480C ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
error when i change the sysctl env
freebsd6.0+ipfilter ， i use the ipfilter like a firewall proxy my lan connect to the internet , on my old computer , i use freebsd5.4 and write the follow lan to the file sysctl.conf net.inet.ipf.fr_tcpclosewait=120 net.inet.ipf.fr_tcplastack=120 net.inet.ipf.fr_tcptimeout=240 net.inet.ipf.fr_tcpclosed=60 net.inet.ipf.fr_tcphalfclosed=300 net.inet.ipf.fr_udptimeout=90 net.inet.ipf.fr_icmptimeout=35 and work fine ,but in the machine of freebsd6.0 ,when boot up ,the system tall me the device is busy ,and the sysctl env is not alive .i think write it to the file /boot/loader.conf will be ok ,but it is not work yet ,i dont know what can use that sysctl env ??? thanks ... -- == NAME ：webnamechina N U M ：9809338 [EMAIL PROTECTED] == ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
sysctl documentation
where can i find documentation for sysctl variables, mostly vfs.* ? or it it's nonexistant, where can i look for info? While FreeBSD gives best performance in every case i tested (compared to other BSD's and linux) it doesn't mean it can't be faster after some tuning. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
SV: sysctl documentation
According to the manual page of sysctl - the best place to find the documentation is the source. But chapter 11 (sounds funny ;) ) in the handbook might also help you (the tuning sections). Thomas -Ursprungligt meddelande- Från: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] För Wojciech Puchar Skickat: den 29 november 2005 15:29 Till: freebsd-questions@freebsd.org Ämne: sysctl documentation where can i find documentation for sysctl variables, mostly vfs.* ? or it it's nonexistant, where can i look for info? While FreeBSD gives best performance in every case i tested (compared to other BSD's and linux) it doesn't mean it can't be faster after some tuning. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sysctl documentation
Wojciech Puchar wrote: where can i find documentation for sysctl variables, mostly vfs.* ? or it it's nonexistant, where can i look for info? sysctl -d will help in many cases, otherwise check the manpage for the associated driver, netgraph module, etc. Or UTSL. :-) While FreeBSD gives best performance in every case i tested (compared to other BSD's and linux) it doesn't mean it can't be faster after some tuning. OK. Well, see man tuning and the Handbook for a starting place... -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
verbose sysctl messages in dmesg?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 for some reason, my dmesg output is filled with what looked sysctl options: [/usr/home/paul]:: dmesg 14 fastforwarding RW *Handler Int 15 keepfaith RW *Handler Int 100 subnets_are_local RW *Handler Int 101 fw RW Node 100 enable RW *Handler Int 101 one_pass RW *Handler Int 102 debug RW *Handler Int 103 verbose RW *Handler Int 104 verbose_limit RW *Handler Int 105 dyn_buckets RW *Handler Int 106 curr_dyn_buckets R *Handler Int 107 dyn_count R *Handler Int 108 dyn_max RW *Handler Int 109 static_count R *Handler Int 110 dyn_ack_lifetime RW *Handler Int 111 dyn_syn_lifetime RW *Handler Int 112 dyn_fin_lifetime RW *Handler Int 113 dyn_rst_lifetime RW *Handler Int 114 dyn_udp_lifetime RW *Handler Int 115 dyn_short_lifetime RW *Handler Int 116 dyn_grace_time R *Handler Int 102 maxfragpackets RW *Handler Int 103 maxfragsperpacket RW *Handler Int 104 sendsourcequench RW *Handler Int I get almost 1000 lines of this stuff, to the exclusion of anything else in dmesg. Is this something I can toggle off? This is in FreeBSD 4.11, built from sources pulled just a couple of days ago. - -- Paul Beard contact info: www.paulbeard.org/paulbeard.vcf Are you trying to win an argument or solve a problem? -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFDTd68fHLPwpj1/JQRAh8rAKCAjNn4uNgoaMSUammdhof7OynsHACgmfY0 ChPiPdkP/UW2fcHNie+ckqg= =kp0r -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sysctl or system tweak for symbolic links?
Using FreeBSD_6.0_Beta4 (applies to Beta2, also). Not related to FreeBSD versions, i think. I'm trying to track down a problem I've been having with apache-2.0.54 not following symbolic links. It's basically come down to my being able to follow the link if it's in the same directory structure (ie: .. or /path/to/..), but fails if the symbolic link is located elsewhere (ie: /usr/local/path/directory) or on another disk. It is the `normal' behaviour for Apache, AFAIK. I wonder if there's a sysctl or other system variable that handles the behavior of or access to symbolic links in this fashion that I may have missed. Seemed like a reasonable conclusion after these tests have been failing, though it could be something else, too. Don't know if it is possible (and advisable) to succeed in following an external link this way. More help/answers may be obtain from the Apache people, since it seems more an httpd configuration trick, than a FreeBSD one. -- -jpeg. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sysctl or system tweak for symbolic links?
Forrest Aldrich [EMAIL PROTECTED] writes: Using FreeBSD_6.0_Beta4 (applies to Beta2, also). I'm trying to track down a problem I've been having with apache-2.0.54 not following symbolic links. It's basically come down to my being able to follow the link if it's in the same directory structure (ie: .. or /path/to/..), but fails if the symbolic link is located elsewhere (ie: /usr/local/path/directory) or on another disk. I wonder if there's a sysctl or other system variable that handles the behavior of or access to symbolic links in this fashion that I may have missed. Seemed like a reasonable conclusion after these tests have been failing, though it could be something else, too. Seems like an Apache issue to me. Why do you think it has anything to do with the OS? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sysctl or system tweak for symbolic links?
On Fri, 9 Sep 2005, Forrest Aldrich wrote: Hi, Using FreeBSD_6.0_Beta4 (applies to Beta2, also). I'm trying to track down a problem I've been having with apache-2.0.54 not following symbolic links. It's basically come down to my being able to follow the link if it's in the same directory structure (ie: .. or /path/to/..), but fails if the symbolic link is located elsewhere (ie: /usr/local/path/directory) or on another disk. I wonder if there's a sysctl or other system variable that handles the behavior of or access to symbolic links in this fashion that I may have missed. Seemed like a reasonable conclusion after these tests have been failing, though it could be something else, too. Stock apache configuration. Look at the documentation for the Options directive, particularly SymLinksIfOwnerMatch. -- jan grant, ILRT, University of Bristol. http://www.ilrt.bris.ac.uk/ Tel +44 (0)117 3317661 http://ioctl.org/jan/ Just because I have nothing to hide doesn't mean I have nothing to fear. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sysctl or system tweak for symbolic links?
The problem was fairly hidden. It turns out that one of the directories in the PATH of the symbolic link did not have the search bits enabled (permissions). Once that was adjusted, it worked fine. This turns out to be a problem with Apache-2, since it should report a better (unambiguous) error - there is a bug report filed about it. Thanks. Julien Gabel wrote: Using FreeBSD_6.0_Beta4 (applies to Beta2, also). Not related to FreeBSD versions, i think. I'm trying to track down a problem I've been having with apache-2.0.54 not following symbolic links. It's basically come down to my being able to follow the link if it's in the same directory structure (ie: .. or /path/to/..), but fails if the symbolic link is located elsewhere (ie: /usr/local/path/directory) or on another disk. It is the `normal' behaviour for Apache, AFAIK. I wonder if there's a sysctl or other system variable that handles the behavior of or access to symbolic links in this fashion that I may have missed. Seemed like a reasonable conclusion after these tests have been failing, though it could be something else, too. Don't know if it is possible (and advisable) to succeed in following an external link this way. More help/answers may be obtain from the Apache people, since it seems more an httpd configuration trick, than a FreeBSD one. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
sysctl or system tweak for symbolic links?
Hi, Using FreeBSD_6.0_Beta4 (applies to Beta2, also). I'm trying to track down a problem I've been having with apache-2.0.54 not following symbolic links. It's basically come down to my being able to follow the link if it's in the same directory structure (ie: .. or /path/to/..), but fails if the symbolic link is located elsewhere (ie: /usr/local/path/directory) or on another disk. I wonder if there's a sysctl or other system variable that handles the behavior of or access to symbolic links in this fashion that I may have missed. Seemed like a reasonable conclusion after these tests have been failing, though it could be something else, too. Thanks. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
can not change a sysctl value
Hello, I've added: kern.randompid=1 to my /etc/sysctl.conf file, but on boot the value isn't reset it's still zero, does anyone know why i can't reset this value? The box is not operating at an increased security level. Thanks. Dave. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: can not change a sysctl value
At 11:08 AM 8/17/2005, dave wrote: Hello, I've added: kern.randompid=1 to my /etc/sysctl.conf file, but on boot the value isn't reset it's still zero, does anyone know why i can't reset this value? The box is not operating at an increased security level. It's probably read only. Try setting it in /boot/loader.conf -Glenn Thanks. Dave. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
sysctl options loader.conf or sysctl.conf
I'm a bit confused about whcih options needs to be set where. I know i.e. that hw.ata.atapi_dma=1 needs to be set in /boot/loader.conf while others are set in /etc/sysctl.conf. I need to know where I can find info on the rules about this. Now I'm dependant on what I happen to read somewhere. I read something about vfs.read_max=16 - where do I set this I wonder? Is there info about this somewhere? -- dick -- http://nagual.st/ -- PGP/GnuPG key: F86289CE ++ Running FreeBSD 4.11-stable ++ FreeBSD 5.4 + Nai tiruvantel ar vayuvantel i Valar tielyanna nu vilja ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sysctl options loader.conf or sysctl.conf
dick hoogendijk [EMAIL PROTECTED] writes: I'm a bit confused about whcih options needs to be set where. You're not alone. I know i.e. that hw.ata.atapi_dma=1 needs to be set in /boot/loader.conf while others are set in /etc/sysctl.conf. I need to know where I can find info on the rules about this. Now I'm dependant on what I happen to read somewhere. Well, sysctl(8) refers to loader.conf(5), sysctl.conf(5), loader(8), which refer to /boot/defaults/loader.conf /etc/sysctl.conf and don't forget the handboot and FAQ. I read something about vfs.read_max=16 - where do I set this I wonder? Since sysctl.conf is read in only when going multi-user and that sounds like something you'd want always, I'd put it in loader.conf. Is there info about this somewhere? Google? If you think it's needed, please write a PR (probably on /boot/default/loader.conf). ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sysctl options loader.conf or sysctl.conf
On Aug 3, 2005, at 11:21 AM, dick hoogendijk wrote: I'm a bit confused about whcih options needs to be set where. This changes over time. A lot of options once needed to be set in the loader.conf before the kernel started up, but the system is getting more flexible and some of those can be changed at runtime now I know i.e. that hw.ata.atapi_dma=1 needs to be set in /boot/loader.conf while others are set in /etc/sysctl.conf. I need to know where I can find info on the rules about this. Now I'm dependant on what I happen to read somewhere. I read something about vfs.read_max=16 - where do I set this I wonder? Is there info about this somewhere? Look at /boot/defaults/loader.conf, that ought to give you a good idea of what needs to be (or can be) set via that. Otherwise, try using sysctl to change things, and if they are marked read-only, then they needed to be changed earlier or by rebuilding the kernel with a different config. -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sysctl options loader.conf or sysctl.conf
On Wed, 03 Aug 2005 10:48:04 -0700 [EMAIL PROTECTED] (Gary W. Swearingen) wrote: Since sysctl.conf is read in only when going multi-user and that sounds like something you'd want always, I'd put it in loader.conf. Not so. I tried /boot/loader.conf but vfs.read_max still was default after the booting process. Putting it in /etc/sysctl.conf worked. Confusing.. -- dick -- http://nagual.st/ -- PGP/GnuPG key: F86289CE ++ Running FreeBSD 4.11-stable ++ FreeBSD 5.4 + Nai tiruvantel ar vayuvantel i Valar tielyanna nu vilja ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: sysctl deadmantimer
In the BSD/OS there is a kernel countdown counter that can be used to reboot the machine in case of lock. It´s called deadmantimer. I used to put a cron entry to preset this counter every 3 min, so if it goes to zero the server is rebooted. In the past it save me some times. Is there anything like this in Freebsd? Have a look at watchdogd(8). Only available under 5X and above. Norbert ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
