Can't install freebsd/pcbsd
Hi all, I'm trying to install freebsd on a notebook for quite some time. It is an Acer Aspire 9302AWMSi with a AMD Turion 64 Mobile CPU. I tried freebsd 8.2, pcbsd 8.2 and pcbsd 9.0 . Unfortunately the installation routine gets trapped in some kind of endless loop. Version 8.2 starts up and restarts again as soon the kernel gets loaded. With version 9.0 I come to a menu and when I select any of the choices, the computer restarts again. Any advice what I could do? Or is it simply impossible to install freebsd on this kind of notebook? Cheers, Andy ___ 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: options atapicam and/or device ATA_CAM in kernel config?
On 11/27/11, Lowell Gilbert freebsd-questions-lo...@be-well.ilk.org wrote: b. f. bf1...@googlemail.com writes: What is the role of options atapicam and device ATA_CAM in kernel config file? Are they redundant? Kernel will build with both these options, but will it make things go awry? Is ATA_CAM deprecated? They are redundant and incompatible. atapicam is deprecated, and ATA_CAM is the new default on FreeBSD 9 and 10. Unless you have some special requirements, you should use ATA_CAM on recent versions of FreeBSD, because it usually performs better than the old ATA code, and has added functionality. Ah. My apologies to anyone I confused with my incorrect comments. I must say that I'm thoroughly disappointed that my searches through the official documentation didn't turn up anything related to this. Even the Handbook, with extensive practical descriptions of how to use this functionality, doesn't mention that its advice is irrelevant to anything past 8.x. The handbook does contain some oblique and scattered references to the new code, or at least to constructs that are common to both the old and the new code, but the addition of a brief discussion of the differences between the new and old ATA code in the handbook -- i.e., the kernel and userland components that are now obsolete, and their replacements -- might be of some help to users. The primary author of the new code did add some material to various notes and manpages, but he has been very busy writing and debugging code, and English is not his first language, so others will have to supplement his efforts. Perhaps you could ask for some additions on the freebsd-doc mailing list? b. Now I see it's options ATA_CAM or device atapicam. It looks like I inadvertently transposed device and options in subject line. Now I think I'll try to rebuild the kernel with options ATA_CAM and drop device atapicam. This question needs to be better resolved in time for FreeBSD 9.0-RELEASE. I cross-post this message to freebsd-curr...@freebsd.org so the developers will see it. FreeBSD users want to be able to burn CDs and DVDs, and since SCSI hardware has fallen out of style, I can say very few if any FreeBSD 9.0 users will have an actual SCSI CD or DVD drive. Tom ___ 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: options atapicam and/or device ATA_CAM in kernel config?
Now I think I'll try to rebuild the kernel with options ATA_CAM and drop device atapicam. This question needs to be better resolved in time for FreeBSD 9.0-RELEASE. I cross-post this message to freebsd-curr...@freebsd.org so the developers will see it. FreeBSD users want to be able to burn CDs and DVDs, and since SCSI hardware has fallen out of style, I can say very few if any FreeBSD 9.0 users will have an actual SCSI CD or DVD drive. The new CAM(4) is not just for SCSI devices (and SCSI, as it is usually used now, does not deal only with the old parallel SCSI devices). Despite the fact that most CD and DVD drives will now appear as cdX devices, and cd(4) is full of references to SCSI, most CD and DVD drives should be supported. And while burncd(8) will not work with the new interface, other software in ports should -- for example, sysutils/cdrtools and sysutils/cdrtools-devel, as was mentioned before. b. ___ 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: unsubscribe
On Mon, 28 Nov 2011 00:19:55 -0600
Gary Gatten articulated:
Unsubscribe
{SNIP}
Gary, assuming you want to be removed from this mailing list, I
suggest you check the headers of it's e-mail where you will find these
informative links:
List-Id: User questions freebsd-questions.freebsd.org
List-Unsubscribe:
http://lists.freebsd.org/mailman/listinfo/freebsd-questions,
mailto:freebsd-questions-requ...@freebsd.org?subject=unsubscribe
List-Archive: http://lists.freebsd.org/pipermail/freebsd-questions
List-Post: mailto:freebsd-questions@freebsd.org
List-Help: mailto:freebsd-questions-requ...@freebsd.org?subject=help
List-Subscribe: http://lists.freebsd.org/mailman/listinfo/freebsd-questions,
mailto:freebsd-questions-requ...@freebsd.org?subject=subscribe
Pick the one you think will be the most useful and use it.
--
Jerry ♔
Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the Reply-To header.
__
___
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
Alternative to syslogd that actually writes external logs to files?
Hi, I would like to know if there's a syslog alternative out there that will actually write my network equipments' logs to files. After having major issues with syslogd and attempting a thorough debug of which I posted to this mailing list and wasn't able to fix even with more experienced peoples help I am now looking for an alternative! My issue with syslogd was the fact that the logging information would be sent to my system and that could evidently be seen, however, the software didn't write to the log file specified for whatever reason :-( During debug I started syslogd using the -d and -vv options, checked the log file in question was created and had correct permission. Everything seemed fine but nothing even tried to write to file. Basically I am looking for just something that will write all my external logs to file and can keep syslogd for the system specific logs as that's no problem. Since at the time I was using FreeBSD 8.0 CURRENT x64, I upgraded to 8.2 on the basis that my system and hence ports collection was out-of-date; but unfortunately the update didn't solve my issues regarding syslog. - which is way odd considering I had FreeBSD 8.1 or 8.2 x86 edition running on an old (now packed-up) PIV which did my logging without any issues. - The current setup is the same except for the fact that am running Jails and am on a 64bit platform. Can anybody suggest anything? Thanks! ___ 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
diagnosing packetloss: x-files edition
Guys, The packet loss I asked about earlier is getting weirder and weirder. I managed to track this down to being between two specific hosts exclusively. When I run mtr from saffron to cumin I get packet loss reported on all intermediate routers. When I run mtr from cumin to saffron I get packet loss reported only on the end hop to saffron. But (and here it gets weird) when I run mtr from saffron to any other host on the Internet (although I have not tried exhaustively) I get *no* packet loss at all. So what I expect now is that this is a hardware issue with the NIC in Saffron that only affects the traffic going to cumin and not traffic to any other host. I will swap the NIC in saffron, but I just wanted to check: * can this be caused by the fact that I use fwd rules in ipfw? Both Saffron and Cumin have such rule. * Can this be caused by IP aliassing? With Saffron and cumin use two IP addresses on their NIC. * Anything else? -- Kees Jan http://java-monitor.com/ kjkos...@kjkoster.org +31651838192 I hate unit tests; I much prefer the illusion that there are no errors in my code. -- Hendrik Muller ___ 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
Dedicated Bulk Email Servers Bulk Email Hosting
Dedicated Bulk Email Servers Bulk Email Hosting Dedicated Bulk Email Servers MMS provides fully managed dedicated Linux servers configured to host mail, web and database applications. Linux hosting packages include Apache web server, mod_perl, Qmail, Clam Antivirus, SpamAssassin, and MySQL database. All plans include 24×7 monitoring, firewall security, and managed support for server hardware and software. - Send Unlimited Emails. - Multiple Dedicated IPs. (Free IP Replacement in case of blacklist) - Unlimited SMTP/POP accounts. - Deliver Fast emails to *multiple* recipients. - Your Application/Software, your SMTP. - Port 25 ISP not required. - Send your messages in both Text and HTML format. - No long term contracts. - Exceptional value! Lowest cost in the industry! How it Works? http://www.massmailservers.com/?page_id=179 Start Nowhttp://www.massmailservers.com/?page_id=179 http://dedicated-bulk-email-bulk-email-host.blogspot.com/ Bulk Email Hosting Overview:Sending bulk or high volume email presents unique challenges for businesses, ISPs and email hosting companies. To accommodate bulk email sending, MMS provides several SMTP options including shared, semi-dedicated and dedicated hosting services. - Dedicated clean IP address. - One SMTP/POP account. - Deliver emails to *multiple* recipients. - Send your messages in both Text and HTML format. - Your Application/Software, Our SMTP. - Port 25 ISP not required. - Send your messages in both Text and HTML format. - No long term contracts. - Exceptional value! Lowest cost in the industry! How it Works? http://www.massmailservers.com/?page_id=159 Start Now http://dedicated-bulk-email-bulk-email-host.blogspot.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: unsubscribe
Yup, thx everyone - I think I'm removed now just took a little longer than I
thought.
- Original Message -
From: Jerry [mailto:je...@seibercom.net]
Sent: Monday, November 28, 2011 06:53 AM
To: FreeBSD freebsd-questions@freebsd.org
Subject: Re: unsubscribe
On Mon, 28 Nov 2011 00:19:55 -0600
Gary Gatten articulated:
Unsubscribe
{SNIP}
Gary, assuming you want to be removed from this mailing list, I
suggest you check the headers of it's e-mail where you will find these
informative links:
List-Id: User questions freebsd-questions.freebsd.org
List-Unsubscribe:
http://lists.freebsd.org/mailman/listinfo/freebsd-questions,
mailto:freebsd-questions-requ...@freebsd.org?subject=unsubscribe
List-Archive: http://lists.freebsd.org/pipermail/freebsd-questions
List-Post: mailto:freebsd-questions@freebsd.org
List-Help: mailto:freebsd-questions-requ...@freebsd.org?subject=help
List-Subscribe: http://lists.freebsd.org/mailman/listinfo/freebsd-questions,
mailto:freebsd-questions-requ...@freebsd.org?subject=subscribe
Pick the one you think will be the most useful and use it.
--
Jerry ♔
Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the Reply-To header.
__
___
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
font size=1
div style='border:none;border-bottom:double windowtext 2.25pt;padding:0in 0in
1.0pt 0in'
/div
This email is intended to be reviewed by only the intended recipient
and may contain information that is privileged and/or confidential.
If you are not the intended recipient, you are hereby notified that
any review, use, dissemination, disclosure or copying of this email
and its attachments, if any, is strictly prohibited. If you have
received this email in error, please immediately notify the sender by
return email and delete this email from your system.
/font
___
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: Invalid fdisk partition table found (fwd)
On Sat, 26 Nov 2011 19:07:57 -0700 (MST) Warren Block wbl...@wonkity.com wrote: On Sat, 26 Nov 2011, Robert wrote: Some difference today. Not sure at what point this happened but one of my CF cards now reads: [robert@dell64] ~ fdisk /dev/da1 *** Working on device /dev/da1 *** parameters extracted from in-core disklabel are: cylinders=2057 heads=255 sectors/track=63 (16065 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=2057 heads=255 sectors/track=63 (16065 blks/cyl) fdisk: invalid fdisk partition table found Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 63, size 33045642 (16135 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 8/ head 254/ sector 63 The data for partition 2 is: UNUSED The data for partition 3 is: UNUSED The data for partition 4 is: UNUSED Now showing 16GB but still not right. ... I also did this in single user with the same results. Ideally, I would like to change these cards to FAT32 but I cannot get there with fdisk and am not sure how to get there with gpart or if I can. Creating an MS-DOS layout with gpart(8), where the disk is da0: # gpart destroy -F da0 da0 destroyed # gpart create -s mbr da0 da0 created # gpart add -t \!11 da0 da0s1 added Warren, Thanks for hanging in there with me. I am about ready to give up, but here is where everything stands now. [robert@dell64] ~ gpart destroy -F da1 da1 destroyed [robert@dell64] ~ sudo gpart create -s mbr da1 Password: da1 created [robert@dell64] ~ sudo gpart add -t \!11 da1 da1s1 added [robert@dell64] ~ gpart show da1 = 32 60448 da1 MBR (29M) 32 604481 fat32 (29M) [robert@dell64] ~ newfs_msdos -F32 /dev/da1s1 /dev/da1s1: 60296 sectors in 7537 FAT32 clusters (4096 bytes/cluster) BytesPerSec=512 SecPerClust=8 ResSectors=32 FATs=2 Sectors=60448 Media=0xf0 SecPerTrack=32 Heads=64 HiddenSecs=0 FATsecs=59 RootCluster=2 FSInfo=1 Backup=2 [robert@dell64] ~ sudo mount_msdosfs /dev/da1s1 /mnt mount_msdosfs: /dev/da1s1: Invalid argument [robert@dell64] ~ fdisk /dev/da1 *** Working on device /dev/da1 *** parameters extracted from in-core disklabel are: cylinders=29 heads=64 sectors/track=32 (2048 blks/cyl) parameters to be used for BIOS calculations are: cylinders=29 heads=64 sectors/track=32 (2048 blks/cyl) fdisk: invalid fdisk partition table found Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 32, size 59360 (28 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 28/ head 63/ sector 32 The data for partition 2 is: UNUSED The data for partition 3 is: UNUSED The data for partition 4 is: UNUSED [robert@dell64] ~ sudo gpart destroy da1 Password: gpart: Device busy [robert@dell64] ~ dd if=/dev/null of=/dev/da1 0+0 records in 0+0 records out 0 bytes transferred in 0.18 secs (0 bytes/sec) [robert@dell64] ~ gpart show da1 gpart: No such geom: da1. [robert@dell64] ~ Now I lost the info that I created with gpart. 11 is 0x0b, the FAT32 partition type. There might be a more mnemonic string for it, this is the first time I've ever used gpart for FAT32. The exclamation is for gpart/GPT, and the backslash is to keep the shell from messing with it. # gpart show da0 = 63 15662997 da0 MBR (7.5G) 63 156629971 fat32 (7.5G) # ls /dev/da0* /dev/da0 /dev/da0s1 # newfs_msdos -F32 /dev/da0s1 fdisk(8) may be easier, just set the partition type to 11. I haven't had any luck with the second CF card as it still show 29MB. I will try some more later today or tomorrow. What happened to make the one card show 16G? I wish I knew :-). I was doing everything that you and Julian suggested and somewhere along the line it started showing 16G. Yesterday I got it to show FAT32 (tyoe 12) along with 16G but on da1 without a s1. I then put it in a WinXP box but it did not even bring up the drive. When I put it back in the FreeBSD box it was back to 28MB. This is the card that I show above. It acts like there is some sort of write protect on sector 1 or the cards are defective. Robert ___ 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: options atapicam and/or device ATA_CAM in kernel config?
b. f. bf1...@googlemail.com writes: The handbook does contain some oblique and scattered references to the new code, or at least to constructs that are common to both the old and the new code, but the addition of a brief discussion of the differences between the new and old ATA code in the handbook -- i.e., the kernel and userland components that are now obsolete, and their replacements -- might be of some help to users. The primary author of the new code did add some material to various notes and manpages, but he has been very busy writing and debugging code, and English is not his first language, so others will have to supplement his efforts. Perhaps you could ask for some additions on the freebsd-doc mailing list? I started writing some additions as soon as I noticed the issue. They won't be sufficient, since I don't yet have a 9.x system, but they'll be a start. ___ 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: Invalid fdisk partition table found (fwd)
On Mon, 28 Nov 2011, Robert wrote: Thanks for hanging in there with me. I am about ready to give up, but here is where everything stands now. Before giving up, a few more suggestions. First, check the BIOS settings. It's possible the computer has a BIOS that protects the boot block from viruses by making it read-only. Second, sudo is not the same as being root, there are differences. So I'd also suggest trying these as root, just in case. [robert@dell64] ~ gpart destroy -F da1 da1 destroyed [robert@dell64] ~ sudo gpart create -s mbr da1 Password: da1 created [robert@dell64] ~ sudo gpart add -t \!11 da1 da1s1 added [robert@dell64] ~ gpart show da1 = 32 60448 da1 MBR (29M) 32 604481 fat32 (29M) [robert@dell64] ~ newfs_msdos -F32 /dev/da1s1 /dev/da1s1: 60296 sectors in 7537 FAT32 clusters (4096 bytes/cluster) BytesPerSec=512 SecPerClust=8 ResSectors=32 FATs=2 Sectors=60448 Media=0xf0 SecPerTrack=32 Heads=64 HiddenSecs=0 FATsecs=59 RootCluster=2 FSInfo=1 Backup=2 [robert@dell64] ~ sudo mount_msdosfs /dev/da1s1 /mnt mount_msdosfs: /dev/da1s1: Invalid argument That's odd. da1s1 went away after being formatted. Have these cards been heavily used to the point where they may be failing? If the card is failing, I'd expect there to be something in /var/log/messages. For that matter, even sysutils/smartmontools might work on these. [robert@dell64] ~ fdisk /dev/da1 Something I noticed when testing yesterday: fdisk results may not agree with gpart until the card has been reconnected. In particular fdisk showed the single FAT32 partition as the last instead of the first. *** Working on device /dev/da1 *** parameters extracted from in-core disklabel are: cylinders=29 heads=64 sectors/track=32 (2048 blks/cyl) parameters to be used for BIOS calculations are: cylinders=29 heads=64 sectors/track=32 (2048 blks/cyl) fdisk: invalid fdisk partition table found [robert@dell64] ~ sudo gpart destroy da1 Password: gpart: Device busy gpart won't destroy a GEOM unless it's unused. So either delete all the partitions first, or use 'gpart destroy -F'. Interesting that here the partition still exists, though. [robert@dell64] ~ dd if=/dev/null of=/dev/da1 0+0 records in 0+0 records out 0 bytes transferred in 0.18 secs (0 bytes/sec) This didn't write anything (0+0 records). Should be dd if=/dev/zero of=/dev/da1 bs=512 count=35 count=35 to make sure MBR/disklabel or primary GPT are wiped out. It acts like there is some sort of write protect on sector 1 This is what made me think of a BIOS virus-protect mentioned above. Hopefully that's the problem. or the cards are defective. It's worth contacting the manufacturer. Maybe they have a reset or reformat program. If you do get to the point of discarding the cards, I'd be interested in experimenting on them. ___ 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: Alternative to syslogd that actually writes external logs to files?
On Mon, Nov 28, 2011 at 6:58 AM, Kaya Saman kayasa...@gmail.com wrote: Hi, I would like to know if there's a syslog alternative out there that will actually write my network equipments' logs to files. After having major issues with syslogd and attempting a thorough debug of which I posted to this mailing list and wasn't able to fix even with more experienced peoples help I am now looking for an alternative! My issue with syslogd was the fact that the logging information would be sent to my system and that could evidently be seen, however, the software didn't write to the log file specified for whatever reason :-( During debug I started syslogd using the -d and -vv options, checked the log file in question was created and had correct permission. Everything seemed fine but nothing even tried to write to file. Basically I am looking for just something that will write all my external logs to file and can keep syslogd for the system specific logs as that's no problem. Since at the time I was using FreeBSD 8.0 CURRENT x64, I upgraded to 8.2 on the basis that my system and hence ports collection was out-of-date; but unfortunately the update didn't solve my issues regarding syslog. - which is way odd considering I had FreeBSD 8.1 or 8.2 x86 edition running on an old (now packed-up) PIV which did my logging without any issues. - The current setup is the same except for the fact that am running Jails and am on a 64bit platform. Properly configured, syslogd will log remotely. However something like sysutils/rsyslog may fit your requirements better. -- Adam Vande More ___ 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: OpenBGPd stability issue on FreebBSD 9-PRERELEASE
All RX, not a single packet arrives. 28.11.2011, 04:59, Adrian Chadd adr...@freebsd.org: Hi, Are all RX frames dropped at that point, or just the BGP TCP session related IP frames? Adrian ___ 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: Alternative to syslogd that actually writes external logs to files?
[...snip...]
Properly configured, syslogd will log remotely. However something
like sysutils/rsyslog may fit your requirements better.
--
Adam Vande More
Thanks for that. I have tested rsyslog which is backwards compatible
with syslog but again something failed with that in order to write to
the created logfile???
Here is my config just incase something hinky can be seen; although have
already posted it (with minimal responses) in a heading: Syslog server
not logging remote machines to file? {basically please don't lynch me
for double posting!!}
/etc/rc.conf
syslogd_enable=YES
syslog_flags=
syslogd_flags=-b 192.168.1.120 -a 192.168.1.1/24:* -C
#syslogd_flags=-d -b 192.168.1.120 -a 192.168.1.1/24:* -vv -C
#syslogd_flags=-c
#rsyslogd_enable=YES
#rsyslogd_pidfile=/var/run/syslog.pid
#rsyslogd_config=/etc/syslog.conf
#rsyslogd_klog_enable=YES
#rsyslogd_flags=-d
The extra addition to /etc/syslog.conf under the ppp statement
!*
+192.168.1.1
*.*/var/log/cisco857w.log
Debug from tcpdump:
# tcpdump -tlnvv -i em0 port 514
tcpdump: listening on em0, link-type EN10MB (Ethernet), capture size 96
bytes
IP (tos 0x0, ttl 255, id 337, offset 0, flags [none], proto UDP (17),
length 122)
192.168.1.1.59189 192.168.1.120.514: SYSLOG, length: 94
Facility local7 (23), Severity debug (7)
Msg: 10040: 010027: Nov 19 10:28:04.322: ISAKMP:(0): S[|syslog]
IP (tos 0x0, ttl 255, id 338, offset 0, flags [none], proto UDP (17),
length 122)
192.168.1.1.59189 192.168.1.120.514: SYSLOG, length: 94
Facility local7 (23), Severity debug (7)
Msg: 10041: 010028: Nov 19 10:28:04.326: ISAKMP:(0): S[|syslog]
IP (tos 0x0, ttl 255, id 339, offset 0, flags [none], proto UDP (17),
length 142)
192.168.1.1.59189 192.168.1.120.514: SYSLOG, length: 114
Facility local7 (23), Severity notice (5)
Msg: 10042: 010029: Nov 19 10:28:04.770: %SYS-5-CONFIG[|syslog]
IP (tos 0x0, ttl 255, id 340, offset 0, flags [none], proto UDP (17),
length 122)
192.168.1.1.59189 192.168.1.120.514: SYSLOG, length: 94
Facility local7 (23), Severity debug (7)
Msg: 10043: 010030: Nov 19 10:30:30.672: ISAKMP:(0): S[|syslog]
IP (tos 0x0, ttl 255, id 341, offset 0, flags [none], proto UDP (17),
length 122)
192.168.1.1.59189 192.168.1.120.514: SYSLOG, length: 94
Facility local7 (23), Severity debug (7)
Msg: 10044: 010031: Nov 19 10:30:30.672: ISAKMP:(0): S[|syslog]
IP (tos 0x0, ttl 255, id 342, offset 0, flags [none], proto UDP (17),
length 189)
192.168.1.1.59189 192.168.1.120.514: SYSLOG, length: 161
Facility local7 (23), Severity info (6)
Msg: 10045: 010032: Nov 19 10:30:36.455: %DOT11-6-ASSO[|syslog]
IP (tos 0x0, ttl 255, id 343, offset 0, flags [none], proto UDP (17),
length 203)
192.168.1.1.59189 192.168.1.120.514: SYSLOG, length: 175
Facility local7 (23), Severity info (6)
Msg: 10046: 010033: Nov 19 10:30:47.643: %DOT11-6-DISA[|syslog]
Debug from syslogd:
# /etc/rc.d/syslogd restart
syslogd not running? (check /var/run/syslog.pid).
Starting syslogd.
allowaddr: rule 0: numeric, addr = 192.168.1.0, mask = 255.255.255.0;
port = 0
listening on inet and/or inet6 socket
sending on inet and/or inet6 socket
off running
init
cfline(*.err;kern.warning;auth.notice;mail.crit/dev/console,
f, *, +Server.domain)
cfline(*.notice;local7.none;authpriv.none;kern.debug;lpr.info;mail.crit;news.err
/var/log/messages, f, *, +Server.domain)
cfline(security.*/var/log/security, f, *,
+Server.domain)
cfline(auth.info;authpriv.info/var/log/auth.log, f,
*, +Server.domain)
cfline(mail.info/var/log/maillog, f, *,
+Server.domain)
cfline(lpr.info/var/log/lpd-errs, f, *,
+Server.domain)
cfline(ftp.info/var/log/xferlog, f, *,
+Server.domain)
cfline(cron.*/var/log/cron, f, *,
+Server.domain)
cfline(*.=debug/var/log/debug.log, f, *,
+Server.domain)
cfline(*.emerg*, f, *, +Server.domain)
cfline(*.*/var/log/ppp.log, f, ppp,
+Server.domain)
cfline(*.*/var/log/cisco857w.log, f, *,
+192.168.1.1)
4 3 2 3 5 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 X CONSOLE: /dev/console
7 5 2 5 5 5 6 3 5 5 X 5 5 5 5 5 5 5 5 5 5 5 5 X X FILE: /var/log/messages
X X X X X X X X X X X X X 7 X X X X X X X X X X X FILE: /var/log/security
X X X X 6 X X X X X 6 X X X X X X X X X X X X X X FILE: /var/log/auth.log
X X 6 X X X X X X X X X X X X X X X X X X X X X X FILE: /var/log/maillog
X X X X X X 6 X X X X X X X X X X X X X X X X X X FILE: /var/log/lpd-errs
X X X X X X X X X X X 6 X X X X X X X X X X X X X FILE: /var/log/xferlog
X X X X X X X X X 7 X X X X X X X X X X X X X X X FILE: /var/log/cron
7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 X FILE: /var/log/debug.log
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 X WALL:
7 7 7 7 7 7 7 7 7 7 7 7 7 7 7
Re: Invalid fdisk partition table found (fwd)
On Mon, 28 Nov 2011 08:02:55 -0700 (MST) Warren Block wbl...@wonkity.com wrote: On Mon, 28 Nov 2011, Robert wrote: Thanks for hanging in there with me. I am about ready to give up, but here is where everything stands now. Before giving up, a few more suggestions. First, check the BIOS settings. It's possible the computer has a BIOS that protects the boot block from viruses by making it read-only. Second, sudo is not the same as being root, there are differences. So I'd also suggest trying these as root, just in case. I saw nothing in BIOS to suggest any protection. I am doing the testing on a Dell Precision 490. I did discover that an external card reader I was using on the Windows XP computer is defective. It had a bent pin and another recessed pin. I hope that is not what damaged these cards. Have these cards been heavily used to the point where they may be failing? I couldn't say for sure but I am waiting for answers from the photographer/owner about other questions. She does take an incredible amount of photos so I would guess they have been used and clear many times. If the card is failing, I'd expect there to be something in /var/log/messages. Nothing shows in /var/log/messages For that matter, even sysutils/smartmontools might work on these. [root@dell64] ~# smartctl /dev/da1 smartctl 5.42 2011-10-20 r3458 [FreeBSD 8.2-STABLE amd64] (local build) Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net /dev/da1: Unknown USB bridge [0x0644:0x0200 (0x400)] Smartctl: please specify device type with the -d option. [root@dell64] ~# smartctl -d scsi -a /dev/da1 smartctl 5.42 2011-10-20 r3458 [FreeBSD 8.2-STABLE amd64] (local build) Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net Vendor: TEAC Product: USB HS-CF Card Revision: 4.00 User Capacity:30,965,760 bytes [30.9 MB] Logical block size: 512 bytes Device type: disk Local Time is:Mon Nov 28 10:20:13 2011 PST Device does not support SMART Error Counter logging not supported Device does not support Self Test logging [robert@dell64] ~ fdisk /dev/da1 Something I noticed when testing yesterday: fdisk results may not agree with gpart until the card has been reconnected. In particular fdisk showed the single FAT32 partition as the last instead of the first. Interesting that here the partition still exists, though. [robert@dell64] ~ dd if=/dev/null of=/dev/da1 0+0 records in 0+0 records out 0 bytes transferred in 0.18 secs (0 bytes/sec) This didn't write anything (0+0 records). Should be dd if=/dev/zero of=/dev/da1 bs=512 count=35 I was attempting to force another look at /dev/da1 to see any change not actually zero out anything. I did a lot of my testing in single user but switched to multi so that I could more easily cut and paste tests and results. Her are the results as root: [root@dell64] ~# gpart create -s mbr da1 da1 created [root@dell64] ~# gpart add -t \!11 da1 da1s1 added [root@dell64] ~# gpart show da1 = 32 60448 da1 MBR (29M) 32 604481 fat32 (29M) [root@dell64] ~# newfs_msdos -F32 /dev/da1s1 /dev/da1s1: 60296 sectors in 7537 FAT32 clusters (4096 bytes/cluster) BytesPerSec=512 SecPerClust=8 ResSectors=32 FATs=2 Sectors=60448 Media=0xf0 SecPerTrack=32 Heads=64 HiddenSecs=0 FATsecs=59 RootCluster=2 FSInfo=1 Backup=2 At this point I removed the card and using a different external card reader placed it in the WinXP system. Windows said the card was not formatted and asked. I attempted to format but windows failed saying the card could not be formatted. I put it back in FreeBSD system and here is what I see. [root@dell64] ~# gpart show da1 = 32 60448 da1 MBR (29M) 32 604481 fat32 (29M) [root@dell64] ~# mount_msdosfs /dev/da1s1 /mnt mount_msdosfs: /dev/da1s1: Invalid argument [root@dell64] ~# gpart show da1 = 32 60448 da1 MBR (29M) 32 604481 fat32 (29M) It acts like there is some sort of write protect on sector 1 This is what made me think of a BIOS virus-protect mentioned above. Hopefully that's the problem. or the cards are defective. It's worth contacting the manufacturer. Maybe they have a reset or reformat program. If you do get to the point of discarding the cards, I'd be interested in experimenting on them. I will spend some time today or tomorrow on the manufacturer's chat. If I do give it up and it is OK with the owner I will contact you offline. Thanks for you help. Robert ___ 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: problem in changing serial console speed!
Quoth Fritz Wuehler on Monday, 28 November 2011: I don't know but I do know a real VT100 won't run at 115,200 unless you drop it out of an airplane. Are you using a physical terminal or an emulator? If an emulator you often have to match up the emulator speed and parity settings etc. to the host settings. Alas my Sun boxes only run at 9,800 over serial even though minicom itself could do alot more. Sorry for the OT reply, but this made me laugh out loud. Having been shackled to a real VT100 for years, the image of dropping one from an airplane is full of win. -- .O. | Sterling (Chip) Camden | http://camdensoftware.com ..O | sterl...@camdensoftware.com | http://chipsquips.com OOO | 2048R/D6DBAF91 | http://chipstips.com pgpyQMYpXCfIZ.pgp Description: PGP signature
Re: Alternative to syslogd that actually writes external logs to files?
On 11/28/11 7:09 PM, Kaya Saman wrote: [...snip...] Properly configured, syslogd will log remotely. However something like sysutils/rsyslog may fit your requirements better. -- Adam Vande More Thanks for that. I have tested rsyslog which is backwards compatible with syslog but again something failed with that in order to write to the created logfile??? We have absolutely no problems whatsoever with rsyslogd here. It runs on our FreeBSD firewall boxes and logs both to local files and a remote server running rsyslogd on debian. Additionally and in reply to your need to track what happens on your network, I very highly recommend Observium which we have been running for over 18 months now and which I use on an almost daily basis. http://www.observium.org/wiki/Main_Page The icing on the cake is that you'll be able to export your logs to Observium directly. ___ 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: Invalid fdisk partition table found (fwd)
On Mon, 28 Nov 2011, Robert wrote: I did discover that an external card reader I was using on the Windows XP computer is defective. It had a bent pin and another recessed pin. I hope that is not what damaged these cards. Ouch. That sounds like a logical cause. Although the card itself has sockets, and would hopefully still work in a good reader... A bad pin would explain why they show similar but not identical capacity. Have these cards been heavily used to the point where they may be failing? I couldn't say for sure but I am waiting for answers from the photographer/owner about other questions. She does take an incredible amount of photos so I would guess they have been used and clear many times. I was thinking of them being used as drive in a computer application. In that kind of use, flash drives are reported to last 1.5 to 3 years. I was attempting to force another look at /dev/da1 to see any change not actually zero out anything. Oh. A little easier: true /dev/da0 I did a lot of my testing in single user but switched to multi so that I could more easily cut and paste tests and results. Sorry, forgot to mention that earlier. It really should make no difference here. ___ 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: Can't install freebsd/pcbsd
Em Seg, 2011-11-28 às 18:53 +1030, Andreas Junius escreveu: Hi all, I'm trying to install freebsd on a notebook for quite some time. It is an Acer Aspire 9302AWMSi with a AMD Turion 64 Mobile CPU. I tried freebsd 8.2, pcbsd 8.2 and pcbsd 9.0 . Unfortunately the installation routine gets trapped in some kind of endless loop. Version 8.2 starts up and restarts again as soon the kernel gets loaded. With version 9.0 I come to a menu and when I select any of the choices, the computer restarts again. Any advice what I could do? Or is it simply impossible to install freebsd on this kind of notebook? Cheers, Andy ___ 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 Hello. I do now know about the other persons, but I swear to NEVER EVER buy an ACER product again Their bios is buggy, (does not map pci devices...), the dma is broken, the memory dumps core, and they do not care about the users I bought a Lenovo with AMD vision (very cheap and good notebook) and I it works very well. Sergio ___ 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: too many open files
On 11/27/2011 22:07, Murray Taylor wrote: I have have the same issue on a 8.0-RELEASE box and found with fstat the tgam_server was holding 12511 open files ... A what purpose does this serve (google seems to indicate that it is to speed up file access) File alteration monitoring B howinhell can I clobber it so it releases the files OR (preferably) doesn't start doing this or anything...? Create a gaminrc. I stole the template from the first google hit on gaminrc and stuck it in /usr/local/etc/gamin/gaminrc ___ 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: Can't install freebsd/pcbsd
On Mon, 28 Nov 2011, Sergio de Almeida Lenzi wrote: Em Seg, 2011-11-28 ?s 18:53 +1030, Andreas Junius escreveu: Hi all, I'm trying to install freebsd on a notebook for quite some time. It is an Acer Aspire 9302AWMSi with a AMD Turion 64 Mobile CPU. I tried freebsd 8.2, pcbsd 8.2 and pcbsd 9.0 . Unfortunately the installation routine gets trapped in some kind of endless loop. Version 8.2 starts up and restarts again as soon the kernel gets loaded. With version 9.0 I come to a menu and when I select any of the choices, the computer restarts again. Any advice what I could do? Or is it simply impossible to install freebsd on this kind of notebook? Cheers, Andy ___ 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 Hello. I do now know about the other persons, but I swear to NEVER EVER buy an ACER product again Their bios is buggy, (does not map pci devices...), the dma is broken, the memory dumps core, and they do not care about the users I bought a Lenovo with AMD vision (very cheap and good notebook) and I it works very well. Check out the compatibility list: http://laptop.bsdgroup.de/freebsd/index.html I would be very surprised if you can not install FreeBSD 8.2. Xorg is unfortunately another matter. If you can easily reinstall windows (I assume you want to dual boot) you can try to install only FreeBSD and see if that works. Windows 7 uses a different scheme that makes dual booting more of an issue than it used to be. If you google that or have access to questions archive there are instructions and/or experience on doing that. I use a Dell 17 inspiron which works fine but Xorg does not yet support the video or the wifi card (both Intel). What I did to get dual boot working does not track with most of the other experiences with windows 7. I assume that is Dell related. I forget what the exact term is, but if you use the built-in partition manager to split the disk and then make a restore disk set, you can easily get back to that configuration. I found that installing 8.x at worst takes away the MBR so that only FreeBSD will boot. Take the standard install, accept the geometry, take the default slice definitions, the minimum footprint, and no ports. That should take 10-15 mins or so. If the ethernet card is supported use csup or freebsd-update to get to the 8.2_release. I have no experience with FreeBSD 9.0 (has a new GUI install) or pcbsd. Following the above should be straight forward unless the compatibility tells you your hardware is not supported. I hope this helps, DougD ___ 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: Can't install freebsd/pcbsd
On Mon, 28 Nov 2011 15:10:10 -0500 (EST) d...@safeport.com articulated: I would be very surprised if you can not install FreeBSD 8.2. Xorg is unfortunately another matter. If you can easily reinstall windows (I assume you want to dual boot) you can try to install only FreeBSD and see if that works. Windows 7 uses a different scheme that makes dual booting more of an issue than it used to be. If you google that or have access to questions archive there are instructions and/or experience on doing that. I use a Dell 17 inspiron which works fine but Xorg does not yet support the video or the wifi card (both Intel). What I did to get dual boot working does not track with most of the other experiences with windows 7. I assume that is Dell related. I forget what the exact term is, but if you use the built-in partition manager to split the disk and then make a restore disk set, you can easily get back to that configuration. I found that installing 8.x at worst takes away the MBR so that only FreeBSD will boot. Take the standard install, accept the geometry, take the default slice definitions, the minimum footprint, and no ports. That should take 10-15 mins or so. If the ethernet card is supported use csup or freebsd-update to get to the 8.2_release. These URLs might prove useful: https://forums.freebsd.org/showthread.php?t=14222 http://apcmag.com/the_definitive_dualbooting_guide_linux_vista_and_xp_stepbystep.htm -- Jerry ♔ Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ Whoever dies with the most toys wins. ___ 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
ape-project
I've got a client wanting to use this. http://www.ape-project.org/ its not in ports, and won't build even after some gentle caressing. for reference, the easily solved issues were: bash path dep on zip, but beyond this it's still failing. Has anyone else got this working on BSD yet? Paul. -- - Paul Macdonald IFDNRG Ltd Web and video hosting - t: 0131 5548070 m: 07534206249 e: p...@ifdnrg.com w: http://www.ifdnrg.com - IFDNRG 40 Maritime Street Edinburgh EH6 6SA - ___ 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: too many open files
On 11/28/2011 19:07, Murray Taylor wrote: My /etc/gamin/gaminrc contains this fsset ufs none fsset msdosfs none (zfs and nfs too, if appropriate) and I still have 16564 files associated with gam_server in fstat out of 17424 open files reported by sysctl kern.openfiles It appears that gam_server doesn't play nice with kill -HUP ( there are 6 processes running) and also doesn't play nice with x-org/KDE as I can often get a program hang/crash as the kernel bitches about too many open files Kmail is particularly susceptible to this. What actually initiates it as there appears to be no related entry in either /etc/rc.d or /usr/local/etc/rc.d ? Currently, it is a waste of space to me, and a cause of program instability! pkg_info -R gamin\* should lead you to an ICBM coordinates suitable for nuking and ridding yourself of the thing. I had the opposite problem where I have production box on a desktop that wants to keep monitoring (we use nautilus) but gamin_server out of the box chews up a lot of processor time (the fix for this was kernel notification for my ufs and zfs) ___ 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: multimedia/vlc: no graphical interface on FreeBSD 9 and 10
2011/11/27, O. Hartmann ohart...@zedat.fu-berlin.de: Since a while, vlc on my FreeBSD 10 and FreeBSD 9 boxes do not show a graphical interface anymore. Compiling multimedia/vlc works, either with the legacy gcc or clang. But either way I compile vlc, the result is always the same: no GUI. Instead, I receive the below show message: VLC media player 1.1.12 The Luggage (revision exported) Blocked: call to unsetenv(DBUS_ACTIVATION_ADDRESS) Blocked: call to unsetenv(DBUS_ACTIVATION_BUS_TYPE) [0x802080a70] main interface error: no suitable interface module [0x8020691b0] main libvlc error: interface globalhotkeys,none initialization failed [0x8020691b0] main libvlc: Running vlc with the default interface. Use 'cvlc' to use vlc without interface. [0x802080a70] main interface error: option qt-volume-complete does not exist [0x802080a70] skins2 interface error: no suitable dialogs provider found (hint: compile the qt4 plugin, and make sure it is loaded properly) [0x802080a70] skins2 interface error: cannot instanciate qt4 dialogs provider I tried several times to recompile everything vlc depends on, but with not success. I also tried to delete every configuration file vlc created in the past and my now suffer from legzy options, but that hadn't any effect - as far as I could catch each config file. try to use pkg_add or you can install smplyer, smplayer for me is a good tool to see videos or to listen music... Is anybody out here having had the same or similar problem and solved it? Regards, Oliver -- Edguitar ;) http://cybernautape.blogspot.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: Alternative to syslogd that actually writes external logs to files?
Kaya Saman wrote:
[...snip...]
Properly configured, syslogd will log remotely. However something
like sysutils/rsyslog may fit your requirements better.
--
Adam Vande More
Thanks for that. I have tested rsyslog which is backwards compatible
with syslog but again something failed with that in order to write to
the created logfile???
Here is my config just incase something hinky can be seen; although have
already posted it (with minimal responses) in a heading: Syslog server
not logging remote machines to file? {basically please don't lynch me
for double posting!!}
/etc/rc.conf
syslogd_enable=YES
syslog_flags=
syslogd_flags=-b 192.168.1.120 -a 192.168.1.1/24:* -C
#syslogd_flags=-d -b 192.168.1.120 -a 192.168.1.1/24:* -vv -C
#syslogd_flags=-c
#rsyslogd_enable=YES
#rsyslogd_pidfile=/var/run/syslog.pid
#rsyslogd_config=/etc/syslog.conf
#rsyslogd_klog_enable=YES
#rsyslogd_flags=-d
The extra addition to /etc/syslog.conf under the ppp statement
!*
+192.168.1.1
*.*/var/log/cisco857w.log
Debug from tcpdump:
# tcpdump -tlnvv -i em0 port 514
tcpdump: listening on em0, link-type EN10MB (Ethernet), capture size 96
bytes
IP (tos 0x0, ttl 255, id 337, offset 0, flags [none], proto UDP (17),
length 122)
192.168.1.1.59189 192.168.1.120.514: SYSLOG, length: 94
Facility local7 (23), Severity debug (7)
Msg: 10040: 010027: Nov 19 10:28:04.322: ISAKMP:(0): S[|syslog]
IP (tos 0x0, ttl 255, id 338, offset 0, flags [none], proto UDP (17),
length 122)
192.168.1.1.59189 192.168.1.120.514: SYSLOG, length: 94
Facility local7 (23), Severity debug (7)
Msg: 10041: 010028: Nov 19 10:28:04.326: ISAKMP:(0): S[|syslog]
IP (tos 0x0, ttl 255, id 339, offset 0, flags [none], proto UDP (17),
length 142)
192.168.1.1.59189 192.168.1.120.514: SYSLOG, length: 114
Facility local7 (23), Severity notice (5)
Msg: 10042: 010029: Nov 19 10:28:04.770: %SYS-5-CONFIG[|syslog]
IP (tos 0x0, ttl 255, id 340, offset 0, flags [none], proto UDP (17),
length 122)
192.168.1.1.59189 192.168.1.120.514: SYSLOG, length: 94
Facility local7 (23), Severity debug (7)
Msg: 10043: 010030: Nov 19 10:30:30.672: ISAKMP:(0): S[|syslog]
IP (tos 0x0, ttl 255, id 341, offset 0, flags [none], proto UDP (17),
length 122)
192.168.1.1.59189 192.168.1.120.514: SYSLOG, length: 94
Facility local7 (23), Severity debug (7)
Msg: 10044: 010031: Nov 19 10:30:30.672: ISAKMP:(0): S[|syslog]
IP (tos 0x0, ttl 255, id 342, offset 0, flags [none], proto UDP (17),
length 189)
192.168.1.1.59189 192.168.1.120.514: SYSLOG, length: 161
Facility local7 (23), Severity info (6)
Msg: 10045: 010032: Nov 19 10:30:36.455: %DOT11-6-ASSO[|syslog]
IP (tos 0x0, ttl 255, id 343, offset 0, flags [none], proto UDP (17),
length 203)
192.168.1.1.59189 192.168.1.120.514: SYSLOG, length: 175
Facility local7 (23), Severity info (6)
Msg: 10046: 010033: Nov 19 10:30:47.643: %DOT11-6-DISA[|syslog]
Debug from syslogd:
# /etc/rc.d/syslogd restart
syslogd not running? (check /var/run/syslog.pid).
Starting syslogd.
allowaddr: rule 0: numeric, addr = 192.168.1.0, mask = 255.255.255.0;
port = 0
listening on inet and/or inet6 socket
sending on inet and/or inet6 socket
off running
init
cfline(*.err;kern.warning;auth.notice;mail.crit/dev/console,
f, *, +Server.domain)
cfline(*.notice;local7.none;authpriv.none;kern.debug;lpr.info;mail.crit;news.err
/var/log/messages, f, *, +Server.domain)
cfline(security.*/var/log/security, f, *,
+Server.domain)
cfline(auth.info;authpriv.info/var/log/auth.log, f,
*, +Server.domain)
cfline(mail.info/var/log/maillog, f, *,
+Server.domain)
cfline(lpr.info/var/log/lpd-errs, f, *,
+Server.domain)
cfline(ftp.info/var/log/xferlog, f, *,
+Server.domain)
cfline(cron.*/var/log/cron, f, *,
+Server.domain)
cfline(*.=debug/var/log/debug.log, f, *,
+Server.domain)
cfline(*.emerg*, f, *, +Server.domain)
cfline(*.*/var/log/ppp.log, f, ppp,
+Server.domain)
cfline(*.*/var/log/cisco857w.log, f, *,
+192.168.1.1)
4 3 2 3 5 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 X CONSOLE: /dev/console
7 5 2 5 5 5 6 3 5 5 X 5 5 5 5 5 5 5 5 5 5 5 5 X X FILE: /var/log/messages
X X X X X X X X X X X X X 7 X X X X X X X X X X X FILE: /var/log/security
X X X X 6 X X X X X 6 X X X X X X X X X X X X X X FILE: /var/log/auth.log
X X 6 X X X X X X X X X X X X X X X X X X X X X X FILE: /var/log/maillog
X X X X X X 6 X X X X X X X X X X X X X X X X X X FILE: /var/log/lpd-errs
X X X X X X X X X X X 6 X X X X X X X X X X X X X FILE: /var/log/xferlog
X X X X X X X X X 7 X X X X X X X X X X X X X X X FILE: /var/log/cron
7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 X FILE: /var/log/debug.log
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 X WALL:
7 7 7 7 7 7
Re: Alternative to syslogd that actually writes external logs to files?
On 11/29/2011 04:18 AM, Fbsd8 wrote:
Kaya Saman wrote:
[...snip...]
Properly configured, syslogd will log remotely. However something
like sysutils/rsyslog may fit your requirements better.
--
Adam Vande More
Thanks for that. I have tested rsyslog which is backwards compatible
with syslog but again something failed with that in order to write to
the created logfile???
Here is my config just incase something hinky can be seen; although
have already posted it (with minimal responses) in a heading: Syslog
server not logging remote machines to file? {basically please don't
lynch me for double posting!!}
/etc/rc.conf
syslogd_enable=YES
syslog_flags=
syslogd_flags=-b 192.168.1.120 -a 192.168.1.1/24:* -C
#syslogd_flags=-d -b 192.168.1.120 -a 192.168.1.1/24:* -vv -C
#syslogd_flags=-c
#rsyslogd_enable=YES
#rsyslogd_pidfile=/var/run/syslog.pid
#rsyslogd_config=/etc/syslog.conf
#rsyslogd_klog_enable=YES
#rsyslogd_flags=-d
The extra addition to /etc/syslog.conf under the ppp statement
!*
+192.168.1.1
*.*/var/log/cisco857w.log
Debug from tcpdump:
# tcpdump -tlnvv -i em0 port 514
tcpdump: listening on em0, link-type EN10MB (Ethernet), capture size
96 bytes
IP (tos 0x0, ttl 255, id 337, offset 0, flags [none], proto UDP (17),
length 122)
192.168.1.1.59189 192.168.1.120.514: SYSLOG, length: 94
Facility local7 (23), Severity debug (7)
Msg: 10040: 010027: Nov 19 10:28:04.322: ISAKMP:(0): S[|syslog]
IP (tos 0x0, ttl 255, id 338, offset 0, flags [none], proto UDP (17),
length 122)
192.168.1.1.59189 192.168.1.120.514: SYSLOG, length: 94
Facility local7 (23), Severity debug (7)
Msg: 10041: 010028: Nov 19 10:28:04.326: ISAKMP:(0): S[|syslog]
IP (tos 0x0, ttl 255, id 339, offset 0, flags [none], proto UDP (17),
length 142)
192.168.1.1.59189 192.168.1.120.514: SYSLOG, length: 114
Facility local7 (23), Severity notice (5)
Msg: 10042: 010029: Nov 19 10:28:04.770: %SYS-5-CONFIG[|syslog]
IP (tos 0x0, ttl 255, id 340, offset 0, flags [none], proto UDP (17),
length 122)
192.168.1.1.59189 192.168.1.120.514: SYSLOG, length: 94
Facility local7 (23), Severity debug (7)
Msg: 10043: 010030: Nov 19 10:30:30.672: ISAKMP:(0): S[|syslog]
IP (tos 0x0, ttl 255, id 341, offset 0, flags [none], proto UDP (17),
length 122)
192.168.1.1.59189 192.168.1.120.514: SYSLOG, length: 94
Facility local7 (23), Severity debug (7)
Msg: 10044: 010031: Nov 19 10:30:30.672: ISAKMP:(0): S[|syslog]
IP (tos 0x0, ttl 255, id 342, offset 0, flags [none], proto UDP (17),
length 189)
192.168.1.1.59189 192.168.1.120.514: SYSLOG, length: 161
Facility local7 (23), Severity info (6)
Msg: 10045: 010032: Nov 19 10:30:36.455: %DOT11-6-ASSO[|syslog]
IP (tos 0x0, ttl 255, id 343, offset 0, flags [none], proto UDP (17),
length 203)
192.168.1.1.59189 192.168.1.120.514: SYSLOG, length: 175
Facility local7 (23), Severity info (6)
Msg: 10046: 010033: Nov 19 10:30:47.643: %DOT11-6-DISA[|syslog]
Debug from syslogd:
# /etc/rc.d/syslogd restart
syslogd not running? (check /var/run/syslog.pid).
Starting syslogd.
allowaddr: rule 0: numeric, addr = 192.168.1.0, mask = 255.255.255.0;
port = 0
listening on inet and/or inet6 socket
sending on inet and/or inet6 socket
off running
init
cfline(*.err;kern.warning;auth.notice;mail.crit
/dev/console, f, *, +Server.domain)
cfline(*.notice;local7.none;authpriv.none;kern.debug;lpr.info;mail.crit;news.err
/var/log/messages, f, *, +Server.domain)
cfline(security.*/var/log/security, f, *,
+Server.domain)
cfline(auth.info;authpriv.info/var/log/auth.log, f,
*, +Server.domain)
cfline(mail.info/var/log/maillog, f, *,
+Server.domain)
cfline(lpr.info/var/log/lpd-errs, f, *,
+Server.domain)
cfline(ftp.info/var/log/xferlog, f, *,
+Server.domain)
cfline(cron.*/var/log/cron, f, *,
+Server.domain)
cfline(*.=debug/var/log/debug.log, f, *,
+Server.domain)
cfline(*.emerg*, f, *, +Server.domain)
cfline(*.*/var/log/ppp.log, f, ppp,
+Server.domain)
cfline(*.*/var/log/cisco857w.log, f, *,
+192.168.1.1)
4 3 2 3 5 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 X CONSOLE: /dev/console
7 5 2 5 5 5 6 3 5 5 X 5 5 5 5 5 5 5 5 5 5 5 5 X X FILE:
/var/log/messages
X X X X X X X X X X X X X 7 X X X X X X X X X X X FILE:
/var/log/security
X X X X 6 X X X X X 6 X X X X X X X X X X X X X X FILE:
/var/log/auth.log
X X 6 X X X X X X X X X X X X X X X X X X X X X X FILE: /var/log/maillog
X X X X X X 6 X X X X X X X X X X X X X X X X X X FILE:
/var/log/lpd-errs
X X X X X X X X X X X 6 X X X X X X X X X X X X X FILE: /var/log/xferlog
X X X X X X X X X 7 X X X X X X X X X X X X X X X FILE: /var/log/cron
7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 X FILE:
/var/log/debug.log
0 0 0 0 0 0 0 0 0 0 0
