altman's questions

Recently, i installed FreeBSD for work and geli for encryption. (Full disk encyrption without boot partition.) When I finished getting it setup, I found that every time it boots, I need to enter the parse password to mount the root disk.

This is not for my needs. I just want my system to boot automatically, so i can ssh to it. But when others shutdown my machine, and try to use another freeBSD system to mount my disk, they can't. If they mount the partition with another FreeBSD system, they can only see /boot dir. All files are secure!

Is my concept possible? (To have an encrypted system boot automatically if mounted by another system?) And if so, how do I do it with freeBSD?

everyone! After i install syslog-ng in my freebsd9.1 and use it for my log systerm. Every time i start it there display an error:

Error opening plugin module; module='afuser', error='/usr/local/lib/syslog-ng/libafuser.so: Undefined symbol "endutent"'

And this is my config file.

  #############################################################################
  # Default syslog-ng.conf file which collects all local logs into a
  # single file called /var/log/messages.
  #
  @version: 3.4

  source s_net { 
   udp(ip(0.0.0.0) port(514));

   };

    filter firewallfilter {
     program("haproxy");

    };

   template m_template {
   template("$MSGONLY\n");
   template_escape(no);
    };

    destination d_net_secure {
         file("/weblog/haproxy/$YEAR/$MONTH.$DAY/${R_HOUR}$(/ ${R_MIN} 5).log"                                           
         template(m_template) create_dirs(yes));
        };

    log {
         source(s_net);
         filter (firewallfilter);
         destination(d_net_secure);
    };

my base systerm info:

   FreeBSD 9.1-BETA1
     syslog-ng 3.4.0alpha3
   Installer-Version: 3.4.0alpha3
    Revision: ssh+git://[email protected]//var/scm/git/syslog-ng/syslog-ng-ose--     mainline--3.4#master#709ab1252920063e6d4d0d610ad5c1ee5ebdfb75
      Compile-Date: Jul 27 2012 15:30:21
      Available-Modules: afsocket,afsocket-notls,afsocket-                         tls,afsql,affile,afprog,afmongodb,csvparser,confgen,syslogformat,basicfuncs,dbparser,tfuuid
      Enable-Debug: on
      Enable-GProf: off
      Enable-Memtrace: off
      Enable-IPv6: off
     Enable-Spoof-Source: off
      Enable-TCP-Wrapper: off
      Enable-Linux-Caps: off
      Enable-Pcre: on

I google many times but there was no answer. Does any one can tell me, What's the wrong with my syslog-ng and my freebsd.

I has a simple freebsd 9.0 machine.But everytime i start my freebsd and use command dmesg. There aren't any hardware information there but full of

         "Limiting icmp unreach response from 1293 to 200 packets/sec"

there.

Does any one there can tell me why this happen? And how can i erase this ?

I use debian for my things,but when i config speed 1000 and duplex full the error occur

the exactly command i use: ethtool -s eth0 autoneg off speed 1000 duplex full

  Cannot set new settings: Invalid argument
         not setting speed
         not setting duplex
         not setting autoneg
  Cannot set new settings: Invalid argument
         not setting speed
         not setting duplex
         not setting autoneg

And this is my eth0 information.

   Settings for eth0:
        Supported ports: [ TP ]
        Supported link modes:   10baseT/Half 10baseT/Full 
                        100baseT/Half 100baseT/Full 
                        1000baseT/Full 
     Supported pause frame use: No
     Supports auto-negotiation: Yes
     Advertised link modes:  10baseT/Half 10baseT/Full 
                        100baseT/Half 100baseT/Full 
                        1000baseT/Full 
     Advertised pause frame use: No
     Advertised auto-negotiation: Yes
     Speed: 100Mb/s
     Duplex: Full
     Port: Twisted Pair
     PHYAD: 1
     Transceiver: internal
     Auto-negotiation: on
     MDI-X: Unknown
     Supports Wake-on: g
     Wake-on: d
     Link detected: yes


      driver: bnx2
      version: 2.1.11
      firmware-version: bc 3.5.12 ipms 1.6.0
      bus-info: 0000:04:00.0
      supports-statistics: yes
      supports-test: yes
      supports-eeprom-access: yes
      supports-register-dump: yes
      supports-priv-flags: no

Could any one tell me which is the wrong place?

I just installed Windows2008 in my debian OS with kvm. And i install virtIO nic. I just wanna config virtIO nic with vlan. But after search many times. There seems no solution here. So, Is someone here can resolve my problem?

I has a debian wheezy OS. And it's a non-X environment, but we just wanna install a windowns 2008 on it.But we couldn't install a X environment on my debian. Could any one tell me howto? Thanks!

Sorry, i'm learning Squid. This is my squid key config

cache_peer 192.168.157.201 parent 3128 0 carp  no-netdb-exchange login=PASS  http11
cache_peer 192.168.157.202 parent 3128 0 carp  no-netdb-exchange login=PASS  http11
cache_peer 192.168.157.203 parent 3128 0 carp  no-netdb-exchange login=PASS  http11
cache_peer 192.168.157.207 parent 3333 0 carp  no-netdb-exchange login=PASS  http11

acl display_addr dstdomain .ip.cn
cache_peer_access 192.168.157.201 deny dispaly_addr
cache_peer_access 192.168.157.202 deny dispaly_addr
cache_peer_access 192.168.157.203 deny dispaly_addr
cache_peer_access 192.168.157.201 allow all
cache_peer_access 192.168.157.202 allow all
cache_peer_access 192.168.157.203 allow all

but when i start my squid i get this error.

FATAL: Bungled common.frontend.conf line 22: cache_peer_access 192.168.157.201 deny    dispaly_addr
Squid Cache (Version LUSCA_HEAD-r14809): Terminated abnormally.
FATAL: Bungled common.frontend.conf line 22: cache_peer_access 192.168.157.201 deny dispaly_addr
Squid Cache (Version LUSCA_HEAD-r14809): Terminated abnormally.
FATAL: Bungled common.frontend.conf line 22: cache_peer_access 192.168.157.201 deny dispaly_addr
Squid Cache (Version LUSCA_HEAD-r14809): Terminated abnormally.
FATAL: Bungled common.frontend.conf line 22: cache_peer_access 192.168.157.201 deny dispaly_addr
Squid Cache (Version LUSCA_HEAD-r14809): Terminated abnormally.

My nginx sends lots of messages to syslog, but I don't need them. In my nginx.conf:

      error_log  /var/log/nginx-error.log  notice;
        ......
      server {
      access_log  off;
      location /
      {
         .... 
        }
      }

but, in my /var/log/message you see

Nov 22 23:25:09 cache3 nginx: 2011/11/22 23:25:09 [error] 3437#0: *32172530         kevent() reported about an closed connection (60: Operation timed out) while reading response header from upstream, client: , server: , request: "GET http://www.igoido012.com//vk HTTP/1.1", upstream: "http:////vk", host: "www.igoido012.com", referrer: "http://www.baidu.com/"
Nov 22 23:25:09 cache3 nginx: 2011/11/22 23:25:09 [error] 3437#0: *32099531 upstream timed out (60: Operation timed out) while reading response header from upstream, client: , server: , request: "GET http://t.web2.qq.com/channel/poll?msg_id=0&clientid=431509&t=1321975433305 HTTP/1.1", upstream: "http://:80/channel/poll?msg_id=0&clientid=431509&t=1321975433305", host: "t.web2.qq.com", referrer: "http://t.web2.qq.com/proxy.html?v=20110331001"

How can I prevent nginx sending messages to my syslog?