Hi arKers,
KDE 4.7 has been released[1] and our packages are ready in [testing].
As you already know KDE is (slowly) moving to GIT. With this
transition some KDE module has been splitted into subprojects, and the
remaining modules should be splitted before KDE 4.8.
The result of this is that some
On Wed, Jul 27, 2011 at 9:29 AM, Renato wrote:
> On Wed, 27 Jul 2011 21:52:24 +1000
> Simon Perry wrote:
>
> > On 27/07/11, Renato wrote:
> >
> > | no, didn't know it conflicted with lastb. However, stopping it
> > doesn't | change the situtation, bad logins aren't logged
> > to /var/log/btmp. |
On 27/07/11, Renato wrote:
| sorry, I think I don't understand what you're saying, maybe my english
| isn't very good. the files /var/log/wtmp and /var/log/btmp are indeed
| present in my system
Make sure:
- Your files are 600 and are owned by root:root
- You run 'lastb' with sudo or as root
- T
On Wed, 27 Jul 2011 21:52:24 +1000
Simon Perry wrote:
> On 27/07/11, Renato wrote:
>
> | no, didn't know it conflicted with lastb. However, stopping it
> doesn't | change the situtation, bad logins aren't logged
> to /var/log/btmp. |
> | Can I configure syslog-ng to report bad login attempts?
>
On 27/07/11, Renato wrote:
| no, didn't know it conflicted with lastb. However, stopping it doesn't
| change the situtation, bad logins aren't logged to /var/log/btmp.
|
| Can I configure syslog-ng to report bad login attempts?
Dude, it's not syslog-ng.
Read the man pages, for example "man last
On Wed, 27 Jul 2011 09:37:56 +0300
Ionut Biru wrote:
> have you removed syslog-ng from DAEMONS?
>
no, didn't know it conflicted with lastb. However, stopping it doesn't
change the situtation, bad logins aren't logged to /var/log/btmp.
Can I configure syslog-ng to report bad login attempts?
c
On 27 July 2011 13:47, JL Young wrote:
> On 26/07/11 17:19, Vic Demuzere wrote:
>
>> After first booting into windows, it simply connects and stays
>> connected. Everything works fine then. Note that it always works fine
>> in windows, so it isn't a hardware problem.
>>
>> Does anyone else have th
On 26/07/11 17:19, Vic Demuzere wrote:
After first booting into windows, it simply connects and stays
connected. Everything works fine then. Note that it always works fine
in windows, so it isn't a hardware problem.
Does anyone else have this problem, or knows how to fix it?
--
v...@demuzere.b
On 27 July 2011 11:02, Benedikt Kraxner wrote:
> Hi,
>
> I had a similar problem with a different WiFi card.
> Try "ifconfig wlan0 down" before starting the network.
>
That sounds like a weird solution, never tried that! I've tried using
"ip link set dev up" before starting the network.
I can't
On 26 July 2011 23:13, David C. Rankin wrote:
> On my Toshiba laptop, I created a profile in rc.conf based on the following
> note:
>
> Install the netcfg package, create a profile under /etc/network.d (there are
> some examples, so you shouldn't have any problem), and edit /etc/rc.conf:
> add
> t
Hi,
I had a similar problem with a different WiFi card.
Try "ifconfig wlan0 down" before starting the network.
--
Benedikt
11 matches
Mail list logo
