Re: [indiana-discuss] Why the Ys?
Hi Gilles, On Mon, 2009-05-11 at 08:35 +0200, Gilles Gravier wrote: Most of the times, when my laptop boots, before the login prompt, I get a full page of Y caracters... Anybody know the reason? And how this could be cleaned out? Could this be 6834261 y-umlaut and other noise when switching boot-graphics to text or to usb-serial console fixed in 111b or snv_114 according to the bug. cheers, tim ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
Re: [indiana-discuss] Why the Ys?
Hi! Tim Foster wrote: Hi Gilles, On Mon, 2009-05-11 at 08:35 +0200, Gilles Gravier wrote: Most of the times, when my laptop boots, before the login prompt, I get a full page of Y caracters... Anybody know the reason? And how this could be cleaned out? Could this be 6834261 y-umlaut and other noise when switching boot-graphics to text or to usb-serial console fixed in 111b or snv_114 according to the bug. Indeed... looks like it. Well... I'm running 111a... so waiting for 111b to see if it disappears. :) Thanks, Gilles ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
[indiana-discuss] syslog broken in os2008.11?
hello all, i'm unable to write with syslog from my apps: # perl -MSys::Syslog -e 'Sys::Syslog::syslog(daemon|debug, this is a better test: %d, time);' and syslog.conf: *.err;kern.notice;auth.notice /dev/sysmsg *.err;kern.debug;daemon.notice;mail.crit/var/adm/messages *.alert;kern.err;daemon.err operator *.alert root *.emerg * mail.debug ifdef(`LOGHOST', /var/log/syslog, @loghost) ifdef(`LOGHOST', , user.err/dev/sysmsg user.err/var/adm/messages user.alert `root, operator' user.emerg * ) local6.debug/var/log/sipserver.log /var/log/syslog and /var/adm/messages aren't written! the same problem appears in a non global zone. Anybody has seen the problem? this is very important thanks in advance for help, gerard ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
Re: [indiana-discuss] syslog broken in os2008.11?
solarg wrote: # perl -MSys::Syslog -e 'Sys::Syslog::syslog(daemon|debug, this is a better test: %d, time);' and syslog.conf: *.err;kern.notice;auth.notice /dev/sysmsg *.err;kern.debug;daemon.notice;mail.crit/var/adm/messages *.alert;kern.err;daemon.err operator *.alert root *.emerg * mail.debug ifdef(`LOGHOST', /var/log/syslog, @loghost) ifdef(`LOGHOST', , user.err/dev/sysmsg user.err/var/adm/messages user.alert `root, operator' user.emerg * ) local6.debug/var/log/sipserver.log /var/log/syslog and /var/adm/messages aren't written! you are writing to daemon.debug but your syslog.conf is not configured to log daemon.debug daemon.debugTABs/var/log/syslog pfexec pkill -HUP syslogd ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
Re: [indiana-discuss] TimeSlider and ZFS pools on removable media
Cindy Sounds like a good RFE. Hmm, in which category? Unfortunately there's no overview about the existing categories and what RFE/BUG should to to which category (or I did not found it yet ...) regards Bernd cindy.swearin...@sun.com wrote: Hi Bernd, I don't know how you could disable Time Slider for all the pools on removable media. Sounds like a good RFE. If you know the pool name, then you could disable like this: # zfs set com.sun:auto-snapshot=false pool-name Cindy Bernd Schemmer wrote: Hi, I've enabled the TimeSlider on my OpenSolaris 06.2009 for some but not all filesystems. That works very well for the filesystems on the local disks. But if I connect an USB disk with a zpool TimeSlider is always enabled for the filesystems in that zpool. I would like to configure TimeSlider so that it ignores all pools on removable media. Can this be configured and, if yes, how? regards Bernd -- Bernd Schemmer, Frankfurt am Main, Germany http://home.arcor.de/bnsmb/index.html M s temprano que tarde el mundo cambiar . Fidel Castro ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
Re: [indiana-discuss] syslog broken in os2008.11?
Hi-- I generally restart syslog if I make modifications to syslog.conf, like this: # svcadm restart svc:/system/system-log:default Cindy solarg wrote: hello all, i'm unable to write with syslog from my apps: # perl -MSys::Syslog -e 'Sys::Syslog::syslog(daemon|debug, this is a better test: %d, time);' and syslog.conf: *.err;kern.notice;auth.notice /dev/sysmsg *.err;kern.debug;daemon.notice;mail.crit/var/adm/messages *.alert;kern.err;daemon.err operator *.alert root *.emerg * mail.debug ifdef(`LOGHOST', /var/log/syslog, @loghost) ifdef(`LOGHOST', , user.err/dev/sysmsg user.err/var/adm/messages user.alert `root, operator' user.emerg * ) local6.debug/var/log/sipserver.log /var/log/syslog and /var/adm/messages aren't written! the same problem appears in a non global zone. Anybody has seen the problem? this is very important thanks in advance for help, gerard ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
Re: [indiana-discuss] syslog broken in os2008.11?
Oscar del Rio wrote:
solarg wrote:
# perl -MSys::Syslog -e 'Sys::Syslog::syslog(daemon|debug, this is
a better test: %d, time);'
and syslog.conf:
*.err;kern.notice;auth.notice /dev/sysmsg
*.err;kern.debug;daemon.notice;mail.crit/var/adm/messages
*.alert;kern.err;daemon.err operator
*.alert root
*.emerg *
mail.debug ifdef(`LOGHOST', /var/log/syslog,
@loghost)
ifdef(`LOGHOST', ,
user.err/dev/sysmsg
user.err/var/adm/messages
user.alert `root, operator'
user.emerg *
)
local6.debug/var/log/sipserver.log
/var/log/syslog and /var/adm/messages aren't written!
you are writing to daemon.debug but your syslog.conf is not
configured to log daemon.debug
daemon.debugTABs/var/log/syslog
FWIW I've noticed that many of the log messages which I deal with and
which used to go to user.* now go to daemon.*
Maybe this is simply the transition from dtlogin to gdm (which implies
any logging from PAM during login), but it seems to go beyond that.
I'm not sure that the default syslog.conf has evolved appropriately to
accommodate this new use of facility in the default set of daemons (note
the ifdef('LOGHOST'... clause which used to catch login errors but no
longer does).
-Bob
___
indiana-discuss mailing list
indiana-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
Re: [indiana-discuss] syslog broken in os2008.11?
Luc I. Suryo wrote: make sure the file exist, syslog does not create them. yes it exists: # ls -l /var/log/sipserver.log -rw-r--r-- 1 root root 0 May 11 13:59 /var/log/sipserver.log ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
Re: [indiana-discuss] syslog broken in os2008.11?
Oscar del Rio wrote: you are writing to daemon.debug but your syslog.conf is not configured to log daemon.debug daemon.debugTABs/var/log/syslog pfexec pkill -HUP syslogd ok, # date Mon May 11 20:38:58 CEST 2009 # perl -MSys::Syslog -e 'Sys::Syslog::syslog(daemon|notice, this is a better test: %d, time);' and syslog.conf contains: *.err;kern.debug;daemon.notice;mail.crit/var/adm/messages but: # tail /var/adm/messages ... May 11 15:58:08 catalogue3 syslogd: going down on signal 15 May 11 16:08:48 catalogue3 syslogd: going down on signal 15 May 11 17:27:53 catalogue3 syslogd: going down on signal 15 May 11 18:31:55 catalogue3 syslogd: going down on signal 15 r...@catalogue3:/usr/local/koha/lib/C4/SIP# and nothing else... anybody can test this above simple perl command in a os2008.11 zone and report if it works? thanks for help, gerard ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
Re: [indiana-discuss] syslog broken in os2008.11?
cindy.swearin...@sun.com wrote: Hi-- I generally restart syslog if I make modifications to syslog.conf, like this: # svcadm restart svc:/system/system-log:default i did it, and also rebooting the zone without success thanks for help gerard ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
Re: [indiana-discuss] syslog broken in os2008.11?
solarg wrote: anybody can test this above simple perl command in a os2008.11 zone and report if it works? very strange behaviour! if i launch syslogd in debug mode, it works: # /usr/sbin/syslogd -d main(1): Started at time Mon May 11 23:14:22 2009 hnc_init(1): hostname cache configured 2037 entry ttl:1200 getnets(1): found 1 addresses, they are: 0.0.0.0.2.2 amiloghost(1): testing 127.0.0.1.2.2 conf_init(1): I am loghost cfline(1): (*.err;kern.notice;auth.notice /dev/sysmsg) cfline(1): (*.err;kern.debug;daemon.notice;mail.crit/var/adm/messages) cfline(1): (*.alert;kern.err;daemon.err operator) cfline(1): (*.alert root) cfline(1): (*.emerg *) cfline(1): (mail.debug /var/log/syslog) cfline(1): (local6.debug /var/log/sipserver.log) syslogd: version %I% Started: Mon May 11 23:14:22 2009 Input message count: system 0, network 0 # Outputs: 7 priority = [file, facility] 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 2 2 2 2 2 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 -- 5 3 3 3 5 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 X CONSOLE: /dev/sysmsg 7 3 2 5 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 X FILE: /var/adm/messages 3 1 1 3 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 X USERS: operator 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 X USERS: root 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 X WALL: X X 7 X X X X X X X X X X X X X X X X X X X X X X FILE: /var/log/syslog X X X X X X X X X X X X X X X X X X X X X X 7 X X FILE: /var/log/sipserver.log Facilities: [00] kern: 0 [01] user: 8 [02] mail: 16 [03] daemon: 24 [04] auth: 32 [05] security: 32 [06] mark: 192 [07] syslog: 40 [08] lpr: 48 [09] news: 56 [10] uucp: 64 [11] audit: 104 [12] cron: 120 [13] local0: 128 [14] local1: 136 [15] local2: 144 [16] local3: 152 [17] local4: 160 [18] local5: 168 [19] local6: 176 [20] local7: 184 Priorities: [00] panic: 0 [01] emerg: 0 [02] alert: 1 [03] crit: 2 [04] err: 3 [05] error: 3 [06] warn: 4 [07] warning: 4 [08] notice: 5 [09] info: 6 [10] debug: 7 [11] none: 16 Per File Statistics FileTot DupsNofwd Errs --- - /dev/sysmsg 0 0 0 0 /var/adm/messages 0 0 0 0 operator0 0 0 0 root0 0 0 0 WALL0 0 0 0 /var/log/syslog 0 0 0 0 /var/log/sipserver.log 0 0 0 0 logmsg(9): msg dispatcher started sys_poll(10): sys_thread started init(1): accepting messages from local system hostname_lookup(12): hostname_lookup started set_udp_buffer(1): allocate 262144 for fd 4 init(1): accepting messages from remote net_poll(13): net_thread started init(1): syslogd: started main(1): off running net_poll(13): received empty packet from 127.0.0.1.209.156 net_poll(13): received message from 127.0.0.1.209.156 writemsg(8): Logging msg 'May 11 23:14:26 this is a better test: 1242076466 ' to FILE /var/log/sipserver.log as you see, it products the correct output (with perl -MSys::Syslog -e 'Sys::Syslog::syslog(local6|debug, this is a better test: %d, time);') but if syslogd is started by svcs, it products nothing! One difference i note is that in mode debug, pfiles pid-syslogd shows /dev/udp and this doesn't exist when started by svcadm gerard ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
Re: [indiana-discuss] syslog broken in os2008.11?
solarg wrote: as you see, it products the correct output (with perl -MSys::Syslog -e 'Sys::Syslog::syslog(local6|debug, this is a better test: %d, time);') but if syslogd is started by svcs, it products nothing! One difference i note is that in mode debug, pfiles pid-syslogd shows /dev/udp and this doesn't exist when started by svcadm % svcprop system-log | grep remote Is log_from_remote enabled? ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
[indiana-discuss] services running inside zone
I installed a native OpenSolaris zone and I see the following IP services running: TCP: IPv4 Local AddressRemote AddressSwind Send-Q Rwind Recv-QState - -- - -- --- *.* *.*0 0 49152 0 IDLE *.22 *.*0 0 49152 0 LISTEN *.111*.*0 0 49152 0 LISTEN *.* *.*0 0 49152 0 IDLE *.111*.*0 0 49152 0 LISTEN *.* *.*0 0 49152 0 IDLE TCP: IPv6 Local Address Remote Address Swind Send-Q Rwind Recv-Q State If - - - -- - -- --- - *.* *.* 0 0 49152 0 IDLE *.22 *.* 0 0 49152 0 LISTEN *.111 *.* 0 0 49152 0 LISTEN *.* *.* 0 0 49152 0 IDLE The port 111 is clearly from rpc/bind. Any reason why that is left running? I don't see why that is needed unless there is requirement for NFS or other related service. Why not leave it disabled also? Should I file a RFE for this? -- This message posted from opensolaris.org ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
Re: [indiana-discuss] syslog broken in os2008.11?
Oscar del Rio wrote: solarg wrote: as you see, it products the correct output (with perl -MSys::Syslog -e 'Sys::Syslog::syslog(local6|debug, this is a better test: %d, time);') but if syslogd is started by svcs, it products nothing! One difference i note is that in mode debug, pfiles pid-syslogd shows /dev/udp and this doesn't exist when started by svcadm % svcprop system-log | grep remote Is log_from_remote enabled? right! log_from_remote is set to false, and after setting it to true, output is ok but there is a problem still: # svcprop system-log | grep remote config/log_from_remote boolean false # svccfg -s svc:/system/system-log setprop config/log_from_remote = true # svcadm restart svc:/system/system-log (as described in the man pages) # svccfg -s system-log listprop config/log_from_remote config/log_from_remote boolean true But: # svcprop system-log | grep remote config/log_from_remote boolean false Why does it still display false!!? and about remote behaviour i'm using perl's command on the same machine, why does it need remote enabled? and why does it work in os2009.11 out of box? did they change it between releases? very thanks for your help, gerard ___ indiana-discuss mailing list indiana-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
