Dificuldades para imprimir aspas simples no awk(1)? escaping não ajuda né? Tente um escape no código de aspas simples (47):
# echo a b | \awk '{print "\47"$1"\47\t"$2}'
'a' b
Para aspas duplas use \42
Após sincronizar o Ports, para atualizar seu INDEX de aplicações se você tiver portupgrade instalado, digite:
portsdb -Uu
Se não tiver portupgrade:
cd /usr/ports/ make fetchindex
Recently I have been attending Hostobzor 12th, the Russian conference of hosting providers, beeing held at Raivola hotel near St. Petersburg. The event was great as always thanks to organizers. There was a number of intersting talks given, a lot of interesting discussions held, and, what I appreciate better, a lot of new people with great ideas met.
I gave a talk on using the FreeBSD Ports system to mange a large-scale virtual hosting installations based on Hosting Telesystems experience. I tried to describe in detail how we use the ports collection to deploy a large number of servers diverced by architecture and OS versions, how we build packages and distribute them among servers, talked about how we use Mercurial VCS to incrementally merge upstream changes into our modified ports collection and FreeBSD src trees. Hopefully, I've not screwed it much... At least, some people was interested a lot and asked interesting questions.
ip or vlan
vlan or ip
$ tcpdump -d -n -r sample.pcap ip or vlanreading from file sample.pcap, link-type EN10MB (Ethernet)(000) ldh [12](001) jeq #0x800 jt 3 jf 2(002) jeq #0x8100 jt 3 jf 4(003) ret #65535(004) ret #0
$ tcpdump -d -n -r sample.pcap vlan or ipreading from file sample.pcap, link-type EN10MB (Ethernet)(000) ldh [12](001) jeq #0x8100 jt 4 jf 2(002) ldh [16](003) jeq #0x800 jt 4 jf 5(004) ret #65535(005) ret #0
tcpdump -n -r ip.pcap \(ip and host 1.2.3.4 and port 80\) or \(vlan and host 1.2.3.4 and port 80\)
freebsd70:/usr/local/src# pkg_add -v splunk-3.4.1-45588-freebsd-6.1-intel.tgzRequested space: 106458852 bytes, free space: 1565927424 bytes in /var/tmp/instmp.HhNhQkRunning pre-install for splunk-3.4.1-45588-freebsd-6.1-intel..extract: Package name is splunk-3.4.1-45588-freebsd-6.1-intelextract: CWD to /optextract: /opt/splunk/README.txtextract: /opt/splunk/bin/btoolextract: /opt/splunk/bin/bunzip2...edited...extract: /opt/splunk/splunk-3.4.1-45588-FreeBSD-i386-manifestextract: CWD to .Running post-install for splunk-3.4.1-45588-freebsd-6.1-intel..----------------------------------------------------------------------Splunk has been installed in: /opt/splunkTo start Splunk, run the command: /opt/splunk/bin/splunk startTo use the Splunk Web interface, point your browser at: http://freebsd70.localdomain:8000Complete documentation is at http://www.splunk.com/r/docs----------------------------------------------------------------------Attempting to record package into /var/db/pkg/splunk-3.4.1-45588-freebsd-6.1-intel..Package splunk-3.4.1-45588-freebsd-6.1-intel registered in /var/db/pkg/splunk-3.4.1-45588-freebsd-6.1-intel
freebsd70:/usr/local/src# /opt/splunk/bin/splunk start/libexec/ld-elf.so.1: Shared object "libc.so.6" not found, required by "splunk"
freebsd70:/usr/local/src# pkg_add -vr ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/ packages-7.0-release/misc/compat6x-i386-6.3.602114.200711.tbzscheme: [ftp]user: []password: []host: [ftp.freebsd.org]port: [0]document: [/pub/FreeBSD/ports/i386/packages-7.0-release/misc/ compat6x-i386-6.3.602114.200711.tbz]---> ftp.freebsd.org:21looking up ftp.freebsd.orgconnecting to ftp.freebsd.org:21<<< 220 ftp.FreeBSD.org NcFTPd Server (licensed copy) ready.>>> USER anonymous<<< 331 Guest login ok, send your complete e-mail address as password.>>> PASS analyst@freebsd70.localdomain<<< 230-You are user #147 of 800 simultaneous users allowed.<<< 230-<<< 230 Logged in anonymously.>>> PWD<<< 257 "/" is cwd.>>> CWD pub/FreeBSD/ports/i386/packages-7.0-release/misc<<< 250 "/pub/FreeBSD/ports/i386/packages-7.0-release/misc" is new cwd.>>> MODE S<<< 200 Mode okay.>>> TYPE I<<< 200 Type okay.setting passive mode>>> PASV<<< 227 Entering Passive Mode (62,243,72,50,214,227)opening data connectioninitiating transfer>>> RETR compat6x-i386-6.3.602114.200711.tbz<<< 150 Data connection accepted from 24.126.62.67:61531; transfer starting for compat6x- i386-6.3.602114.200711.tbz (3164256 bytes).Fetching ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-7.0-release/misc/compat6x- i386-6.3.602114.200711.tbz...x +CONTENTSx +COMMENT...edited...extract: CWD to /usr/localextract: /usr/local/libdata/ldconfig/compat6xextract: CWD to .Running mtree for compat6x-i386-6.3.602114.200711..mtree -U -f +MTREE_DIRS -d -e -p /usr/local >/dev/nullAttempting to record package into /var/db/pkg/compat6x-i386-6.3.602114.200711..Package compat6x-i386-6.3.602114.200711 registered in /var/db/pkg/compat6x-i386-6.3.602114.200711******************************************************************************** ** Do not forget to add COMPAT_FREEBSD6 into ** your kernel configuration (enabled by default). ** ** To configure and recompile your kernel see: ** http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig.html ** ********************************************************************************
freebsd70:/usr/local/src# /opt/splunk/bin/splunk start Splunk Free Software License Agreement...edited...Do you agree with this license? [y/n]: yCopying '/opt/splunk/etc/myinstall/splunkd.xml.cfg-default' to '/opt/splunk/etc/myinstall/splunkd.xml'.Copying '/opt/splunk/etc/openldap/ldap.conf.default' to '/opt/splunk/etc/openldap/ldap.conf'.Copying '/opt/splunk/etc/modules/distributedSearch/config.xml.default' to '/opt/splunk/etc/modules/distributedSearch/config.xml'./opt/splunk/etc/auth/audit/private.pem/opt/splunk/etc/auth/audit/public.pem/opt/splunk/etc/auth/audit/private.pem generated./opt/splunk/etc/auth/audit/public.pem generated./opt/splunk/etc/auth/audit/private.pem/opt/splunk/etc/auth/audit/public.pem/opt/splunk/etc/auth/audit/private.pem generated./opt/splunk/etc/auth/audit/public.pem generated.This appears to be your first time running this version of Splunk.Validating databases... Creating /opt/splunk/var/lib/splunk/audit/thaweddb Creating /opt/splunk/var/lib/splunk/blockSignature/thaweddb Creating /opt/splunk/var/lib/splunk/_internaldb/thaweddb Creating /opt/splunk/var/lib/splunk/fishbucket/thaweddb Creating /opt/splunk/var/lib/splunk/historydb/thaweddb Creating /opt/splunk/var/lib/splunk/defaultdb/thaweddb Creating /opt/splunk/var/lib/splunk/sampledata/thaweddb Creating /opt/splunk/var/lib/splunk/splunkloggerdb/thaweddb Creating /opt/splunk/var/lib/splunk/summarydb/thaweddbValidated databases: _audit, _blocksignature, _internal, _thefishbucket, history, main, sampledata, splunklogger, summaryChecking prerequisites...Checking http port [8000]: openChecking mgmt port [8089]: openVerifying configuration. This may take a while...Finished verifying configuration.Checking index directory...Verifying databases...Verified databases: _audit, _blocksignature, _internal, _thefishbucket, history, main, sampledata, splunklogger, summaryChecking index filesAll index checks passed.All preliminary checks passed.Starting splunkd...Starting splunkweb.../opt/splunk/share/splunk/certs does not exist. Will createGenerating certs for splunkweb serverGenerating a 1024 bit RSA private key..................................++++++.............................................++++++writing new private key to 'privkeySecure.pem'-----Signature oksubject=/CN=freebsd70.localdomain/O=SplunkUserGetting CA Private Keywriting RSA keySplunk Server started. The Splunk web interface is at http://freebsd70.localdomain:8000
I'd like to add you to my network on TimeBridge. Get started by checking out my calendar: http://app.timebridge.com/user/availability/<CENSORED> - <CENSORED>
If the probability of a request failing during the n th 5-minute interval is p(n), and the number of requests issued during the n th interval is determined solely by p(n), the expected value of the Monthly Uptime Percentage is 100% minus the average value of p(n) over all the intervals; put another way, you can't cheat by waiting for a high p(n) and then quickly running up the failure count by issuing lots and lots of requests. However, this uncheatability applies only if the number of requests issued is independent of the success or failure of individual requests; if we can see whether one request succeeded before issuing the next one, we can cheat the SLA -- quite extravagently, in fact.