I recently installed openSUSE 12.1 on a system that ran well for years with 11.0 and earlier versions. There are a couple of problems. 1) It will not boot directly from the hard drive. I have to boot the install DVD and let it boot from the hard drive. If I try to boot from the hard drive, it stops after all the PCI IRQs are listed. Grub is configured to boot from the boot partition, which is sda1, 100 MB ext2. 2) The other, and more severe, problem is networking frequently fails to start. As this is my main system, I need networking. BTW, on this system, 12.1 seems sluggish compared to 11.0. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/12/11 10:41, JAMES KNOTT wrote:
I recently installed openSUSE 12.1 on a system that ran well for years with 11.0 and earlier versions. There are a couple of problems.
1) It will not boot directly from the hard drive. I have to boot the install DVD and let it boot from the hard drive. If I try to boot from the hard drive, it stops after all the PCI IRQs are listed. Grub is configured to boot from the boot partition, which is sda1, 100 MB ext2.
It freezes completely ? does the keyboard respond ?
2) The other, and more severe, problem is networking frequently fails to start. As this is my main system, I need networking.
With what message ? what does /var/log/messages say about the network ? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Cristian Rodríguez wrote:
1) It will not boot directly from the hard drive. I have to boot the install DVD and let it boot from the hard drive. If I try to boot from the hard drive, it stops after all the PCI IRQs are listed. Grub is configured to boot from the boot partition, which is sda1, 100 MB ext2.
It freezes completely ? does the keyboard respond ?
It simply stops at that point. I can use the keyboard to reboot.
2) The other, and more severe, problem is networking frequently fails to start. As this is my main system, I need networking.
With what message ? what does /var/log/messages say about the network ?
I'll have to check next time it happens. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott wrote:
With what message ? what does /var/log/messages say about the network ?
I'll have to check next time it happens.
Here's what was in dmesg: 14.389944] ifup[726]: Service network not started and mode 'auto' -> skipping Also, I had to reboot 3 times to get networking to work. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Thu, Dec 08, 2011 at 08:33:51AM -0500, James Knott wrote:
James Knott wrote:
With what message ? what does /var/log/messages say about the network ?
I'll have to check next time it happens.
Here's what was in dmesg: 14.389944] ifup[726]: Service network not started and mode 'auto' -> skipping
Also, I had to reboot 3 times to get networking to work.
Smells like a systemd issue. See http://en.opensuse.org/openSUSE:Most_annoying_bugs_12.1 in particular the reference to bug 725917. For a quick test it's possible to decide to use sysvinit from the bootloader menu. If using sysvinit works well please file a bug report and assign it to Frederic <fcrozat at suse dot com>. There're several articles in the wiki about it. They're not perfect but give you a good starting point. With your experience you'll also get enabled to enhance them. Thanks. Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany
On 08/12/11 10:33, James Knott wrote:
Also, I had to reboot 3 times to get networking to work.
try zypper in -f http://download.opensuse.org/repositories/home:/fcrozat:/systemd/openSUSE_12... and reboot, tell us the results ;) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Cristian Rodríguez wrote:
On 08/12/11 10:33, James Knott wrote:
Also, I had to reboot 3 times to get networking to work.
try
zypper in -f http://download.opensuse.org/repositories/home:/fcrozat:/systemd/openSUSE_12...
and reboot, tell us the results ;)
It still fails. I had to boot with system v to get it to work this time. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 08/12/11 14:09, James Knott wrote:
It still fails. I had to boot with system v to get it to work this time.
You mean, boot fails totally by now ? what happends if you remove "quiet" from the boot command line and add systemd.log_level=debug to it ? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Cristian Rodríguez wrote:
On 08/12/11 14:09, James Knott wrote:
It still fails. I had to boot with system v to get it to work this time.
You mean, boot fails totally by now ?
It fails frequently.
what happends if you remove "quiet" from the boot command line and add systemd.log_level=debug to it ?
I'll give that a try when I have some more time to experiment. Also, where is that "quiet" found? And where should I add that line? It appears this switch to systemctl was a bit premature, as it breaks a lot of things. A few months ago, I built a server at work with 11.4. I am very grateful that I didn't attempt it with 12.1. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 08/12/11 15:22, James Knott wrote:
I'll give that a try when I have some more time to experiment. Also, where is that "quiet" found? And where should I add that line?
in /boot/grub/menu.lst
It appears this switch to systemctl was a bit premature, as it breaks a lot of things.
Not a single one broke in a significant way in any machine I have put my hands on. I believe there is something wrong in your particular setup. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 12/8/2011 10:44 AM, Cristian Rodríguez wrote:
On 08/12/11 15:22, James Knott wrote:
I'll give that a try when I have some more time to experiment. Also, where is that "quiet" found? And where should I add that line?
in /boot/grub/menu.lst
It appears this switch to systemctl was a bit premature, as it breaks a lot of things.
Not a single one broke in a significant way in any machine I have put my hands on.
I believe there is something wrong in your particular setup.
Boy that sounds familiar..... Here we go again. They haven't even got systemd running reliably on Fedora as any simple google will reveal. If its too soon to be reliable, its also too soon to start blaming the users. -- _____________________________________ ---This space for rent--- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
John Andersen said the following on 12/08/2011 02:43 PM:
They haven't even got systemd running reliably on Fedora as any simple google will reveal.
Perhaps the articles you are viewing are out of date or apply to specific machines and configurations. I'm running Fedora 15 on a crappy old AMD-64 I picked up at a thrift store and and crappy old 20G drive to boot it from and NFS mount to all the space consuming stuff as spare LVM partitions on my server. Not quite PXE/diskless - HAHA :-) While SystemD is strange for me, once I figure something out it works quite reliably. This isn't to say that packaging/imposing it on openSuse for 12.1 will give you the same result, but I can say for sure, for sure, for sure I tell you three times, it works OK on Fedora-15, right here, right now. Fedora-14, dunno; Fedora-16, dunno. But it does run reliable for Fedora-15. You are quite entitled to do what I did; go down to your local thrift store and pick up a crappy old machine and enough disk and memory (ooh, lots of memory, I can let you have some DDR2/1G at a reasonable price if you can't find any on eBay), and put stock-from-the-DVD Fedora-15 on it and see for yourself that SystemD **CAN** work satisfactorily. I'll grant you that apart from the NFS for much of the file system I'm not doing anything esoteric with this, but its does all the good stuff; mail, Apache, KDE (in ~/.kde not ~/.kde4), thunderbird, konq and dolphin, firefox, LibreOffice, gwenview, Skype. I've not tried Gimp or Scribus. All the hassles I usually have with flash, of course :-( I doubt that has to do with SystemD though. Sorry if I burst you pretty "SystemD is useless" balloon, but there you are. I have to face up to the evidence in front of me, no matter what google might report about the past. Heck, when I'm looking for stuff about Suse I usually limit my searches to the last year so I don't get results about 8.3 and 10.0 and other time wasting articles. It is possible, I suppose, that Suse is more demanding than Fedora and that Suse 12.1 and the SystemD there won't run on this price of thrift store crap even though Fedora does. I might try that. -- He who would make his own liberty secure must guard even his enemy from oppression; for if he violates this duty he establishes a precedent that will reach to himself. --Thomas Paine -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Cristian Rodríguez wrote:
Not a single one broke in a significant way in any machine I have put my hands on.
I believe there is something wrong in your particular setup.
Can you start fetchmail in system runlevel? Any other way other than from command line? Does postfix run out of the box? Can you start stuff with after.local? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 08/12/11 17:52, James Knott wrote:
Can you start fetchmail in system runlevel? Any other way other than from command line? Does postfix run out of the box? Can you start stuff with after.local?
yes to those 3 things. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Cristian Rodríguez wrote:
On 08/12/11 17:52, James Knott wrote:
Can you start fetchmail in system runlevel? Any other way other than from command line? Does postfix run out of the box? Can you start stuff with after.local?
yes to those 3 things.
How did you get fetchmail to run with systemd? I have to manually start it from the command line. I previously used a script started by after.local and on a server I built at work, I enabled it in System Services. Neither of those methods work with 12.1. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott said the following on 12/09/2011 10:04 AM:
Cristian Rodríguez wrote:
On 08/12/11 17:52, James Knott wrote:
Can you start fetchmail in system runlevel? Any other way other than from command line? Does postfix run out of the box? Can you start stuff with after.local?
yes to those 3 things.
How did you get fetchmail to run with systemd? I have to manually start it from the command line. I previously used a script started by after.local and on a server I built at work, I enabled it in System Services. Neither of those methods work with 12.1.
I run fetchmail on a seperate machine, a mail hub, so this isn't going to be an issue for me until that gets upgraded. But here are my thoughts. Unlike my Fedora box, openSuse seems to want you to use Postix or ... what is it, 'exim'? Check if postfix service is running: sudo systemctl status postfix.service Try cloning that, but make it dependent on Postfix - obviously :-) -- Warning: Do not attempt to stop blade with hands. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Anton Aylward wrote:
I run fetchmail on a seperate machine, a mail hub, so this isn't going to be an issue for me until that gets upgraded.
But here are my thoughts.
Unlike my Fedora box, openSuse seems to want you to use Postix or ... what is it, 'exim'?
Check if postfix service is running:
sudo systemctl status postfix.service
Try cloning that, but make it dependent on Postfix - obviously:-)
I have postfix running, by following the instructions posted earlier. It's fetchmail that I need to run, in order to get my mail from my ISP's POP server. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Fri, Dec 09, 2011 at 10:56:46AM -0500, James Knott wrote:
Anton Aylward wrote:
I run fetchmail on a seperate machine, a mail hub, so this isn't going to be an issue for me until that gets upgraded.
But here are my thoughts.
Unlike my Fedora box, openSuse seems to want you to use Postix or ... what is it, 'exim'?
Postfix since many, many, many years is the default MTA. All the remaining stuff is either legacy (sendmail) or community driven (exim). As both exim and postfix offer a sendmail compatible commandline interface who cares?
Check if postfix service is running:
sudo systemctl status postfix.service
Try cloning that, but make it dependent on Postfix - obviously:-)
I have postfix running, by following the instructions posted earlier. It's fetchmail that I need to run, in order to get my mail from my ISP's POP server.
The fetchmail package includes a fetchmail init script. What do you need more? Answer: "I neee to know what a init script is, how it is handled, and how I activate this service at boot time." a) /etc/init.d/fetchmail b) hip:~ # service fetchmail start /etc/fetchmailrc not existing Opps, looks like I'm a loser and have to create a /etc/fetchmailrc file. I expect you have one. Place it a copy of it at /etc/fetchmailrc and try again. c) Enable the fetchmail service to get started at boot time: hip:~ # chkconfig -a fetchmail Note: This output shows SysV services only and does not include native systemd services. SysV configuration data might be overridden by native systemd configuration. fetchmail 0:off 1:off 2:off 3:on 4:off 5:on 6:off This will fail if no smtp daemon (postfix, sendmail, exim) is enabled to get started too. BTW Have I said this is all well documented? Either in the openSUSE wiki or in the documentation which is part of each release. I know only suckers read documentation and manuals ... Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany
Lars Müller said the following on 12/09/2011 11:18 AM:
On Fri, Dec 09, 2011 at 10:56:46AM -0500, James Knott wrote:
Anton Aylward wrote:
I run fetchmail on a seperate machine, a mail hub, so this isn't going to be an issue for me until that gets upgraded.
But here are my thoughts.
Unlike my Fedora box, openSuse seems to want you to use Postix or ... what is it, 'exim'? Postfix since many, many, many years is the default MTA.
All the remaining stuff is either legacy (sendmail) or community driven (exim).
As both exim and postfix offer a sendmail compatible commandline interface who cares?
While that's true, it makes many assumptions that aren't valid in all situations. More specifically, they aren't valid in *MY* situation. So here's my LAN with a mail hub. The mail hub runs Postfix and SpamAssassin and Dovecot. (There's AV and sanitizer in there somewhere too but never mind.) All are well configured and reliable. There there are workstations. Workstations tend to be minimalist where possible. Not quite "thin clients", but .... (In theory they could PXE boot W/XP, but that's another matter) Their Syslog writes to the Syslog server, for example. So they don't need large /var file systems. They *ALL* use the mail hub. They *ALL* use Thunderbird, and Thunderbird is configured to read mail from the Dovecot IMAP server on the mail hub and send outgoing mail to the Postfix server on the mail hub.
From the user's point of view there is no mail handling on the workstation, its all done on the mail hub.
But some legacy software under Linux still wants to report via mail. That's OK. The workstations have no need for a sophisticated MTA. All they need is a minimalist shim invoked as 'sendmail' that punts the mail over to the mail hub. Yes, postfix and exim can do that, but they are about 10^4 times the size required. There is not need for routing - its hard coded; no need for all the sophistication that any of the classical MTAs supply. Its a shim, a pipe. It could be done with a small script, perl, python, , whatever, if you have those binaries running anyway. All they have to do is to be able to be invoked as /usr/bin/sendmail and punt the mail over to the mail hub. Not complicated. I choose to use the esmtp package. Yes it no longer being developed. That's because there's not much to it. Its minimalist and only needs one line of config: hostname = mailhub:25 Postfix is great. I love Postfix. I just don't want to have to install and configure and debug it on all machines, all thin clients, all PXE boots, all virtual machines. For many home users, even those not running their own mailhub, Postfix is still massive overkill. Their ISP acts as a mail hub - they *have* to proxy all mail there as the ISPs anti-spam measure won't let them send directly to arbitrary mail servers on the 'Net, and they read their mail from mailboxes supplied by the ISP or at Gmail or similar, and so don't have incoming mail to their machine. So Postfix is an unnecessary overhead. Not everyone has the same needs. -- The surest way to corrupt a youth is to instruct him to hold in higher esteem those who think alike than those who think differently. -- Friedrich Nietzsche -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Fri, Dec 09, 2011 at 12:22:08PM -0500, Anton Aylward wrote:
Lars Müller said the following on 12/09/2011 11:18 AM: [ 8< ]
As both exim and postfix offer a sendmail compatible commandline interface who cares?
While that's true, it makes many assumptions that aren't valid in all situations. More specifically, they aren't valid in *MY* situation.
So here's my LAN with a mail hub.
Looks like you need to use something like msmtp Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany
Lars Müller said the following on 12/09/2011 12:31 PM:
On Fri, Dec 09, 2011 at 12:22:08PM -0500, Anton Aylward wrote:
Lars Müller said the following on 12/09/2011 11:18 AM: [ 8< ]
As both exim and postfix offer a sendmail compatible commandline interface who cares?
While that's true, it makes many assumptions that aren't valid in all situations. More specifically, they aren't valid in *MY* situation.
So here's my LAN with a mail hub.
Looks like you need to use something like msmtp
Yes, thank you. msmtp is very similar to esmtp, both are minimalist and lightweight. Its hard to choose between them without looking "under the hood" at the code. Mind you, using netcat or socket as a proxy -- wrapper script required -- would work as well. -- For ages, a deadly conflict has been waged between a few brave men and women of thought and genius upon the one side, and the great ignorant religious mass on the other. This is the war between Science and Faith. The few have appealed to reason, to honor, to law, to freedom, to the known, and to happiness here in this world. The many have appealed to prejudice, to fear, to miracle, to slavery, to the unknown, and to misery hereafter. The few have said "Think" The many have said "Believe!" --Robert Ingersoll (Gods) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Lars Müller wrote:
Opps, looks like I'm a loser and have to create a /etc/fetchmailrc file. I expect you have one. Place it a copy of it at /etc/fetchmailrc and try again.
If you'd read my previous posts, you'd know I already have one that's worked well for years. To recap, the problem is with 12.1 & systemd, I have to manually start it, whereas in previous systems, I was able to start it with either System Services or kick it off with a line in after.local. Neither of those methods work with systemd. The after.local does not appear to run. If I try to start in System Services, I get an undefined error. My computer is currently booted with systemv and fetchmail started right up with the after.local script. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Fri, Dec 09, 2011 at 04:01:27PM -0500, James Knott wrote:
Lars Müller wrote:
Opps, looks like I'm a loser and have to create a /etc/fetchmailrc file. I expect you have one. Place it a copy of it at /etc/fetchmailrc and try again.
If you'd read my previous posts, you'd know I already have one that's worked well for years.
Yes, as soon as you use sysvinit. Therefore please file a bug report for the systemd case. Please reference this thread with a pointer to the archive at http://lists.openSUSE.org/opensuse/ Thanks. Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany
James Knott said the following on 12/09/2011 10:56 AM:
Anton Aylward wrote:
I run fetchmail on a seperate machine, a mail hub, so this isn't going to be an issue for me until that gets upgraded.
But here are my thoughts.
Unlike my Fedora box, openSuse seems to want you to use Postix or ... what is it, 'exim'?
Check if postfix service is running:
sudo systemctl status postfix.service
Try cloning that, but make it dependent on Postfix - obviously:-)
I have postfix running, by following the instructions posted earlier. It's fetchmail that I need to run, in order to get my mail from my ISP's POP server.
Yes, I understand that. If you don't want to run fetchmail from CRON or something then what I'm suggesting is that you use the way Postfix is started under SystemD to create the necessary entry to run Fetchmail. Create a clone: copy the Postfix SystemD entry to one named fetchmail.service (or whatever is suitable) and edit its contents to start up fetchmail instead of postfix. Fetchmail will, of course, be dependent on Postfix already have started, which will in turn be dependent on networking already have started, and so on. -- "If I must write the truth, I am disposed to avoid every assembly of bishops; for of no synod have I seen a profitable end, but rather an addition to than a diminution of evils; for the love of strife and the thirst for superiority are beyond the power of words to express." -- Father Gregory Nazianzen, 381 AD -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Fri, Dec 09, 2011 at 01:15:43PM -0500, Anton Aylward wrote: [ 8< ]
If you don't want to run fetchmail from CRON or something then what I'm suggesting is that you use the way Postfix is started under SystemD to create the necessary entry to run Fetchmail.
Why shouldn't he? Let us try to keep stuff simple stupid (KISS). :)
Create a clone: copy the Postfix SystemD entry to one named fetchmail.service (or whatever is suitable) and edit its contents to start up fetchmail instead of postfix.
Even that's not needed as there is a fetchmail service defined in /etc/init.d/ as soon as the fetchmail package gets installed. And _all_ services from /etc/init.d/ are also considered by systemd. "Why doen't anyone speak about this?" Read http://lists.opensuse.org/opensuse/2011-12/msg00620.html Looks more like nobody likes to listen. ;) Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany
Lars Müller said the following on 12/09/2011 01:35 PM:
On Fri, Dec 09, 2011 at 01:15:43PM -0500, Anton Aylward wrote: [ 8< ]
Why shouldn't he? Let us try to keep stuff simple stupid (KISS). :)
I really don't know why he shouldn't; I do. But I *DID* say "if". Personally I run a lot of stuff form CRON using @BOOT But then I'm still using 11.4 :-)
Even that's not needed as there is a fetchmail service defined in /etc/init.d/ as soon as the fetchmail package gets installed.
And _all_ services from /etc/init.d/ are also considered by systemd.
In which case why isn't his fetchmail service starting? That's what this thread was originally about, wasn't it?
"Why doen't anyone speak about this?"
Read http://lists.opensuse.org/opensuse/2011-12/msg00620.html
Looks more like nobody likes to listen. ;)
Please read http://lists.opensuse.org/opensuse/2011-12/msg00605.html Which is what I responding to. I gather from what Cristian is saying that he *does* have the fetchmail package installed but that systemd is *not* picking up on the init script. Or maybe it is ... and the script is failing. Anyways, there's always CRON, as I suggested.-- Don't interfere with anything in the Constitution. That must be maintained, for it is the only safeguard of our liberties. --Abraham Lincoln -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Fri, Dec 09, 2011 at 01:58:02PM -0500, Anton Aylward wrote:
Lars Müller said the following on 12/09/2011 01:35 PM: [ 8< ]
Even that's not needed as there is a fetchmail service defined in /etc/init.d/ as soon as the fetchmail package gets installed.
And _all_ services from /etc/init.d/ are also considered by systemd.
In which case why isn't his fetchmail service starting? That's what this thread was originally about, wasn't it?
No, he started multiple threads. This one and http://lists.opensuse.org/opensuse/2011-12/msg00130.html
"Why doen't anyone speak about this?"
Read http://lists.opensuse.org/opensuse/2011-12/msg00620.html
Looks more like nobody likes to listen. ;)
Please read http://lists.opensuse.org/opensuse/2011-12/msg00605.html Which is what I responding to.
I gather from what Cristian is saying that he *does* have the fetchmail package installed but that systemd is *not* picking up on the init script.
Or maybe it is ... and the script is failing.
With your 'maybe' you summarize my overall impression very well. :)
Anyways, there's always CRON, as I suggested.
And there might be one or two Mail User Agents (MUAs) our there which might be able to handle mail boxes too. Big, big maybe. ;) Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany
Anton Aylward wrote:
Create a clone: copy the Postfix SystemD entry to one named fetchmail.service (or whatever is suitable) and edit its contents to start up fetchmail instead of postfix.
You mean copy from /etc/systemd/system/multi-user.target.wants/postfix.service? I wouldn't know where to start modifying that. Of course, one has to ask why isn't there something similar for fetchmail in /lib/systemd/system/postfix.service? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott said the following on 12/09/2011 04:16 PM:
Anton Aylward wrote:
Create a clone: copy the Postfix SystemD entry to one named fetchmail.service (or whatever is suitable) and edit its contents to start up fetchmail instead of postfix. You mean copy from /etc/systemd/system/multi-user.target.wants/postfix.service?
I wouldn't know where to start modifying that.
Not having a copy, not running 12.1, neither do I, but given a copy I could probably make some sensible guesses and experiment a bit. Guessing ... It probably needs to go in ..../multi-user.target.wants/ like postfix.service Guessing some more ... There's probably a line like After=network.target which you'll want for fetchmail, but you might want to add something such as After=postfix.target since you want postfix to be up before you run fetchmail :-) Guessing again, there's probably something like [Service] Type=forking ExecStart=/usr/sbin/postfix -c /etc/postfix start ExecStop=/usr/sbin/postfix -c /etc/postfix stop And you want to replace those relevant lines with something like ExecStart=/usr/bin/fetchmail -f /etc/fetchmailrc ExecStop=/usr/bin/fetchmail -q Of course this is all guesswork that I dreamt up after read the SystemD documentation. I could be quite wrong and I don't have a 12.1 system to experiment with. You are welcome to experiment and report back :-) -- Security is like a box of chocolates: everyone thinks they want it, then they bite down and realize it's not the flavor they were expecting. -- Andy Scoggins, Sat, 5 Aug 2006 20:58:17 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
El sáb 10 dic 2011 10:49:48 CLST, Anton Aylward escribió:
Guessing some more ...
There's probably a line like
After=network.target
which you'll want for fetchmail, but you might want to add something such as
After=postfix.target
Nope, he needs After=mail-transfer-agent.target -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Cristian Rodríguez said the following on 12/10/2011 03:10 PM:
El sáb 10 dic 2011 10:49:48 CLST, Anton Aylward escribió:
Guessing some more ...
There's probably a line like
After=network.target
which you'll want for fetchmail, but you might want to add something such as
After=postfix.target
Nope, he needs After=mail-transfer-agent.target
Ah right, well I was guessing. What does that contain, activate, do? How does it work? What role does it play? Is it something that starts postfix? After all, postfix *is* a "mail transfer agent". -- recursion (n): See recursion. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 10/12/11 17:28, Anton Aylward wrote:
What does that contain, activate, do? How does it work? What role does it play?
See systemd.special(7)
Is it something that starts postfix?
Nope, it will tell systemd to start fetchmail after whatever MTA is configured. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Cristian Rodríguez said the following on 12/10/2011 03:46 PM:
On 10/12/11 17:28, Anton Aylward wrote:
What does that contain, activate, do? How does it work? What role does it play?
See systemd.special(7)
I did but it doesn't adequately explain how this works in this instance.
Is it something that starts postfix?
Nope, it will tell systemd to start fetchmail after whatever MTA is configured.
Could you explain that, the logic, flow of control or whatever. If you think its not of general interest in helping people understand how SystemD works, then we can take this off-list. -- Far away across the field The tolling of the iron bell Calls the faithful to their knees To hear the softly spoken magic spells. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 10/12/11 18:30, Anton Aylward wrote:
Is it something that starts postfix?
Nope, it will tell systemd to start fetchmail after whatever MTA is configured.
Could you explain that, the logic, flow of control or whatever. If you think its not of general interest in helping people understand how SystemD works, then we can take this off-list.
Sorry, I only know a little more than what the documentation tells me, fcrozat probably has more knowledge than me. ;) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2011/12/07 05:41 (GMT-0800) JAMES KNOTT composed:
I recently installed openSUSE 12.1 on a system that ran well for years with 11.0 and earlier versions. There are a couple of problems.
1) It will not boot directly from the hard drive. I have to boot the install DVD and let it boot from the hard drive. If I try to boot from the hard drive, it stops after all the PCI IRQs are listed. Grub is configured to boot from the boot partition, which is sda1, 100 MB ext2.
I've seen the openSUSE installer remove the bootable flag from all primary partitions in the past. Maybe this happened to you. To boot from sda1 either something must chainload to it (e.g. DVD), or the bootable flag must be set on sda1 (1 bit in the MBR partition table; a simple process in any partitioning tool, & YaST). -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Felix Miata wrote:
On 2011/12/07 05:41 (GMT-0800) JAMES KNOTT composed:
I recently installed openSUSE 12.1 on a system that ran well for years with 11.0 and earlier versions. There are a couple of problems.
1) It will not boot directly from the hard drive. I have to boot the install DVD and let it boot from the hard drive. If I try to boot from the hard drive, it stops after all the PCI IRQs are listed. Grub is configured to boot from the boot partition, which is sda1, 100 MB ext2.
I've seen the openSUSE installer remove the bootable flag from all primary partitions in the past. Maybe this happened to you. To boot from sda1 either something must chainload to it (e.g. DVD), or the bootable flag must be set on sda1 (1 bit in the MBR partition table; a simple process in any partitioning tool, & YaST).
I don't see that in Yast Partitioner, but fdisk shows that partition as bootable. Also, Boot Loader Options shows "Set active Flag in Partition Table for Boot Partition" is selected. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
JAMES KNOTT wrote:
1) It will not boot directly from the hard drive. I have to boot the install DVD and let it boot from the hard drive. If I try to boot from the hard drive, it stops after all the PCI IRQs are listed. Grub is configured to boot from the boot partition, which is sda1, 100 MB ext2.
Bug #736108 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (7)
-
Anton Aylward -
Cristian Rodríguez -
Felix Miata -
JAMES KNOTT -
James Knott
-
John Andersen -
Lars Müller