changing cron's From: address in emails
Greetings, here's a simple question for the FreeBSD gurus out there. I have several servers running cron scripts daily for me, and they all send me e-mail with their output. Regardless of which server it is, each of these e-mails have the From: address looking exactly the same. They all say they are from the Cron Daemon. Fine, but I'd like to know more clearly which server the cron output is from. How can I change the From: address of these emails to Myserver Cron Daemon instead? I know cron runs as the user, so it's not immediately obvious to me how to change the From: field. Already the subject line says something like Cron r...@myserver ... but this doesn't stand out enough for my tired eyes. thanks, Kelly ___ 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: installation
On Fri, Oct 23, 2009 at 4:10 PM, levent basar eagleu...@hotmail.com wrote: hi freebsd is one of the good ones but its hard to install why dont you make the installation user friendly like pc bsd and also there are so many ati graphic card users can you add some new ati drives to new freebsd ? It's really not that hard to install. Of all the BSDs (including NetBSD and OpenBSD), I find it the easiest. I try various Linux installs every so often and always seem to have weird problems. I like FreeBSD because it's simple once you get the hang of it, and it's very well documented. The FreeBSD Handbook has detailed documentation on how to install the system, and it's head and shoulders above anything else out there for other systems. Once you've done an install it will get easier the second time and you can do it in a few minutes. Hang in there, it's worth the effort. ___ 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: changing cron's From: address in emails
Kelly Martin wrote: Greetings, here's a simple question for the FreeBSD gurus out there. I have several servers running cron scripts daily for me, and they all send me e-mail with their output. Regardless of which server it is, each of these e-mails have the From: address looking exactly the same. They all say they are from the Cron Daemon. Fine, but I'd like to know more clearly which server the cron output is from. How can I change the From: address of these emails to Myserver Cron Daemon instead? I know cron runs as the user, so it's not immediately obvious to me how to change the From: field. Already the subject line says something like Cron r...@myserver ... but this doesn't stand out enough for my tired eyes. Hmmm... that's actually quite tricky. There's no facility within cron(8) for changing the address it sends /from/, and as the bit you want to change is technically a comment on the From: line, and not the actual sender address (the bit in the angle brackets) all the address rewriting-fu in sendmail won't really help. Besides, r...@... is listed as a member of the 'Exposed User' class: that is, addresses that should be exempt from address rewriting, so you'ld also have to modify that. Do you control the mail server where you read your e-mail? Can you use eg. procmail(1) as a delivery agent? You should be able to match e-mails from Cron and rewrite headers, or deliver cron e-mails into per-machine mailboxes. Something like this: :0 h * From:.*Cron r...@\/[^\.]+ $MATCH The other alternative is to re-write the cron scripts to send e-mail themselves, rather than relying on cron(8) to capture their stdout/stderr and e-mail it for you. Here's a handy shell programming trick that can make that easier. Somewhere near the top of the script, you can add something like this: exec 21 | /usr/sbin/sendmail -oi -t echo From: Sender Name sen...@add.ress echo To: recipi...@some.where echo Subject: e-mail from cron job echo Then everything you print out in the script will be captured as the body of the e-mail and sent to the specified recipient. You might get some warnings about forgery in the mail headers if the userid the script runs as is not the same as the 'From:' address. Cheers, 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
RE: changing cron's From: address in emails
iH, Would this do it? server:$pwd /usr/src/usr.sbin/cron server:$grep -Ri Cron Daemon * cron/do_command.c: fprintf(mail, From: %s (Cron Daemon)\n, usernm); Recompile cron? ]Peter[ Greetings, here's a simple question for the FreeBSD gurus out there. I have several servers running cron scripts daily for me, and they all send me e-mail with their output. Regardless of which server it is, each of these e-mails have the From: address looking exactly the same. They all say they are from the Cron Daemon. Fine, but I'd like to know more clearly which server the cron output is from. How can I change the From: address of these emails to Myserver Cron Daemon instead? I know cron runs as the user, so it's not immediately obvious to me how to change the From: field. Already the subject line says something like Cron r...@myserver ... but this doesn't stand out enough for my tired eyes. thanks, Kelly ___ 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
most bizarre libc.so.7 problem
I have a machine at home that I build releng_7 on from time to time; about once a month or so. yesterday I did that, and this AM I have libc.so.7 errors all over the place. turns out libc.so.7 was not in /lib I had to boot into /rescue/sh and get my zfs stuff mounted and do a quick cp from /usr/obj/usr/src/lib/libc/libc.so.7 to /lib/libc.so.7 then everything was fine.. do I'm doing a buildworld again while I'm here and see if something failed on my part.. I've been doing this for a while and never had this problem.. below is what I do.. cat -n /root/build-world 1 #!/bin/sh 2 cd /usr/src 3 make update 4 #chflags -R noschg /usr/obj/* 5 rm -rf /usr/obj/* 6 mkdir /var/log/build 7 make -j4 buildworld 21 | tee /var/log/build/bworld-`date +%Y%m%d-%H%M`.log \ 8 make -j4 buildkernel 21 | tee /var/log/build/bkernel-`date +%Y%m%d-%H%M`.log \ 9 make installkernel 21 | tee /var/log/build/ikernel-`date +%Y%m%d-%H%M`.log \ 10 make installworld 21 | tee /var/log/build/iworld-`date +%Y%m%d-%H%M`.log \ 11 date | mail -s `hostname -s` n...@domain.com 12 sync \ 13 reboot Not sure if something changed, or if something happened.. thanks in advance ___ 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: most bizarre libc.so.7 problem
B. Cook wrote, On 10/24/2009 7:43 AM: I have a machine at home that I build releng_7 on from time to time; about once a month or so. yesterday I did that, and this AM I have libc.so.7 errors all over the place. turns out libc.so.7 was not in /lib I had to boot into /rescue/sh and get my zfs stuff mounted and do a quick cp from /usr/obj/usr/src/lib/libc/libc.so.7 to /lib/libc.so.7 then everything was fine.. do I'm doing a buildworld again while I'm here and see if something failed on my part.. I've been doing this for a while and never had this problem.. below is what I do.. cat -n /root/build-world 1 #!/bin/sh 2 cd /usr/src 3 make update 4 #chflags -R noschg /usr/obj/* 5 rm -rf /usr/obj/* 6 mkdir /var/log/build 7 make -j4 buildworld 21 | tee /var/log/build/bworld-`date +%Y%m%d-%H%M`.log \ 8 make -j4 buildkernel 21 | tee /var/log/build/bkernel-`date +%Y%m%d-%H%M`.log \ 9 make installkernel 21 | tee /var/log/build/ikernel-`date +%Y%m%d-%H%M`.log \ 10 make installworld 21 | tee /var/log/build/iworld-`date +%Y%m%d-%H%M`.log \ 11 date | mail -s `hostname -s` n...@domain.com 12 sync \ 13 reboot Not sure if something changed, or if something happened.. thanks in advance ___ 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 So installworld is what is failing.. below are the relevant portions of the log that shows whats going on.. here is the output of the iworld log.. cat -n iworld-20091023-0710.log 1 mkdir -p /tmp/install.ljWDSoNZ 2 for prog in [ awk cap_mkdb cat chflags chmod chown date echo egrep find grep install-info ln lockf make mkdir mtree mv pwd_mkdb rm sed sh sysctl test true uname wc zic; do cp `which $prog` /tmp/install.ljWDSoNZ; done 3 cd /usr/src; MAKEOBJDIRPREFIX=/usr/obj MACHINE_ARCH=amd64 MACHINE=amd64 CPUTYPE= GROFF_BIN_PATH=/usr/obj/usr/src/tmp/legacy/usr/bin GROFF_FONT_PATH=/usr/obj/usr/src/tmp/legacy/usr/share/groff_font GROFF_TMAC_PATH=/usr/obj/usr/src/tmp/legacy/usr/share/tmac PATH=/usr/obj/usr/src/tmp/legacy/usr/sbin:/usr/obj/usr/src/tmp/legacy/usr/bin:/usr/obj/usr/src/tmp/legacy/usr/games:/usr/obj/usr/src/tmp/usr/sbin:/usr/obj/usr/src/tmp/usr/bin:/usr/obj/usr/src/tmp/usr/games:/tmp/install.ljWDSoNZ make -f Makefile.inc1 reinstall 4 -- 5 Making hierarchy 6 -- 7 cd /usr/src; make -f Makefile.inc1 hierarchy 8 cd /usr/src/etc;make distrib-dirs 9 mtree -eU -f /usr/src/etc/mtree/BSD.root.dist -p / 10 boot changed 11 type expected dir found link 12 ./boot/defaults missing (directory not created: File exists) 13 ./boot/firmware missing (directory not created: File exists) 14 ./boot/kernel missing (directory not created: File exists) 15 ./boot/modules missing (directory not created: File exists) 16 ./boot/zfs missing (directory not created: File exists) 17 mtree -eU -f /usr/src/etc/mtree/BSD.var.dist -p /var 18 empty changed 19 flags expected schg found none not modified: Invalid argument 20 mtree -eU -f /usr/src/etc/mtree/BSD.usr.dist -p /usr 21 ./share/locale/ca_AD.ISO8859-1 missing (created) 22 ./share/locale/ca_FR.ISO8859-1 missing (created) 23 ./share/locale/ca_IT.ISO8859-1 missing (created) 24 ./share/locale/ca_AD.ISO8859-15 missing (created) 25 ./share/locale/ca_FR.ISO8859-15 missing (created) 26 ./share/locale/ca_IT.ISO8859-15 missing (created) 27 ./share/locale/ca_AD.UTF-8 missing (created) 28 ./share/locale/ca_FR.UTF-8 missing (created) 29 ./share/locale/ca_IT.UTF-8 missing (created) 30 mtree -eU -f /usr/src/etc/mtree/BSD.include.dist -p /usr/include 31 mtree -deU -f /usr/src/etc/mtree/BIND.chroot.dist -p /var/named 32 mtree -deU -f /usr/src/etc/mtree/BSD.sendmail.dist -p / 33 cd /; rm -f /sys; ln -s usr/src/sys sys 34 cd /usr/share/man/en.ISO8859-1; ln -sf ../man* . 35 cd /usr/share/man/en.UTF-8; ln -sf ../man* . 36 cd /usr/share/man; set - `grep ^[a-zA-Z] /usr/src/etc/man.alias`; while [ $# -gt 0 ] ; do rm -rf $1; ln -s $2 $1; shift; shift; done 37 cd /usr/share/openssl/man; set - `grep ^[a-zA-Z] /usr/src/etc/man.alias`; while [ $# -gt 0 ] ; do rm -rf $1; ln -s $2 $1; shift; shift; done 38 cd /usr/share/openssl/man/en.ISO8859-1; ln -sf ../man* . 39 cd /usr/share/nls; set - `grep ^[a-zA-Z] /usr/src/etc/nls.alias`; while [ $# -gt 0 ] ; do rm -rf $1; ln -s $2 $1; shift; shift; done 40 41 -- 42 Installing everything
Re: changing cron's From: address in emails
--On Saturday, October 24, 2009 4:16 AM -0500 Matthew Seaman m.sea...@infracaninophile.co.uk wrote: Kelly Martin wrote: Greetings, here's a simple question for the FreeBSD gurus out there. I have several servers running cron scripts daily for me, and they all send me e-mail with their output. Regardless of which server it is, each of these e-mails have the From: address looking exactly the same. They all say they are from the Cron Daemon. Fine, but I'd like to know more clearly which server the cron output is from. How can I change the From: address of these emails to Myserver Cron Daemon instead? I know cron runs as the user, so it's not immediately obvious to me how to change the From: field. Already the subject line says something like Cron r...@myserver ... but this doesn't stand out enough for my tired eyes. Hmmm... that's actually quite tricky. There's no facility within cron(8) for changing the address it sends /from/, and as the bit you want to change is technically a comment on the From: line, and not the actual sender address (the bit in the angle brackets) all the address rewriting-fu in sendmail won't really help. Besides, r...@... is listed as a member of the 'Exposed User' class: that is, addresses that should be exempt from address rewriting, so you'ld also have to modify that. Do you control the mail server where you read your e-mail? Can you use eg. procmail(1) as a delivery agent? You should be able to match e-mails from Cron and rewrite headers, or deliver cron e-mails into per-machine mailboxes. Something like this: :0 h * From:.*Cron r...@\/[^\.]+ $MATCH The other alternative is to re-write the cron scripts to send e-mail themselves, rather than relying on cron(8) to capture their stdout/stderr and e-mail it for you. Here's a handy shell programming trick that can make that easier. Somewhere near the top of the script, you can add something like this: exec 21 | /usr/sbin/sendmail -oi -t echo From: Sender Name sen...@add.ress echo To: recipi...@some.where echo Subject: e-mail from cron job echo Then everything you print out in the script will be captured as the body of the e-mail and sent to the specified recipient. You might get some warnings about forgery in the mail headers if the userid the script runs as is not the same as the 'From:' address. Why not just echo `hostname` as the first line of every script? Isn't that what he really wants to know? Or echo This script came from `hostname`? Paul Schmehl As if it wasn't already obvious, my opinions are my own and not those of my employer. ___ 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
Anybody is using VirtualBox?
I am tryingto run Windows under FreeBSD. When I run: cat /dev/ad1s1 | VBoxManage stdin OutPutFile.vdi 21474836480 on 80-RC2 I get this output: ERROR: failed to create the VirtualBox object! ERROR: code NS_ERROR_ABORT (0x80004004) - Operation aborted (extended info not available) Most likely, the VirtualBox COM server is not running or failed to start. No processes with name VirtualBox are running. What could be the problem? Yuri ___ 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: Anybody is using VirtualBox?
On Sat, 24 Oct 2009 09:23:10 -0700 Yuri y...@rawbw.com wrote: I am tryingto run Windows under FreeBSD. When I run: cat /dev/ad1s1 | VBoxManage stdin OutPutFile.vdi 21474836480 on 80-RC2 I get this output: ERROR: failed to create the VirtualBox object! ERROR: code NS_ERROR_ABORT (0x80004004) - Operation aborted (extended info not available) Most likely, the VirtualBox COM server is not running or failed to start. No processes with name VirtualBox are running. What could be the problem? Yuri compiled virtual box this morning with additions to run winblows 2003 server. So far it is working better than the xp version which is good as it is one less reason to have to put in the xp harddrive Are you trying to run more than one image copied from the same file? if so use vboxmanage internalcommands sethduuid to change the id of the second image file as renaming does not do that, and you get an error if you try to run it. ___ 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: changing cron's From: address in emails
Paul Schmehl wrote: --On Saturday, October 24, 2009 4:16 AM -0500 Matthew Seaman m.sea...@infracaninophile.co.uk wrote: Kelly Martin wrote: Greetings, here's a simple question for the FreeBSD gurus out there. I have several servers running cron scripts daily for me, and they all send me e-mail with their output. Regardless of which server it is, each of these e-mails have the From: address looking exactly the same. They all say they are from the Cron Daemon. Fine, but I'd like to know more clearly which server the cron output is from. How can I change the From: address of these emails to Myserver Cron Daemon instead? I know cron runs as the user, so it's not immediately obvious to me how to change the From: field. Already the subject line says something like Cron r...@myserver ... but this doesn't stand out enough for my tired eyes. Hmmm... that's actually quite tricky. There's no facility within cron(8) for changing the address it sends /from/, and as the bit you want to change is technically a comment on the From: line, and not the actual sender address (the bit in the angle brackets) all the address rewriting-fu in sendmail won't really help. Besides, r...@... is listed as a member of the 'Exposed User' class: that is, addresses that should be exempt from address rewriting, so you'ld also have to modify that. Do you control the mail server where you read your e-mail? Can you use eg. procmail(1) as a delivery agent? You should be able to match e-mails from Cron and rewrite headers, or deliver cron e-mails into per-machine mailboxes. Something like this: :0 h * From:.*Cron r...@\/[^\.]+ $MATCH The other alternative is to re-write the cron scripts to send e-mail themselves, rather than relying on cron(8) to capture their stdout/stderr and e-mail it for you. Here's a handy shell programming trick that can make that easier. Somewhere near the top of the script, you can add something like this: exec 21 | /usr/sbin/sendmail -oi -t echo From: Sender Name sen...@add.ress echo To: recipi...@some.where echo Subject: e-mail from cron job echo Then everything you print out in the script will be captured as the body of the e-mail and sent to the specified recipient. You might get some warnings about forgery in the mail headers if the userid the script runs as is not the same as the 'From:' address. Why not just echo `hostname` as the first line of every script? Isn't that what he really wants to know? Or echo This script came from `hostname`? There is that, but I had assumed the idea was to be able to better distinguish the different e-mails /before/ opening them up in the MUA. Cheers, 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
Re: changing cron's From: address in emails
Paul Schmehl wrote: --On Saturday, October 24, 2009 4:16 AM -0500 Matthew Seaman m.sea...@infracaninophile.co.uk wrote: Kelly Martin wrote: How can I change the From: address of these emails to Myserver Cron Daemon instead? I know cron runs as the user, so it's not immediately obvious to me how to change the From: field. Already the subject line says something like Cron r...@myserver ... but this doesn't stand out enough for my tired eyes. Do you control the mail server where you read your e-mail? Can you use eg. procmail(1) as a delivery agent? You should be able to match e-mails from Cron and rewrite headers, or deliver cron e-mails into per-machine mailboxes. Something like this: :0 h * From:.*Cron r...@\/[^\.]+ $MATCH The other alternative is to re-write the cron scripts to send e-mail themselves, rather than relying on cron(8) to capture their stdout/stderr and e-mail it for you. Here's a handy shell programming trick that can make that easier. Somewhere near the top of the script, you can add something like this: exec 21 | /usr/sbin/sendmail -oi -t echo From: Sender Name sen...@add.ress echo To: recipi...@some.where echo Subject: e-mail from cron job echo Then everything you print out in the script will be captured as the body of the e-mail and sent to the specified recipient. You might get some warnings about forgery in the mail headers if the userid the script runs as is not the same as the 'From:' address. Why not just echo `hostname` as the first line of every script? Isn't that what he really wants to know? Or echo This script came from `hostname`? Or, on a related note, why have cron(8) do any mailing at all? Most/all of my management scripts compile a mail message in /tmp and then send it as the body of a message with mail(1), so I can have whatever subject header I want, and the envelope data comes from the user (usually m...@myhost.tld). Cron sees nothing because stdout/err is redirected to dev/null. Kevin Kinsey ___ 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: freebsd forgets root password
kalin m wrote: does anybody here know if freebsd has a driver for Marvell 88E8057 nic chip? according to the kernel list of drivers (7.2) marvell chips are driven by the msk driver. but it doesn't show up in pciconf, dmesg or sysinstall strangely enough 88E8057 is not in the list in man msk. although 88E8056 and 88E8058 are. is this just bad luck?! No, as I mentioned earlier, it appears the driver author didn't have or wasn't aware of this chipset. It's quite possible, based on the cursory glance I gave to the headers of the file, that it didn't exist at the time it was written. There are obviously some issues with licensing or disclosure or what-not. See /usr/src/dev/msk/if_msk.c, down about line 210-220 where these are defined. You can, I think, very carefully, attempt to add this device to that file and rebuild your kernel, I think, and then see if it works. I'm thinking OOTOMH the trick would be getting the right DEVICEID string in there. Barring that, you might speak very sweetly to the author of the driver, perhaps offering $BEVERAGE and detailed information about the chip, and see if he/she would attempt to conjure up the right code to make it work. HTH, Kevin Kinsey ___ 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: Anybody is using VirtualBox?
Hi, On Sat, Oct 24, 2009 at 12:23 PM, Yuri y...@rawbw.com wrote: I am tryingto run Windows under FreeBSD. When I run: cat /dev/ad1s1 | VBoxManage stdin OutPutFile.vdi 21474836480 on 80-RC2 I get this output: ERROR: failed to create the VirtualBox object! ERROR: code NS_ERROR_ABORT (0x80004004) - Operation aborted (extended info not available) Most likely, the VirtualBox COM server is not running or failed to start. No processes with name VirtualBox are running. What could be the problem? Do you have the vboxdrv.ko module loaded? -- Glen Barber ___ 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
Using 'USR1' signal in newsyslog.conf file causes error
Dovecot has a site with information regarding how to rotate it's log-file. http://wiki.dovecot.org/Logging Since I do not have logrotate on my FreeBSD-7.2 system, I thought I could use newsyslog to accomplish the action. I seem to have run into a problem however. newsyslog: illegal signal number in config file: /var/log/dovecot.log root:wheel 0666 1 * $M1D0 CJ /var/run/dovecot/master.pid SIGUSR1 I then changed SIGUSR1 TO USR1'; however, the problem continues. Can someone tell me what I am doing wrong? -- Carmel carmel...@hotmail.com |=== |=== |=== |=== | Seattle is so wet that people protect their property with watch-ducks. ___ 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: Using 'USR1' signal in newsyslog.conf file causes error
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sat, 24 Oct 2009 15:26-0400, carmel_ny wrote: Dovecot has a site with information regarding how to rotate it's log-file. http://wiki.dovecot.org/Logging Since I do not have logrotate on my FreeBSD-7.2 system, I thought I could use newsyslog to accomplish the action. I seem to have run into a problem however. newsyslog: illegal signal number in config file: /var/log/dovecot.log root:wheel 0666 1 * $M1D0 CJ /var/run/dovecot/master.pid SIGUSR1 I then changed SIGUSR1 TO USR1'; however, the problem continues. Can someone tell me what I am doing wrong? You're supposed to use a number. Look in /usr/include/sys/signal.h, you'll find SIGUSR1 listed as signal no. 30. Use 30 as opposed to SIGUSR or USR1. Trond. - -- - -- Trond Endrestøl | trond.endres...@fagskolen.gjovik.no ACM, NAS, NUUG, SAGE, USENIX |FreeBSD 7.2-STABLE Alpine 2.00 -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.12 (FreeBSD) iEYEARECAAYFAkrjVrUACgkQbYWZalUoEltaBwCdEs6UdDe7ZF+YwrcHhC7MWsIL yY0An10HF2z4TeQIdoTyt15P3hPM2ITl =CNF+ -END PGP SIGNATURE-___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Using 'USR1' signal in newsyslog.conf file causes error
On Sat, 24 Oct 2009 21:34:08 +0200 (CEST) Trond Endrestøl trond.endres...@fagskolen.gjovik.no replied: On Sat, 24 Oct 2009 15:26-0400, carmel_ny wrote: Dovecot has a site with information regarding how to rotate it's log-file. http://wiki.dovecot.org/Logging Since I do not have logrotate on my FreeBSD-7.2 system, I thought I could use newsyslog to accomplish the action. I seem to have run into a problem however. newsyslog: illegal signal number in config file: /var/log/dovecot.log root:wheel 0666 1 * $M1D0 CJ /var/run/dovecot/master.pid SIGUSR1 I then changed SIGUSR1 TO USR1'; however, the problem continues. Can someone tell me what I am doing wrong? You're supposed to use a number. Look in /usr/include/sys/signal.h, you'll find SIGUSR1 listed as signal no. 30. Use 30 as opposed to SIGUSR or USR1. Trond I did a 'kill -l' right after I posted that message. I discovered the numerical equivalency then. -- Carmel carmel...@hotmail.com |=== |=== |=== |=== | Fantasies are free. NO!! NO!! It's the thought police ___ 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 8rc1 Puc driver
Hi all I have a multi-serial card with an Oxford OX16PCI954 on it. Whatever I do, the oxford chip is not recognized. in dmesg: pci0: simple comms, UART at device 12.0 (no driver attached) and in pciconf -lv : no...@pci0:0:12:0: class=0x070006 card=0x chip=0x950c1415 rev=0x00 hdr=0x00 vendor = 'Oxford Semiconductor Ltd' class = simple comms subclass = UART no...@pci0:0:12:1: class=0x068000 card=0x chip=0x95101415 rev=0x00 hdr=0x00 vendor = 'Oxford Semiconductor Ltd' device = 'PCI Interface (disabled) (OX16PCI954)' class = bridge Can somebody tell me why the second PCI interface is flagged disabled ? How can I solve this ? (I have loaded puc from loader.conf, without more success). T.I.A. PM. PS: (un)works the same way with freebsd 7.2 8.0rc1 ___ 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: Anybody is using VirtualBox?
On Sat, 24 Oct 2009 09:23:10 -0700 Yuri y...@rawbw.com wrote: I am tryingto run Windows under FreeBSD. When I run: cat /dev/ad1s1 | VBoxManage stdin OutPutFile.vdi 21474836480 on 80-RC2 I get this output: ERROR: failed to create the VirtualBox object! ERROR: code NS_ERROR_ABORT (0x80004004) - Operation aborted (extended info not available) Most likely, the VirtualBox COM server is not running or failed to start. No processes with name VirtualBox are running. What could be the problem? Yuri ___ 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 I have VirtualBox 3.0.51_OSE rr22900 successfully running on 7.2 , after i installed it from Ports i got a Kernel Panic after loading vboxdrv. So i put all necessary modules in loader.conf and now everything works really great with a Virtual WinXP installation. loader.conf vboxdrv_load=YES vbnetadp_load=YES vboxnetflt_load=YES Cheers Daniel -- Just because I don`t care - Doesn`t mean I don`t understand ! -- Homer J. Simpson ___ 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: Freebsd 8rc1 Puc driver
On Sat, 24 Oct 2009 22:04:56 +0200, P. Moulin spamarch...@calyopea.com wrote: and in pciconf -lv : vendor = 'Oxford Semiconductor Ltd' device = 'PCI Interface (disabled) (OX16PCI954)' class = bridge Can somebody tell me why the second PCI interface is flagged disabled ? How can I solve this ? I think the strings you see are identification strings obtained either from the device itself, or from a file (of FreeBSD) that transforms vendor/device 0x information into character strings. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: freebsd forgets root password
Kevin Kinsey wrote: kalin m wrote: does anybody here know if freebsd has a driver for Marvell 88E8057 nic chip? according to the kernel list of drivers (7.2) marvell chips are driven by the msk driver. but it doesn't show up in pciconf, dmesg or sysinstall strangely enough 88E8057 is not in the list in man msk. although 88E8056 and 88E8058 are. is this just bad luck?! No, as I mentioned earlier, it appears the driver author didn't have or wasn't aware of this chipset. It's quite possible, based on the cursory glance I gave to the headers of the file, that it didn't exist at the time it was written. There are obviously some issues with licensing or disclosure or what-not. See /usr/src/dev/msk/if_msk.c, down about line 210-220 where these are defined. You can, I think, very carefully, attempt to add this device to that file and rebuild your kernel, I think, and then see if it works. I'm thinking OOTOMH the trick would be getting the right DEVICEID string in there. Barring that, you might speak very sweetly to the author of the driver, perhaps offering $BEVERAGE and detailed information about the chip, and see if he/she would attempt to conjure up the right code to make it work. thanks kevin... i did get an email from (i believe ) the author of the driver. so i'll be hopefully trying his patch on monday. and i have to get some files from HEAD. but it was very nice that he contacted me. i had to look up OOTOMH thought... thanks... HTH, Kevin Kinsey ___ 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
flashplugin
Is there any definitive install guide for flashplugin. I was able to install it on a 7.2 64bit machine and then on an i386 but somehow it has morphed into god-knows-what and no longer works. I thought I had installed it with linux-f8 emulations but I found the linux-f4 on the machine... so I don't know what is going on. Now, trying to reinstall under linux-f8 and flashplugin9 does not work... Adobe seems to be toally unreliable as to what they are doing with their software; at least from what I can see about the problems users are having with their products. So, the question - what is the latest method to get the flashplugin to work - what linux emulation, whick version of flashplugin... stumble, bumble and mumble ... ___ 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: flashplugin
Howdy, On Sat, Oct 24, 2009 at 7:56 PM, PJ af.gour...@videotron.ca wrote: Is there any definitive install guide for flashplugin. I was able to install it on a 7.2 64bit machine and then on an i386 but somehow it has morphed into god-knows-what and no longer works. Any errors? I thought I had installed it with linux-f8 emulations but I found the linux-f4 on the machine... so I don't know what is going on. Now, trying to reinstall under linux-f8 and flashplugin9 does not work... I used the steps in the handbook[1] to get flash on my FreeBSD 8 machines. I never used flash on 7 because it wasn't worth the trouble. Things have changed since. Adobe seems to be toally unreliable as to what they are doing with their software; at least from what I can see about the problems users are having with their products. Any major software vendor fits in this category, IMHO. Not everything works for everyone. Computer configurations, hardware, OS, etc differ from person to person, company to company. So, the question - what is the latest method to get the flashplugin to work - what linux emulation, whick version of flashplugin... stumble, bumble and mumble ... [1] - http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/desktop-browsers.html#MOZ-FLASH-PLUGIN HTH. -- Glen Barber ___ 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: flashplugin
Glen Barber wrote: Howdy, On Sat, Oct 24, 2009 at 7:56 PM, PJ af.gour...@videotron.ca wrote: Is there any definitive install guide for flashplugin. I was able to install it on a 7.2 64bit machine and then on an i386 but somehow it has morphed into god-knows-what and no longer works. Any errors? I was just about to add what I had forgotten... latest fiddling with the non-working installation gives error: shared object libdl.so.2 not found required by libflashplugin.so And I've roamed the web trying to find solutions, but nothing really is solid... I used some instructions from crnl.org-blog-Flash 9 for FreeBSD 7.1 and it worked when I first installed it both on 7.2 x64bit and i386... but that wasn't for long.. I thought I had installed it with linux-f8 emulations but I found the linux-f4 on the machine... so I don't know what is going on. Now, trying to reinstall under linux-f8 and flashplugin9 does not work... I used the steps in the handbook[1] to get flash on my FreeBSD 8 machines. I never used flash on 7 because it wasn't worth the trouble. Things have changed since. I've been using 7.2 thinking it was to be stable for a while... oh, well... now I'm waiting for 8 to be released before switching. Adobe seems to be toally unreliable as to what they are doing with their software; at least from what I can see about the problems users are having with their products. Any major software vendor fits in this category, IMHO. But MS and Adobe are unbelievabley horrendous...and why they don't fix the problems their software have had for many years already is beyond me.. Not everything works for everyone. Computer configurations, hardware, OS, etc differ from person to person, company to company. Well, that's normal if the user has no idea of what they are doing... I'd hope I know a little more than that... but that doesn't help eityher... for instance, the only way I can get Windoze XP office to work is to set up a new user and it works fine... the original user just refuses to work... ridiculous... but then, I only use the damned thing when someone else has forceed me to open what they have made... So, the question - what is the latest method to get the flashplugin to work - what linux emulation, whick version of flashplugin... stumble, bumble and mumble ... [1] - http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/desktop-browsers.html#MOZ-FLASH-PLUGIN Yeah, I had installed that and it worked fine... but now it no longer works... I had it on two machines and two installations of 7.2 on the same machine... but now ... it no longer works... and I don't understand why... I did install gimp and inksckape on one of the installations, but neither the other nor this one wanted to work... so hurray for adobe and Linux... I waste more time trying to get their stuff to work without hindrances and Thanks for the suggestions. ___ 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: Anybody is using VirtualBox?
Glen Barber wrote: Hi, On Sat, Oct 24, 2009 at 12:23 PM, Yuri y...@rawbw.com wrote: I am tryingto run Windows under FreeBSD. When I run: cat /dev/ad1s1 | VBoxManage stdin OutPutFile.vdi 21474836480 on 80-RC2 I get this output: ERROR: failed to create the VirtualBox object! ERROR: code NS_ERROR_ABORT (0x80004004) - Operation aborted (extended info not available) Most likely, the VirtualBox COM server is not running or failed to start. No processes with name VirtualBox are running. What could be the problem? Do you have the vboxdrv.ko module loaded? I'll chime in here because I just de-installed virtualbox so it's fresh in mind. I had problems when I tried to run virtualbox after loading the vboxdrvr.ko manually while the machine was running. Maybe it crashed the machine, can't remember. After rebooting though, with the modules in /boot/modules/ and the modules having been loaded at boot time things worked great. So for me it was imperative that the module loaded at boot and not after the machine was fully up if I wanted virtualbox to run. (I de-installed because, after running opensolaris a few weeks, the novelty of virtual machines has worn off.) HTH sa ___ 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: changing cron's From: address in emails
On Sat, 24 Oct 2009 01:08:21 -0600 Kelly Martin kellymar...@gmail.com wrote: Greetings, here's a simple question for the FreeBSD gurus out there. I have several servers running cron scripts daily for me, and they all send me e-mail with their output. Regardless of which server it is, each of these e-mails have the From: address looking exactly the same. They all say they are from the Cron Daemon. Fine, but I'd like to know more clearly which server the cron output is from. How can I change the From: address of these emails to Myserver Cron Daemon instead? I know cron runs as the user, so it's not immediately obvious to me how to change the From: field. Already the subject line says something like Cron r...@myserver ... but this doesn't stand out enough for my tired eyes. Why don`t you just create some filter rules in your mua ? It may makes it clear for you if you create a folder for each host and filter your msg on receiving ? e.g. Inbox ... CronDir - Host 1 - Host 2 Cheers Daniel -- Just because I don`t care - Doesn`t mean I don`t understand ! -- Homer J. Simpson ___ 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
