[SLUG] MS2003 Server training for freedom hating customer!?
Hi Guys, It doesent matter how hard i try I cant seem to get away from customers that have MS 2000 or MS 2003 servers. I have resided myself to the fact that I am going to have to be trained in this area, so my question is: can anyone recommend a training provider that provide courses in MS Server and Exchange Server training (e.g. over a week or so)? -- Thanks in advance! Trent -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
Re: [SLUG] mdadm
Hi David, Removing mdadm is okay, no hotplug devices use it and it only required if you have a software RAID device/setup. From the bug report that you posted, this is a new feature that gets you to make sure the mdadm.conf file is the same as the out of a mdadm scan. This causes the failure of your initrd creation as initrd builds depend on mdadm being happy (because you can include modules related to mdadm to be built into your initrd to bring up hardware devices before mdadm tries to create md devices) before they are built. -- Steve (sorry, just hit reply before thinking.. must be from my intense three day session on forgetting all about work) :-} david wrote: I'm getting error messages about mdadm. There are suggestions that this can be removed if not using RAID (I don't). [1] Are there any other issues with removing it? EG: hotplug devices like USB storage devices etc. Google isn't really making this clear. thanks... David p[1] https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/98911 __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __ -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
Re: [SLUG] mdadm
On Tue, 2007-06-12 at 17:11 +1000, Steve Granger wrote: Hi David, Removing mdadm is okay, no hotplug devices use it and it only required if you have a software RAID device/setup. From the bug report that you posted, this is a new feature that gets you to make sure the mdadm.conf file is the same as the out of a mdadm scan. This causes the failure of your initrd creation as initrd builds depend on mdadm being happy (because you can include modules related to mdadm to be built into your initrd to bring up hardware devices before mdadm tries to create md devices) before they are built. yes... I removed, but then re-installed because of all the nasty warnings I was getting. I'm not entirely sure where I'm at now - not quite game to re-boot just yet. Nothing is simple :( -- Steve (sorry, just hit reply before thinking.. must be from my intense three day session on forgetting all about work) :-} david wrote: I'm getting error messages about mdadm. There are suggestions that this can be removed if not using RAID (I don't). [1] Are there any other issues with removing it? EG: hotplug devices like USB storage devices etc. Google isn't really making this clear. thanks... David p[1] https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/98911 __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __ -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
Re: [SLUG] mdadm
david wrote: On Tue, 2007-06-12 at 17:11 +1000, Steve Granger wrote: Hi David, Removing mdadm is okay, no hotplug devices use it and it only required if you have a software RAID device/setup. From the bug report that you posted, this is a new feature that gets you to make sure the mdadm.conf file is the same as the out of a mdadm scan. This causes the failure of your initrd creation as initrd builds depend on mdadm being happy (because you can include modules related to mdadm to be built into your initrd to bring up hardware devices before mdadm tries to create md devices) before they are built. yes... I removed, but then re-installed because of all the nasty warnings I was getting. I'm not entirely sure where I'm at now - not quite game to re-boot just yet. Nothing is simple :( So you've removed mdadm? what happens when you run dpkg-configure -a? does the install process finish? run update-initramfs -k all -u to get your initrd to build again, it should do this without complaining now. Seems like a few people in the bug thread ignored the error, rebooted and didn't have their systems come up... Good way to learn how to use a rescue CD... -- Steve (sorry, just hit reply before thinking.. must be from my intense three day session on forgetting all about work) :-} david wrote: I'm getting error messages about mdadm. There are suggestions that this can be removed if not using RAID (I don't). [1] Are there any other issues with removing it? EG: hotplug devices like USB storage devices etc. Google isn't really making this clear. thanks... David p[1] https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/98911 __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __ __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __ -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
[SLUG] KHTML version of Safari 3 ?
Question: Which KHTML release is Safari using? Is there an about:buildconfig equivalent ? Rant: I think that it's great that Safari to coming to Windows. From a technical point it mean's that the Konqueror's KHTML engine has been ported to Windows. It will also help in web development. Because the closest I got to testing Safari in a Windows development environment was running a VMWare instance of Linux with Konqueror. -- Simon Males [EMAIL PROTECTED] -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
Re: [SLUG] Remotely executing scheduled tasks using samba
Basically yeah. -- Simon Males [EMAIL PROTECTED] Dean Hamstead wrote: like say? ssh [EMAIL PROTECTED] /path/somescript.sh Dean Simon Males wrote: Hello all, Earlier today I found out that Windows Scheduled Tasks can be executed remotely from another Windows system using schtasks.exe with the following syntax: schtasks /Run /TN Backups /S remote_system_name This is actually quite cool. Though I need to do this from a Linux system. Has anyone used schtasks from a Linux system? Or know about MS-RPC (which I guess is doing the ground work). -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
Re: [SLUG] mdadm
On Tue, 2007-06-12 at 17:55 +1000, Steve Granger wrote: david wrote: On Tue, 2007-06-12 at 17:11 +1000, Steve Granger wrote: Hi David, Removing mdadm is okay, no hotplug devices use it and it only required if you have a software RAID device/setup. From the bug report that you posted, this is a new feature that gets you to make sure the mdadm.conf file is the same as the out of a mdadm scan. This causes the failure of your initrd creation as initrd builds depend on mdadm being happy (because you can include modules related to mdadm to be built into your initrd to bring up hardware devices before mdadm tries to create md devices) before they are built. yes... I removed, but then re-installed because of all the nasty warnings I was getting. I'm not entirely sure where I'm at now - not quite game to re-boot just yet. Nothing is simple :( So you've removed mdadm? what happens when you run dpkg-configure -a? does the install process finish? run update-initramfs -k all -u to get your initrd to build again, it should do this without complaining now. Seems like a few people in the bug thread ignored the error, rebooted and didn't have their systems come up... Good way to learn how to use a rescue CD... Ha! rescue CD's are great things to NOT need ;-) I had some fstab disasters and learned about rescue CD's then. I'm doing dpkg-reconfigure -a while I'm writing this. I did get this message: update-initramfs: Generating /boot/initrd.img-2.6.20-16-386 W: mdadm: unchecked configuration file: /etc/mdadm/mdadm.conf W: mdadm: please read /usr/share/doc/mdadm/README.upgrading-2.5.3.gz . W: mdadm: no arrays defined in configuration file. W: mdadm: falling back to emergency procedure in initramfs. then later: update-initramfs: Generating /boot/initrd.img-2.6.20-16-386 W: mdadm: unchecked configuration file: /etc/mdadm/mdadm.conf W: mdadm: please read /usr/share/doc/mdadm/README.upgrading-2.5.3.gz . W: mdadm: no arrays defined in configuration file. W: mdadm: falling back to emergency procedure in initramfs. update-initramfs: Generating /boot/initrd.img-2.6.20-16-386 W: mdadm: unchecked configuration file: /etc/mdadm/mdadm.conf W: mdadm: please read /usr/share/doc/mdadm/README.upgrading-2.5.3.gz . W: mdadm: no arrays defined in configuration file. W: mdadm: falling back to emergency procedure in initramfs. Bear in mind that I apt-get removed mdadm but then apt-get installed it again because the error messages scared me ;-) Oh what fun when you don't know what you are doing ;-) -- Steve (sorry, just hit reply before thinking.. must be from my intense three day session on forgetting all about work) :-} david wrote: I'm getting error messages about mdadm. There are suggestions that this can be removed if not using RAID (I don't). [1] Are there any other issues with removing it? EG: hotplug devices like USB storage devices etc. Google isn't really making this clear. thanks... David p[1] https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/98911 __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __ __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __ -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
Re: [SLUG] vmware-server and kernel headers
Hi David, actually my last email meant to say that if you have an old version (of vmware) uninstall it first... not gcc. My apologies. I'm not a linux guru and I don't know debian ways. Can debian do rpm's? Is there a different installation you can use rather than apt-get? Also try to give a smaller amount of memory if the VM will not power on. Sometimes it has to do with lack of available memory... in that you may have only 1GB but have 3 VM's each with 1GB memory. At some stage one or more VM's will refuse to start. Hope this helps Ben david wrote: On Mon, 2007-06-11 at 15:35 +1000, Ben Donohue wrote: Hi David, make sure gcc is installed. gcc is the latest version according to apt-get [EMAIL PROTECTED]:~ $ ls -l /usr/bin/gcc lrwxrwxrwx 1 root root 7 2007-05-26 22:10 /usr/bin/gcc - gcc-4.1 gcc-4.0 also exists, but isn't symlinked. Should I uninstall it? if you've got an old version, uninstall it first. I run rpm -i VMware-server-1.0.1-29996.i386.rpm (or whatever version) after you've installed run /usr/bin/vmware-config.pl I was using apt-get, which seems to configure as part of the installation, and installs vmware-server_1.0.3-1_i386.deb . I get as far as a vmware configuration gui, which looks fine until I click on the power on button, but then fails with a message which simply says error. I don't know if this relates to the linux-headers issue or not. All I know is that it doesn't work :( If the linux-headers version DOES matter, I can't see how to get around the packaging problem. I'm using 2.6.20-15, but the package insists on 2.6.20-16 and try as I might, I can't get past that. I've fiddled around with different package installation sequences including using dkpg -i one package at a time, but the apt insists that on doing it the way it wants to. I've already installed linux-headers for 2.6.20-15 (successfully) but vmware insists on an upgrade to 16. It looks like maybe the vmware-server deb package has got ahead of the kernel package. (I believe there were some problems with 2.6.20-16) I would be really happy if someone would tell me I'm wrong. Failing that, how to resolve the tarball problem (below). many thanks... David. do you get that far? Ben david wrote: I'm getting some conflicts (?) with the feisty vmware package: [EMAIL PROTECTED]:~ $ uname -a Linux test 2.6.20-15-386 #2 Sun Apr 15 07:34:00 UTC 2007 i686 GNU/Linux [EMAIL PROTECTED]:~ $ sudo apt-get install vmware-server The following NEW packages will be installed vmware-server vmware-server-kernel-modules vmware-server-kernel-modules-2.6.20-16 VMware installs, configures, but fails to power up. vmware-server-kernel-modules-2.6.20-15 is in the repository but I have no idea how to get apt-get to install it appropriately. I tried installing from tar, but the installer asks for linux-headers-386 but isn't happy with /usr/src/linux-headers-2.6.20-15-386/ Are they the same thing? should I put in a symlink perhaps? What's more annoying is that my friend has apt-get installed vmware on feisty without any issues and it works perfectly :( -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
Re: [SLUG] mdadm
On Tue, 2007-06-12 at 17:55 +1000, Steve Granger wrote: david wrote: On Tue, 2007-06-12 at 17:11 +1000, Steve Granger wrote: Hi David, Removing mdadm is okay, no hotplug devices use it and it only required if you have a software RAID device/setup. From the bug report that you posted, this is a new feature that gets you to make sure the mdadm.conf file is the same as the out of a mdadm scan. This causes the failure of your initrd creation as initrd builds depend on mdadm being happy (because you can include modules related to mdadm to be built into your initrd to bring up hardware devices before mdadm tries to create md devices) before they are built. yes... I removed, but then re-installed because of all the nasty warnings I was getting. I'm not entirely sure where I'm at now - not quite game to re-boot just yet. Nothing is simple :( So you've removed mdadm? what happens when you run dpkg-configure -a? does the install process finish? Everything finished. run update-initramfs -k all -u Lots of warnings (see below). I sort of think these are not problems, because I don't have any raid devices but I'm still bothered that I might reboot and die! Some of the messages are pretty cryptic if you don't actually know. God help a beginner. Maybe I shouldn't worry so much - just re-boot and hope. I really did read /usr/share/doc/mdadm/README.upgrading-2.5.3.gz as suggested, but I'm not a lot wiser. At least I've got a vague idea what initramfs IS now. I still can't guess what md is administering.Multi Device? [EMAIL PROTECTED]:~/test $ sudo update-initramfs -k all -u Password: update-initramfs: Generating /boot/initrd.img-2.6.20-16-386 W: mdadm: unchecked configuration file: /etc/mdadm/mdadm.conf W: mdadm: please read /usr/share/doc/mdadm/README.upgrading-2.5.3.gz . W: mdadm: no arrays defined in configuration file. W: mdadm: falling back to emergency procedure in initramfs. update-initramfs: Generating /boot/initrd.img-2.6.20-15-386 W: mdadm: unchecked configuration file: /etc/mdadm/mdadm.conf W: mdadm: please read /usr/share/doc/mdadm/README.upgrading-2.5.3.gz . W: mdadm: no arrays defined in configuration file. W: mdadm: falling back to emergency procedure in initramfs. update-initramfs: Generating /boot/initrd.img-2.6.17-10-386 W: mdadm: unchecked configuration file: /etc/mdadm/mdadm.conf W: mdadm: please read /usr/share/doc/mdadm/README.upgrading-2.5.3.gz . W: mdadm: no arrays defined in configuration file. W: mdadm: falling back to emergency procedure in initramfs. update-initramfs: Generating /boot/initrd.img-2.6.15-23-386 W: udev hook script requires at least kernel version 2.6.17 W: not generating requested initramfs for kernel 2.6.15-23-386 to get your initrd to build again, it should do this without complaining now. Seems like a few people in the bug thread ignored the error, rebooted and didn't have their systems come up... Good way to learn how to use a rescue CD... -- Steve (sorry, just hit reply before thinking.. must be from my intense three day session on forgetting all about work) :-} david wrote: I'm getting error messages about mdadm. There are suggestions that this can be removed if not using RAID (I don't). [1] Are there any other issues with removing it? EG: hotplug devices like USB storage devices etc. Google isn't really making this clear. thanks... David p[1] https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/98911 __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __ __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __ -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
Re: [SLUG] mdadm
... snip update-initramfs -k all -u Lots of warnings (see below). I sort of think these are not problems, because I don't have any raid devices but I'm still bothered that I might reboot and die! Some of the messages are pretty cryptic if you don't actually know. God help a beginner. Maybe I shouldn't worry so much - just re-boot and hope. I really did read /usr/share/doc/mdadm/README.upgrading-2.5.3.gz as suggested, but I'm not a lot wiser. At least I've got a vague idea what initramfs IS now. I still can't guess what md is administering.Multi Device? so you have rm -f /var/lib/mdadm/CONF-UNCHECKED got rid of the errors for me.. on a system running software raid, not that it should matter. [EMAIL PROTECTED]:~/test $ sudo update-initramfs -k all -u Password: update-initramfs: Generating /boot/initrd.img-2.6.20-16-386 W: mdadm: unchecked configuration file: /etc/mdadm/mdadm.conf W: mdadm: please read /usr/share/doc/mdadm/README.upgrading-2.5.3.gz . W: mdadm: no arrays defined in configuration file. W: mdadm: falling back to emergency procedure in initramfs. update-initramfs: Generating /boot/initrd.img-2.6.20-15-386 W: mdadm: unchecked configuration file: /etc/mdadm/mdadm.conf W: mdadm: please read /usr/share/doc/mdadm/README.upgrading-2.5.3.gz . W: mdadm: no arrays defined in configuration file. W: mdadm: falling back to emergency procedure in initramfs. update-initramfs: Generating /boot/initrd.img-2.6.17-10-386 W: mdadm: unchecked configuration file: /etc/mdadm/mdadm.conf W: mdadm: please read /usr/share/doc/mdadm/README.upgrading-2.5.3.gz . W: mdadm: no arrays defined in configuration file. W: mdadm: falling back to emergency procedure in initramfs. update-initramfs: Generating /boot/initrd.img-2.6.15-23-386 W: udev hook script requires at least kernel version 2.6.17 W: not generating requested initramfs for kernel 2.6.15-23-386 ... snip -- Steve __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __ -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
Re: [SLUG] Postfix question
My apologies to anyone looking at this in the archives and wondering why I seem to be responding to a non-existent email. Howard didn't feel that his email was worth archiving, even thous the replies are going to be archived. On 13/06/07, Howard Lowndes [EMAIL PROTECTED] wrote: I have a Linux/Postfix server that accepts email from the Internet, performs filtering checks on the email and then forwards acceptable emails onto a Linux/Domino server on the local intranet. The Postfix checks are all being done by LDAP so I am able to see what is happening on the Linux/Postfix server. Postfix has the relayhost parameter set in main.cf to point to the Linux/Domino server so that emails are correctly forwarded on. I can see the Linux/Postfix server doing all the checks that I have specified in main.cf. These include: smtpd_client_restrictions smtpd_helo_restrictions smtpd_sender_restrictions smtpd_recipient_restrictions However, the smtpd_recipient_restrictions appear to be failing safe with a default DUNNO result rather than a default REJECT result. The same checks, when not used in conjunction with a relayhost setting appear to default fail as REJECT rather than DUNNO. Am I right in assuming that the use of the relayhost parameter is causing this change in default behaviour, and how is the best way to fix it? The Domino machine, being the real MTA, obviously knows what addresses it's going to accept mail for (the ones that are defined as valid addresses) and which it's going to reject (the rest - unless it has a catchall, in which case, there aren't any that it will reject). Does the Postfix machine have some way of knowing this same information, or is it just left knowing that all mail for that domain gets forwarded to 1.2.3.4? -- There is nothing more worthy of contempt than a man who quotes himself - Zhasper, 2004 -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
Re: [SLUG] mdadm
On Wed, 2007-06-13 at 10:22 +1000, Steve Granger wrote: ... snip update-initramfs -k all -u Lots of warnings (see below). I sort of think these are not problems, because I don't have any raid devices but I'm still bothered that I might reboot and die! Some of the messages are pretty cryptic if you don't actually know. God help a beginner. Maybe I shouldn't worry so much - just re-boot and hope. I really did read /usr/share/doc/mdadm/README.upgrading-2.5.3.gz as suggested, but I'm not a lot wiser. At least I've got a vague idea what initramfs IS now. I still can't guess what md is administering.Multi Device? so you have rm -f /var/lib/mdadm/CONF-UNCHECKED got rid of the errors for me.. on a system running software raid, not that it should matter. GR same warnings (see below)... it's the word emergency that keeps worrying me, especially since I really don't quite know what's going on. (thanks for your help by the way) regards, David [EMAIL PROTECTED]:~ $ sudo mv /var/lib/mdadm/CONF-UNCHECKED /home/david [EMAIL PROTECTED]:~ $ sudo update-initramfs -k all -u update-initramfs: Generating /boot/initrd.img-2.6.20-16-386 W: mdadm: /etc/mdadm/mdadm.conf defines no arrays. W: mdadm: no arrays defined in configuration file. W: mdadm: falling back to emergency procedure in initramfs. update-initramfs: Generating /boot/initrd.img-2.6.20-15-386 W: mdadm: /etc/mdadm/mdadm.conf defines no arrays. W: mdadm: no arrays defined in configuration file. W: mdadm: falling back to emergency procedure in initramfs. update-initramfs: Generating /boot/initrd.img-2.6.17-10-386 W: mdadm: /etc/mdadm/mdadm.conf defines no arrays. W: mdadm: no arrays defined in configuration file. W: mdadm: falling back to emergency procedure in initramfs. update-initramfs: Generating /boot/initrd.img-2.6.15-23-386 W: udev hook script requires at least kernel version 2.6.17 W: not generating requested initramfs for kernel 2.6.15-23-386 [EMAIL PROTECTED]:~ $ [EMAIL PROTECTED]:~/test $ sudo update-initramfs -k all -u Password: update-initramfs: Generating /boot/initrd.img-2.6.20-16-386 W: mdadm: unchecked configuration file: /etc/mdadm/mdadm.conf W: mdadm: please read /usr/share/doc/mdadm/README.upgrading-2.5.3.gz . W: mdadm: no arrays defined in configuration file. W: mdadm: falling back to emergency procedure in initramfs. update-initramfs: Generating /boot/initrd.img-2.6.20-15-386 W: mdadm: unchecked configuration file: /etc/mdadm/mdadm.conf W: mdadm: please read /usr/share/doc/mdadm/README.upgrading-2.5.3.gz . W: mdadm: no arrays defined in configuration file. W: mdadm: falling back to emergency procedure in initramfs. update-initramfs: Generating /boot/initrd.img-2.6.17-10-386 W: mdadm: unchecked configuration file: /etc/mdadm/mdadm.conf W: mdadm: please read /usr/share/doc/mdadm/README.upgrading-2.5.3.gz . W: mdadm: no arrays defined in configuration file. W: mdadm: falling back to emergency procedure in initramfs. update-initramfs: Generating /boot/initrd.img-2.6.15-23-386 W: udev hook script requires at least kernel version 2.6.17 W: not generating requested initramfs for kernel 2.6.15-23-386 ... snip -- Steve __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __ -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
[SLUG] Off-topic ThinkPad X60s
Hi List, To sell a brand new ThinkPad X60s at a discount, if anyone is interested please email me off list. Cheers, Chris -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
Re: [SLUG] mdadm
On Wed, Jun 13, 2007 at 11:25:36AM +1000, david wrote: On Wed, 2007-06-13 at 10:22 +1000, Steve Granger wrote: ... snip update-initramfs -k all -u Lots of warnings (see below). I sort of think these are not problems, because I don't have any raid devices but I'm still bothered that I might reboot and die! Some of the messages are pretty cryptic if you don't actually know. God help a beginner. Maybe I shouldn't worry so much - just re-boot and hope. I really did read /usr/share/doc/mdadm/README.upgrading-2.5.3.gz as suggested, but I'm not a lot wiser. At least I've got a vague idea what initramfs IS now. I still can't guess what md is administering.Multi Device? so you have rm -f /var/lib/mdadm/CONF-UNCHECKED got rid of the errors for me.. on a system running software raid, not that it should matter. GR same warnings (see below)... it's the word emergency that keeps worrying me, especially since I really don't quite know what's going on. (thanks for your help by the way) what does /etc/mdadm/mdadm.conf look like also can you copy cat /proc/mdstat regards, David [EMAIL PROTECTED]:~ $ sudo mv /var/lib/mdadm/CONF-UNCHECKED /home/david [EMAIL PROTECTED]:~ $ sudo update-initramfs -k all -u update-initramfs: Generating /boot/initrd.img-2.6.20-16-386 W: mdadm: /etc/mdadm/mdadm.conf defines no arrays. W: mdadm: no arrays defined in configuration file. W: mdadm: falling back to emergency procedure in initramfs. update-initramfs: Generating /boot/initrd.img-2.6.20-15-386 W: mdadm: /etc/mdadm/mdadm.conf defines no arrays. W: mdadm: no arrays defined in configuration file. W: mdadm: falling back to emergency procedure in initramfs. update-initramfs: Generating /boot/initrd.img-2.6.17-10-386 W: mdadm: /etc/mdadm/mdadm.conf defines no arrays. W: mdadm: no arrays defined in configuration file. W: mdadm: falling back to emergency procedure in initramfs. update-initramfs: Generating /boot/initrd.img-2.6.15-23-386 W: udev hook script requires at least kernel version 2.6.17 W: not generating requested initramfs for kernel 2.6.15-23-386 [EMAIL PROTECTED]:~ $ [EMAIL PROTECTED]:~/test $ sudo update-initramfs -k all -u Password: update-initramfs: Generating /boot/initrd.img-2.6.20-16-386 W: mdadm: unchecked configuration file: /etc/mdadm/mdadm.conf W: mdadm: please read /usr/share/doc/mdadm/README.upgrading-2.5.3.gz . W: mdadm: no arrays defined in configuration file. W: mdadm: falling back to emergency procedure in initramfs. update-initramfs: Generating /boot/initrd.img-2.6.20-15-386 W: mdadm: unchecked configuration file: /etc/mdadm/mdadm.conf W: mdadm: please read /usr/share/doc/mdadm/README.upgrading-2.5.3.gz . W: mdadm: no arrays defined in configuration file. W: mdadm: falling back to emergency procedure in initramfs. update-initramfs: Generating /boot/initrd.img-2.6.17-10-386 W: mdadm: unchecked configuration file: /etc/mdadm/mdadm.conf W: mdadm: please read /usr/share/doc/mdadm/README.upgrading-2.5.3.gz . W: mdadm: no arrays defined in configuration file. W: mdadm: falling back to emergency procedure in initramfs. update-initramfs: Generating /boot/initrd.img-2.6.15-23-386 W: udev hook script requires at least kernel version 2.6.17 W: not generating requested initramfs for kernel 2.6.15-23-386 ... snip -- Steve __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __ -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html signature.asc Description: Digital signature -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
Re: [SLUG] MS2003 Server training for freedom hating customer!?
thanks matt - i will take a look. Trent On 13/06/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hi Guys, It doesent matter how hard i try I cant seem to get away from customers that have MS 2000 or MS 2003 servers. I have resided myself to the fact that I am going to have to be trained in this area, so my question is: can anyone recommend a training provider that provide courses in MS Server and Exchange Server training (e.g. over a week or so)? I've used dimension data for citrix in the past and they were pretty good, http://www.ddls.com.au another alternative that the windows guys where I work use is new horizons http://www.nhaustralia.com.au their advantage is you don't have to complete the courses in a block of days if thats difficult for you to arrange, you can do them a day or two a week, not instructor led, but you have access to the instructor on site if you need, otherwise self paced at their site. HTH Matt Chan -- Regards, Trent Murray IT Consultant Guardian Technology Group T: 0419 39 99 78 F: 02 9543 7654 E: [EMAIL PROTECTED]received direct to mobile phone M: P.O Box 3269 Bangor N.S.W 2234 Member of Linux Australia Registered Microsoft Business Partner Authorised Ubuntu Solutions Provider -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
Re: [SLUG] MS2003 Server training for freedom hating customer!?
Hi Guys, It doesent matter how hard i try I cant seem to get away from customers that have MS 2000 or MS 2003 servers. I have resided myself to the fact that I am going to have to be trained in this area, so my question is: can anyone recommend a training provider that provide courses in MS Server and Exchange Server training (e.g. over a week or so)? I've used dimension data for citrix in the past and they were pretty good, http://www.ddls.com.au another alternative that the windows guys where I work use is new horizons http://www.nhaustralia.com.au their advantage is you don't have to complete the courses in a block of days if thats difficult for you to arrange, you can do them a day or two a week, not instructor led, but you have access to the instructor on site if you need, otherwise self paced at their site. HTH Matt Chan -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
Re: [SLUG] mdadm
On Wed, 2007-06-13 at 11:43 +1000, Alex Samad wrote: On Wed, Jun 13, 2007 at 11:25:36AM +1000, david wrote: On Wed, 2007-06-13 at 10:22 +1000, Steve Granger wrote: ... snip update-initramfs -k all -u Lots of warnings (see below). I sort of think these are not problems, because I don't have any raid devices but I'm still bothered that I might reboot and die! Some of the messages are pretty cryptic if you don't actually know. God help a beginner. Maybe I shouldn't worry so much - just re-boot and hope. I really did read /usr/share/doc/mdadm/README.upgrading-2.5.3.gz as suggested, but I'm not a lot wiser. At least I've got a vague idea what initramfs IS now. I still can't guess what md is administering.Multi Device? so you have rm -f /var/lib/mdadm/CONF-UNCHECKED got rid of the errors for me.. on a system running software raid, not that it should matter. GR same warnings (see below)... it's the word emergency that keeps worrying me, especially since I really don't quite know what's going on. (thanks for your help by the way) what does /etc/mdadm/mdadm.conf look like also can you copy cat /proc/mdstat [EMAIL PROTECTED]:~ $ cat /proc/mdstat Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10] unused devices: none [EMAIL PROTECTED]:~ $ cat /etc/mdadm/mdadm.conf DEVICE partitions MAILADDR root [EMAIL PROTECTED]:~ $ regards, David [EMAIL PROTECTED]:~ $ sudo mv /var/lib/mdadm/CONF-UNCHECKED /home/david [EMAIL PROTECTED]:~ $ sudo update-initramfs -k all -u update-initramfs: Generating /boot/initrd.img-2.6.20-16-386 W: mdadm: /etc/mdadm/mdadm.conf defines no arrays. W: mdadm: no arrays defined in configuration file. W: mdadm: falling back to emergency procedure in initramfs. update-initramfs: Generating /boot/initrd.img-2.6.20-15-386 W: mdadm: /etc/mdadm/mdadm.conf defines no arrays. W: mdadm: no arrays defined in configuration file. W: mdadm: falling back to emergency procedure in initramfs. update-initramfs: Generating /boot/initrd.img-2.6.17-10-386 W: mdadm: /etc/mdadm/mdadm.conf defines no arrays. W: mdadm: no arrays defined in configuration file. W: mdadm: falling back to emergency procedure in initramfs. update-initramfs: Generating /boot/initrd.img-2.6.15-23-386 W: udev hook script requires at least kernel version 2.6.17 W: not generating requested initramfs for kernel 2.6.15-23-386 [EMAIL PROTECTED]:~ $ [EMAIL PROTECTED]:~/test $ sudo update-initramfs -k all -u Password: update-initramfs: Generating /boot/initrd.img-2.6.20-16-386 W: mdadm: unchecked configuration file: /etc/mdadm/mdadm.conf W: mdadm: please read /usr/share/doc/mdadm/README.upgrading-2.5.3.gz . W: mdadm: no arrays defined in configuration file. W: mdadm: falling back to emergency procedure in initramfs. update-initramfs: Generating /boot/initrd.img-2.6.20-15-386 W: mdadm: unchecked configuration file: /etc/mdadm/mdadm.conf W: mdadm: please read /usr/share/doc/mdadm/README.upgrading-2.5.3.gz . W: mdadm: no arrays defined in configuration file. W: mdadm: falling back to emergency procedure in initramfs. update-initramfs: Generating /boot/initrd.img-2.6.17-10-386 W: mdadm: unchecked configuration file: /etc/mdadm/mdadm.conf W: mdadm: please read /usr/share/doc/mdadm/README.upgrading-2.5.3.gz . W: mdadm: no arrays defined in configuration file. W: mdadm: falling back to emergency procedure in initramfs. update-initramfs: Generating /boot/initrd.img-2.6.15-23-386 W: udev hook script requires at least kernel version 2.6.17 W: not generating requested initramfs for kernel 2.6.15-23-386 ... snip -- Steve __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __ -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
Re: [SLUG] mdadm
On Wed, Jun 13, 2007 at 12:29:53PM +1000, david wrote: On Wed, 2007-06-13 at 11:43 +1000, Alex Samad wrote: On Wed, Jun 13, 2007 at 11:25:36AM +1000, david wrote: On Wed, 2007-06-13 at 10:22 +1000, Steve Granger wrote: ... snip update-initramfs -k all -u Lots of warnings (see below). I sort of think these are not problems, because I don't have any raid devices but I'm still bothered that I might reboot and die! Some of the messages are pretty cryptic if you don't actually know. God help a beginner. Maybe I shouldn't worry so much - just re-boot and hope. I really did read /usr/share/doc/mdadm/README.upgrading-2.5.3.gz as suggested, but I'm not a lot wiser. At least I've got a vague idea what initramfs IS now. I still can't guess what md is administering.Multi Device? so you have rm -f /var/lib/mdadm/CONF-UNCHECKED got rid of the errors for me.. on a system running software raid, not that it should matter. GR same warnings (see below)... it's the word emergency that keeps worrying me, especially since I really don't quite know what's going on. (thanks for your help by the way) what does /etc/mdadm/mdadm.conf look like also can you copy cat /proc/mdstat [EMAIL PROTECTED]:~ $ cat /proc/mdstat Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10] unused devices: none [EMAIL PROTECTED]:~ $ cat /etc/mdadm/mdadm.conf DEVICE partitions MAILADDR root [EMAIL PROTECTED]:~ $ looks like you can ignore the messages, as your no running any raid partitions on the system There might still be some hooks in mkinitfs that tell it to look for raid disks and it baulks at the fact it can't find any regards, David [EMAIL PROTECTED]:~ $ sudo mv /var/lib/mdadm/CONF-UNCHECKED /home/david [EMAIL PROTECTED]:~ $ sudo update-initramfs -k all -u update-initramfs: Generating /boot/initrd.img-2.6.20-16-386 W: mdadm: /etc/mdadm/mdadm.conf defines no arrays. W: mdadm: no arrays defined in configuration file. W: mdadm: falling back to emergency procedure in initramfs. update-initramfs: Generating /boot/initrd.img-2.6.20-15-386 W: mdadm: /etc/mdadm/mdadm.conf defines no arrays. W: mdadm: no arrays defined in configuration file. W: mdadm: falling back to emergency procedure in initramfs. update-initramfs: Generating /boot/initrd.img-2.6.17-10-386 W: mdadm: /etc/mdadm/mdadm.conf defines no arrays. W: mdadm: no arrays defined in configuration file. W: mdadm: falling back to emergency procedure in initramfs. update-initramfs: Generating /boot/initrd.img-2.6.15-23-386 W: udev hook script requires at least kernel version 2.6.17 W: not generating requested initramfs for kernel 2.6.15-23-386 [EMAIL PROTECTED]:~ $ [EMAIL PROTECTED]:~/test $ sudo update-initramfs -k all -u Password: update-initramfs: Generating /boot/initrd.img-2.6.20-16-386 W: mdadm: unchecked configuration file: /etc/mdadm/mdadm.conf W: mdadm: please read /usr/share/doc/mdadm/README.upgrading-2.5.3.gz . W: mdadm: no arrays defined in configuration file. W: mdadm: falling back to emergency procedure in initramfs. update-initramfs: Generating /boot/initrd.img-2.6.20-15-386 W: mdadm: unchecked configuration file: /etc/mdadm/mdadm.conf W: mdadm: please read /usr/share/doc/mdadm/README.upgrading-2.5.3.gz . W: mdadm: no arrays defined in configuration file. W: mdadm: falling back to emergency procedure in initramfs. update-initramfs: Generating /boot/initrd.img-2.6.17-10-386 W: mdadm: unchecked configuration file: /etc/mdadm/mdadm.conf W: mdadm: please read /usr/share/doc/mdadm/README.upgrading-2.5.3.gz . W: mdadm: no arrays defined in configuration file. W: mdadm: falling back to emergency procedure in initramfs. update-initramfs: Generating /boot/initrd.img-2.6.15-23-386 W: udev hook script requires at least kernel version 2.6.17 W: not generating requested initramfs for kernel 2.6.15-23-386 ... snip -- Steve __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __ -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html signature.asc Description: Digital signature -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs:
Re: [SLUG] Postfix question
Howard, I think you have the wrong idea about relayhost. The relayhost parameter in main.cf of postfix is for you to specify an external SMTP server to send through (aka a smarthost). Don't specify an internal host for this (unless you insist on sending through that host). Usually the parameter would be set to your ISP's SMTP server, or the SMTP server specified by your SPF records. What you want to do is set up the relay_domains and transport parameters: Something like: relay_domains = yourdomainname.com.au transport_maps = hash:/etc/postfix/transport in main.cf and put in /etc/postfix/transport yourdomainname.com.au smtp:[192.168.0.143] Again, remember to run postmap /etc/postfix/transport Obviously you'll also have to adjust domain names and IP addresses as needed. http://www.postfix.org/ has wonderful documentation available. There are also a lot of examples that you can learn from. All the best. Raphael Howard Lowndes wrote: I have a Linux/Postfix server that accepts email from the Internet, performs filtering checks on the email and then forwards acceptable emails onto a Linux/Domino server on the local intranet. The Postfix checks are all being done by LDAP so I am able to see what is happening on the Linux/Postfix server. Postfix has the relayhost parameter set in main.cf to point to the Linux/Domino server so that emails are correctly forwarded on. I can see the Linux/Postfix server doing all the checks that I have specified in main.cf. These include: smtpd_client_restrictions smtpd_helo_restrictions smtpd_sender_restrictions smtpd_recipient_restrictions However, the smtpd_recipient_restrictions appear to be failing safe with a default DUNNO result rather than a default REJECT result. The same checks, when not used in conjunction with a relayhost setting appear to default fail as REJECT rather than DUNNO. Am I right in assuming that the use of the relayhost parameter is causing this change in default behaviour, and how is the best way to fix it? -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
