On 02/19/2016 09:44 PM, Brendan McKenna wrote:
Hi,
Actually, that message: "No appenders..." means that what you're missing is not Log4J itself, but the configuration for it -- typically a file called either "log4j.properties" or "log4j2.xml". If you're not interested in seeing the log output of the program, you can just ignore the messages.
It refuses to start. The thing is that it works perfectly with Java from Sun on another install.
Otherwise, you can try putting the following into a file called "log4j.properties" and add the directory it's in to the classpath (the -cp option you're already specifying):
log4j.rootLogger=WARN, stdout
log4j.appender.stdout=org.apache.log4j.ConsoleAppender log4j.appender.stdout.layout=org.apache.log4j.PatternLayout
The above will cause the messages to appear on stdout.
Well, now the program simply does not start, without any error message. The message was a red herring. File log4j.properties saved cer@Gestor:~/Moria/Gigaset/cridmanager> java -cp cridmanager-1.4.3.jar net.sourceforge.cridremote.RemoteControlView cer@Gestor:~/Moria/Gigaset/cridmanager> I guess I have to install the JRE. which fails :-? Gestor:/data/storage_c/repositorios_zypp/LocalRPMs # rpm --install jre-8u66-linux-x64.rpm Unpacking JAR files... plugin.jar... javaws.jar... deploy.jar... rt.jar... jsse.jar... charsets.jar... localedata.jar... jfxrt.jar... /var/tmp/rpm-tmp.QSj6nc: line 638: /usr/sbin/alternatives: No such file or directory warning: %post(jre1.8.0_66-1.8.0_66-fcs.x86_64) scriptlet failed, exit status 127 Gestor:/data/storage_c/repositorios_zypp/LocalRPMs # It wants "/usr/sbin/alternatives", which does not exist. :-? I don't remember how I solved this previously. I'll think about this later. -- Cheers / Saludos, Carlos E. R. (from openSUSE Leap 42.1 x86_64 (test)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org