[Evergreen] we can haz openssl ?
Dear list, seeing that there have been some recent evergreen 13.1 updates (apache, mozilla cert packages) - will we get an openssl update fixing the recently surfaced upstream issues? I'd happily test a bit if there's a testing repo to pick from. best regards Patrick ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
[Evergreen] Logspam: Cannot ad dependency job for unit udev.service
Dear list, as already discussed in May, ever since the 13.1 systemd update then, we regularly get these in our system logs: systemd[1]: Cannot add dependency job for unit udev.service, ignoring: Unit udev.service failed to load: No such file or directory. As I'm finally looking at newer suse versions (tumbleweed), and still see these messages all over the place on my 13.1 systems, I had another look + compared with tumbleweed - and apparently the "solution" is very simple: ln -s systemd-udevd.service /usr/lib/systemd/system/udev.service systemctl daemon-reload Now I don't think we'll get further package updates for 13.1 - but maybe this helps somebody else with that annoyance. best regards Patrick ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
Re: [Evergreen] Where is the Python repository
ftp://ftp.halifax.rwth-aachen.de/opensuse/repositories/devel%3A/languages%3A/python/openSUSE_13.1/ still seems to exist. Grab it while it lasts... On Wed, Jun 29, 2016 at 4:29 PM, Xaver Gerster wrote: > As a follow up to my last mail to this list on 06/16/2016, it seems that now > also the Python repository > > http://download.opensuse.org/repositories/devel:/languages:/python/openSUSE_13.1/ > > has been removed, moreover connecting to its mirror at gwdg via yast seems > broken. Is there any other replacement for this repo? > > ___ > Evergreen mailing list > Evergreen@lists.rosenauer.org > http://lists.rosenauer.org/mailman/listinfo/evergreen ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
Re: [Evergreen] YARSUP - 70-persistent-net.rules
> The old trick of creating the file empty, does not work any more - upon > reboot it is filled again with fresh information. This works as a permanent stop: ln -s /dev/null /etc/udev/rules.d/70-persistent-net.rules hope this helps somebody Patrick ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
[Evergreen] YARSUP - 70-persistent-net.rules
Dear readers, lest it surprises you, too, here's Yet Another Recent Systemd Update Surprise: for a long time, I've been spared the dreaded ethX renumbering when moving hard disks from server to server and/or switching MAC addresses / motherboards around. Today I noticed that after the last round of systemd updates for 13.1, it rears its ugly head again. The old trick of creating the file empty, does not work any more - upon reboot it is filled again with fresh information. I did not notice this before because as an additional surprise, whatever creates the file, creates it empty in my VMs (which I test restarted and which often change their MAC addresses...) But today I cloned a host config to some new machines, and then it hit... Probably nothing that will change - but you might want to examine your practise and/or change your automation accordingly. best regards Patrick ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
Re: [Evergreen] Can you help me with a bugzilla that was closed as invalid because it is about 13.1?
On Fri, May 20, 2016 at 1:47 PM, Carlos E. R. wrote: > Well, now they have removed all the libreoffice repos for 13.1. :-( Last update was late in January, anyway. I wouldn't blame anybody for that, really. The evergreen "promise" never did cover all the various extra repositories, AFAIK. I've been running local mirrors of the repositories for some years now, and use them for all installs and updates, so it's not a big issue to me. best regards Patrick ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
Re: [Evergreen] apache systemd notify related log message
Bug opened: https://bugzilla.opensuse.org/show_bug.cgi ?id=980663[1] [1] https://bugzilla.opensuse.org/show_bug.cgi ?id=980663 ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
Re: [Evergreen] lots of systemd log messages when starting up and stopping user sessions
Thanks Per for the LogLevel hint! Just tested, works. Instead of modifying /etc/systemd/user.conf I opted for creating a user@.service dropin that overrides ExecStart, like this: HOST:~ # cat /etc/systemd/system/user@.service.d/notice.conf [Service] ExecStart= ExecStart=-/usr/lib/systemd/systemd --user --log-level=notice (that way I can just install that snippet from my own automatically installed local-workaround-systemd rpm package :) best regards Patrick ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
[Evergreen] lots of systemd log messages when starting up and stopping user sessions
And another one with latest systemd on 13.1: triggered by cronjobs running as some normal user, my logs now "constantly" contain the list of messages shown below. That was not the case with earlier systemd packages, even earlier 210 ones. I already have some other rsyslog filters for similar stuff, but the amount of different messages here, makes me reluctant to go down the fiter-it-away route further... Maybe somebody knows the root cause + could make it go away? :) best regards Patrick 2016-05-12T15:20:01.128336+02:00 HOSTNAME systemd: pam_unix(systemd-user:session): session opened for user wwwrun by (uid=0) 2016-05-12T15:20:01.134843+02:00 HOSTNAME systemd[14381]: Starting Paths. 2016-05-12T15:20:01.134858+02:00 HOSTNAME systemd[14381]: Reached target Paths. 2016-05-12T15:20:01.134868+02:00 HOSTNAME systemd[14381]: Starting Timers. 2016-05-12T15:20:01.134877+02:00 HOSTNAME systemd[14381]: Reached target Timers. 2016-05-12T15:20:01.134886+02:00 HOSTNAME systemd[14381]: Starting Sockets. 2016-05-12T15:20:01.134895+02:00 HOSTNAME systemd[14381]: Reached target Sockets. 2016-05-12T15:20:01.134903+02:00 HOSTNAME systemd[14381]: Starting Basic System. 2016-05-12T15:20:01.134912+02:00 HOSTNAME systemd[14381]: Reached target Basic System. 2016-05-12T15:20:01.134920+02:00 HOSTNAME systemd[14381]: Starting Default. 2016-05-12T15:20:01.134928+02:00 HOSTNAME systemd[14381]: Reached target Default. 2016-05-12T15:20:01.134935+02:00 HOSTNAME systemd[14381]: Startup finished in 3ms. 2016-05-12T16:28:01.503991+02:00 HOSTNAME systemd[14381]: Stopping Default. 2016-05-12T16:28:01.504004+02:00 HOSTNAME systemd[14381]: Stopped target Default. 2016-05-12T16:28:01.504013+02:00 HOSTNAME systemd[14381]: Stopping Basic System. 2016-05-12T16:28:01.504021+02:00 HOSTNAME systemd[14381]: Stopped target Basic System. 2016-05-12T16:28:01.504029+02:00 HOSTNAME systemd[14381]: Stopping Paths. 2016-05-12T16:28:01.504037+02:00 HOSTNAME systemd[14381]: Stopped target Paths. 2016-05-12T16:28:01.504045+02:00 HOSTNAME systemd[14381]: Stopping Timers. 2016-05-12T16:28:01.504052+02:00 HOSTNAME systemd[14381]: Stopped target Timers. 2016-05-12T16:28:01.504060+02:00 HOSTNAME systemd[14381]: Stopping Sockets. 2016-05-12T16:28:01.504067+02:00 HOSTNAME systemd[14381]: Stopped target Sockets. 2016-05-12T16:28:01.504075+02:00 HOSTNAME systemd[14381]: Starting Shutdown. 2016-05-12T16:28:01.505073+02:00 HOSTNAME systemd[14381]: Reached target Shutdown. 2016-05-12T16:28:01.505087+02:00 HOSTNAME systemd[14381]: Starting Exit the Session... 2016-05-12T16:28:01.505647+02:00 HOSTNAME systemd[14381]: Received SIGRTMIN+24 from PID 16015 (kill). 2016-05-12T16:28:01.507403+02:00 HOSTNAME systemd: pam_unix(systemd-user:session): session closed for user wwwrun ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
[Evergreen] apache systemd notify related log message
With the latest systemd etc. updates for 13.1 on my production webservers, I started to get these messages, several times a day: 2016-05-12T13:13:01.494327+02:00 HOSTNAME systemd[1]: apache2.service: Got notification message from PID 14342, but reception only permitted for main PID 1621 Adding "NotifyAccess=all" to apache2.service [Service] section (done locally through a dropin at the moment), seems to fix the symptom. Maybe that could be put into apache2.service in a future package update? best regards Patrick ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
[Evergreen] systemd user instance error message logged
After the latest systemd updates for 13.1, I regularly (two or three times a day) get the following log message on my production web servers: 2016-05-12T18:35:01.094994+02:00 HOSTNAME systemd: pam_unix(systemd-user:session): session opened for user wwwrun by (uid=0) 2016-05-12T18:35:01.097557+02:00 HOSTNAME systemd[26074]: Trying to run as user instance, but $XDG_RUNTIME_DIR is not set. The symtom fits something in systemd's github, with this PR integrated as a fix: https://github.com/systemd/systemd/pull/265/files Maybe that could be cherry picked? best regards Patrick ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
Re: [Evergreen] Can you help me with a bugzilla that was closed as invalid because it is about 13.1?
On Monday 02 May 2016 16:12:03 Carlos E. R. wrote: > Hi, > > I reported it last november, against LibreOffice ir repo 4.3. It has > been closed now becasue they say that they don't keep that repo. > > So I reopen it against repo 5.0, and again they close it as invalid > because 13.1 is out of maintenance. > > Absurd! The bug is not present in any other distro, it is just a missing > pacakge from the repo and should be easy to solve. Jup, experienced that too - we solved it locally by enabling both the 4.3 libreoffice repo, where these packages are still present, and the 5.0 repo. > I'm starting to think that they will close any bug I report because its > me. I reported a few weeks back something else, it was refused > unpolitely (solve it yourself if you want), then I saw an update that > covered what I had reported :-( Don't worry. I had the same experience (regarding a systemd bug report, after the 210 upgrade fiasco, there are still several of these pending). I stopped perusing bugzilla, and go on baking my own workarounds for now. My time is too short for begging in bug reports. best regards Patrick ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
Re: [Evergreen] Something broken with systemd or udev after the last update
On Fri, Apr 22, 2016 at 1:17 PM, Carlos E. R. wrote: > <3.4> 2016-04-22 13:13:02 Telcontar systemd 1 - - Cannot add dependency job > for unit udev.service, ignoring: Unit udev.service failed to load: No such > file or directory. I'm seeing this, too. Seems to be benign. Patrick ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
[Evergreen] after systemd 210 update, abandoned scope units, related to cron, bunch up
Hi list, I'd like to bring https://bugzilla.novell.com/show_bug.cgi?id=968629 to somebodies attention :) Since the systemd-210 update, on pretty much all systems where I have somewhat high frequency cronjobs running, more and more "abandoned scope units" hang around, as can be easily seen by running "systemctl | fgrep abandon". Occasionally, but a lot more rarely, there is /var/log/warn logspam, too, with messages from pam_systemd(crond:session) regarding "Failed to create session". I'd primarily like to ask whether somebody else here is seeing these symptoms. Of course, ideas regarding fixes are welcome, too :) best regards Patrick ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
Re: [Evergreen] after systemd 210 update, abandoned scope units, related to cron, bunch up
On Fri, Mar 18, 2016 at 8:11 PM, Carlos E. R. wrote: >> >> I'd like to bring https://bugzilla.novell.com/show_bug.cgi?id=968629 to >> somebodies attention :) > > Telcontar:~ # systemctl | fgrep abandon > session-1252.scope loaded active abandoned Session 1252 of user news Thank you for the confirmation! So it is not caused by some peculiarity in the setup that I run. That was my main concern. Would you be so kind to add your observation to that bug report? > There was another update to systemd to correct problems in the previous > systemd update: > > systemd-210-43.1.x86_64 > > I skipped the previous update. I have both 210-40 and 210-43 running on serveral systems; this issue affects both versions (but none of the the systems I still have on 208) best regards Patrick ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
Re: [Evergreen] upgraded my 13.1 desktop, now fails to start (sistemad dependency, claims an nfs drive wasn't mounted).
On Wednesday 16 March 2016 10:16:22 Carlos E. R. wrote: > On 2016-03-16 09:05, Per Jessen wrote: > > I updated my 13.1 office desktop last week, I saw somebody mention a > > new 3.12 kernel. On start-up, it now claims one of two NFS drives > > couldn't be mounted, although in fact they were both mounted. This > > caused postfix and X not to be started. I commented out of the mounts > > in /etc/fstab and rebooted, now it worked. > > I have an nfs mount, but it is done manually, not on boot, and there is no > issue :-? I also ran into this issue, some weeks ago. See http://bugzilla.suse.com/show_bug.cgi?id=968042 It is pretty much analyzed. /etc/init.d/xdm /etc/init.d/ntp and /usr/lib/systemd/system/postfix.service all have dependencies on remote-fs which they would better not have. Just updated that bug report with the workarounds I use to cope with the issue. best regards Patrick ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
Re: [Evergreen] 13.1 kernel update to 3.12 (SLES 12 SP1 level) ready for test
I noticed an issue that somebody might want to look into (or not). On our production kvm virtual machines, we really run a self built kernel provided by the kvm host system; the installed kernel in the virtual machine is dormant. A long time ago I tried to uninstall kernel-default, but was forced by dependencies to install another kernel-*. Finally I arrived at having kernel-vanilla installed on all the VMs. Now, when updating (zypper dup) with the 3.12 update, zypper tells me that in addition to kernel-vanilla, kernel-pae needs to be installed. I don't even have kernel-pae in my repo mirrors, because I exclude all the non-x86_64 stuff there. I can workaround this with "zypper in kernel-default -kernel-vanilla", after that, the kernel-pae is no longer required. Maybe I'll have a close look at the dependencies, and build myself an empty kernel-dummy RPM. Any hints on what dependencies such a package would need to declare (so that the published kernel-* packages would no longer be required?) best regards Patrick ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
Re: [Evergreen] 13.1 kernel update to 3.12 (SLES 12 SP1 level) ready for test
On Wednesday 02 March 2016 11:27:13 Marcus Meissner wrote: > > > > > > The 3.12 kernel version upgrade prepared by Michal is ready for testing: > > > > > > http://download.opensuse.org/repositories/openSUSE:/Maintenance:/4624/op > > > enSUSE_13.1_Update/ > Have other people tried it in the meantime? Tested today on some AMD based desktops, and a Lenovo T410 laptop. Everything fine there. > I want to avoid the same troubles we had with systemd. Had? best regards Patrick ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
Re: [Evergreen] Fwd: [security-announce] Todays openssl release - "DROWN" CVE-2016-0800 and "Cachebleed"
On Wed, Mar 2, 2016 at 7:58 AM, Michal Kubecek wrote: > This is surprising as current evergreen 11.4 openssl update (version > 1.0.1p-68.2) does present exactly the same version (0x1000110f) which > was one of the reasons why I did cherry pick CVE related fixes from > 1.0.1 branch since 1.0.1p instead of simply upgrading to 1.0.1s. Thanks for the explanation. All is well (see my other mail) Just to be sure - this is what I see now with zypper -s search regarding installed stuff: i | home_mkubecek_branches_Evergreen_Maintained_openssl | patch | 1| noarch | Evergreen 11.4 Test i | libopenssl-devel| patch | 5761 | noarch | openSUSE 11.4 Update i | libopenssl-devel| patch | 5634 | noarch | openSUSE 11.4 Update i | libopenssl-devel| patch | 5178 | noarch | openSUSE 11.4 Update i | libopenssl-devel| patch | 4669 | noarch | openSUSE 11.4 Update i | libopenssl1_0_0 | package| 1.0.1p-71.1 | x86_64 | Evergreen 11.4 Test i | openssl | package| 1.0.1p-71.1 | x86_64 | Evergreen 11.4 Test Is that patch at the top okay? What does that do? Testing artefact? best regards Patrick ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
Re: [Evergreen] Fwd: [security-announce] Todays openssl release - "DROWN" CVE-2016-0800 and "Cachebleed"
> http://download.opensuse.org/repositories/home:/mkubecek:/branches:/Evergreen_Maintained:/openssl/openSUSE_Evergreen_11.4/ >> Installing: openssh-5.8p1-4.1 [done] ARGH. I'm stupid. Forget that. I copied the normal evergreen .repo file and changed the baseurl only, so I had two repo files with the same _names_ - and zypper decided to ignore the normal update repo - i.e. that ssh was from the ancient OSS repo. After fixing that the upgrade went fine, the VM is rebooted with your newer openssl, and I'll have a closer look at its operation to see whether there are funny noises in the logs or so. best regards Patrick ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
Re: [Evergreen] Fwd: [security-announce] Todays openssl release - "DROWN" CVE-2016-0800 and "Cachebleed"
On Wed, Mar 2, 2016 at 7:29 AM, Patrick Schaaf wrote: > On Tue, Mar 1, 2016 at 11:49 PM, Michal Kubecek wrote: >> http://download.opensuse.org/repositories/home:/mkubecek:/branches:/Evergreen_Maintained:/openssl/openSUSE_Evergreen_11.4/ > > First observation, upon updating (together with glibc, openssh and > other stuff of the last few days), I see this; > > Installing: openssh-5.8p1-4.1 [done] > OpenSSL version mismatch. Built against 103f, you have 1000110f > > But it's not only on upgrade; any call to ssh gives that output. Clarification: gives that output and DOES NOT make the ssh connection. ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
Re: [Evergreen] Fwd: [security-announce] Todays openssl release - "DROWN" CVE-2016-0800 and "Cachebleed"
On Tue, Mar 1, 2016 at 11:49 PM, Michal Kubecek wrote: > http://download.opensuse.org/repositories/home:/mkubecek:/branches:/Evergreen_Maintained:/openssl/openSUSE_Evergreen_11.4/ I'm going to test that on a VM which makes outgoing SSL connections (PHP/curl) all through the day. First observation, upon updating (together with glibc, openssh and other stuff of the last few days), I see this; Installing: openssh-5.8p1-4.1 [done] Additional rpm output: Updating /etc/sysconfig/ssh... OpenSSL version mismatch. Built against 103f, you have 1000110f But it's not only on upgrade; any call to ssh gives that output. Aborting best regards Patrick ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
Re: [Evergreen] incomplete glibc update, missing debuginfo
Hurray for the glibc updates! And thanks for even making them available for 11.4 evergreen :) Very very much appreciated - I'd otherwise have to re-setup 10 normally-safe-but-DNS- arg... VMs over the weekend, in addition to the normal update round. best regards Patrick "Procrastes" Schaaf ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
Re: [Evergreen] FYI: systemd-210-40 dependency issue
Blush... Sorry for the noise, that issue was my own fault. For reasons that escape me I had 12 month old locks on the systemd packages. best regards Patrick On Wednesday 17 February 2016 08:57:35 Patrick Schaaf wrote: > FYI this list, just opened this bug report: > > https://bugzilla.opensuse.org/show_bug.cgi?id=967007 > > Does anybody else see this? > > best regards > Patrick > > awe:~ # zypper up systemd > Loading repository data... > Reading installed packages... > Resolving package dependencies... > > Problem: nothing provides this-is-only-for-build-envs needed by systemd- > mini-210-40.1.x86_64 > Solution 1: Following actions will be done: > do not forbid installation of systemd-210-40.1.x86_64[repo-update] > do not keep systemd-208-23.3.x86_64 installed > Solution 2: do not ask to install a solvable providing systemd.x86_64 = > 210-40.1 > Solution 3: break systemd-mini-210-40.1.x86_64 by ignoring some of its > dependencies > > Choose from above solutions by number or cancel [1/2/3/c] (c): c ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
[Evergreen] FYI: systemd-210-40 dependency issue
FYI this list, just opened this bug report: https://bugzilla.opensuse.org/show_bug.cgi?id=967007 Does anybody else see this? best regards Patrick awe:~ # zypper up systemd Loading repository data... Reading installed packages... Resolving package dependencies... Problem: nothing provides this-is-only-for-build-envs needed by systemd- mini-210-40.1.x86_64 Solution 1: Following actions will be done: do not forbid installation of systemd-210-40.1.x86_64[repo-update] do not keep systemd-208-23.3.x86_64 installed Solution 2: do not ask to install a solvable providing systemd.x86_64 = 210-40.1 Solution 3: break systemd-mini-210-40.1.x86_64 by ignoring some of its dependencies Choose from above solutions by number or cancel [1/2/3/c] (c): c ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
Re: [Evergreen] New Installation 13.1 possible
On Friday 12 February 2016 11:08:11 Fitl, Matthias wrote: > Hi All, > > as we do still have a lot of servers running with version 13.1 installed. > Therefor I would appreciate it to install this version on our new servers. > This leads to the following questions: > - Will the updates after the installation from the DVD still work? I do not > have a computer to test this upfront at the moment and the planned > installation will be done on some computers in parallel. That generally works, we're doing that each week to reinstall laptops and desktops, using the original DVD, and an autoyast setup with post install scripts that add in the usual repos including the normal update repo, then running an unattended "zypper dup". Keeps working like a charm. (apart from the fact that currently the recent systemd 210 update breaks stuff...) best regards Patrick ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
[Evergreen] chrome 48 warning under 13.1
Maybe interesting for this list: the chrome 48 stable update, released today, started to announce that future updates wouldn't be published for "this version of linux": I started a help forum thread on the topic here (sorry, in Gernan); https://productforums.google.com/forum/#!msg/chrome-de/PbiDsl_6Nqs/jRwcEnVnCAAJ Maybe somebody with contacts at google could try to explain 13.1 evergreen to them? best regards Patrick ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
Re: [Evergreen] evergreen 11.4 openssh update
> An update is already on its way: > > https://build.opensuse.org/request/show/353884 Something is amiss there. https://build.opensuse.org/package/show/openSUSE:Evergreen:11.4/openssh shows "disabled" for both architectures. And there is no updated published at http://download.opensuse.org/repositories/openSUSE:/Evergreen:/11.4/standard/ best regards Patrick ___ Evergreen mailing list Evergreen@lists.rosenauer.org http://lists.rosenauer.org/mailman/listinfo/evergreen
