On Sat, 2011-02-26 at 02:44 +0100, Damjan wrote: > I'm running a self compiled 2.6.38-rc6-00113-g4662db4 on my 64bit > desktop, and I get a nasty warning in dmesg complaining about capabilities. > > Is this a syslog-ng issue, or something with the package in Arch, or > maybe I need to setup some capabilities to the binary? > > syslog-ng is 3.2.2-1, the full kernel warning is below, but afaik most > important is: > Attempt to access syslog with CAP_SYS_ADMIN but no CAP_SYSLOG (deprecated). > > > > ------------[ cut here ]------------ > WARNING: at kernel/printk.c:288 do_syslog+0xc1/0x510() > Hardware name: A780GM-A > Attempt to access syslog with CAP_SYS_ADMIN but no CAP_SYSLOG (deprecated). > Modules linked in: usb_storage uas joydev usbhid hid btusb bluetooth > rfkill sp5100_tco snd_seq_dummy snd_hda_cod > ec_hdmi snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device atl1 mii > snd_pcm_oss snd_mixer_oss snd_hda_codec_i > dt floppy edac_core edac_mce_amd ohci_hcd ehci_hcd i2c_piix4 usbcore > snd_hda_intel snd_hda_codec snd_hwdep snd_p > cm snd_timer snd soundcore snd_page_alloc evdev pcspkr shpchp > pci_hotplug sg button thermal k8temp ip_tables x_t > ables fuse kvm_amd kvm powernow_k8 freq_table processor mperf ext4 > mbcache jbd2 crc16 sd_mod sr_mod cdrom pata_a > cpi ahci libahci pata_atiixp libata scsi_mod radeon ttm drm_kms_helper > drm i2c_algo_bit i2c_core cfbcopyarea cfb > imgblt cfbfillrect > Pid: 3082, comm: syslog-ng Not tainted 2.6.38-rc6-00113-g4662db4 #5 > Call Trace: > [<ffffffff81056afa>] ? warn_slowpath_common+0x7a/0xb0 > [<ffffffff81056bd1>] ? warn_slowpath_fmt+0x41/0x50 > [<ffffffff811bc154>] ? security_capable+0x24/0x30 > [<ffffffff81057db1>] ? do_syslog+0xc1/0x510 > [<ffffffff8119ca47>] ? kmsg_open+0x17/0x20 > [<ffffffff811917e3>] ? proc_reg_open+0xa3/0x190 > [<ffffffff8119ca30>] ? kmsg_open+0x0/0x20 > [<ffffffff8119ca10>] ? kmsg_release+0x0/0x20 > [<ffffffff81191740>] ? proc_reg_open+0x0/0x190 > [<ffffffff81137ac0>] ? __dentry_open+0x100/0x370 > [<ffffffff81143cbe>] ? generic_permission+0x1e/0xc0 > [<ffffffff81138d61>] ? nameidata_to_filp+0x71/0x80 > [<ffffffff81147c18>] ? finish_open+0xc8/0x1b0 > [<ffffffff81147422>] ? do_path_lookup+0x82/0x160 > [<ffffffff81148359>] ? do_filp_open+0x259/0x800 > [<ffffffff810bb270>] ? call_rcu+0x10/0x20 > [<ffffffff81154bd4>] ? alloc_fd+0xf4/0x150 > [<ffffffff8120064d>] ? strncpy_from_user+0x2d/0x40 > [<ffffffff81138dd4>] ? do_sys_open+0x64/0x110 > [<ffffffff81138e9b>] ? sys_open+0x1b/0x20 > [<ffffffff8100bdd2>] ? system_call_fastpath+0x16/0x1b > ---[ end trace 52dc0a1402a3a0af ]--- > If i recall there is an issue with .38 and syslog-ng, also check the bugtracker https://bugs.archlinux.org/task/22555 -- Jelle van der Waa
Attachment:
signature.asc
Description: This is a digitally signed message part
