At Samstag, 7. August 2010 23:07 Guus Snijders wrote:
In that case, try:
lsof | grep DEL
Note the spaces before and after DEL.
After checking it again, i noted that lsof uses caps for the type, so we
can drop the -i from grep.
This idea is better and now i have to wait for an update
At Samstag, 7. August 2010 23:07 Guus Snijders wrote:
In that case, try:
lsof | grep DEL
Okay, with the update of util-linux-ng checking of the deleted files makes
sense
because a lot of files use /lib/libuuid.so.1.3.0. I create this MINI script for
this:
# cat
At Samstag, 7. August 2010 01:26 Guus Snijders wrote:
Well, you certainly do have a point; finding out which apps are using
the updated libraries etc would be nice.
Here is a example of the output and what it is behind:
http://www.kriyayoga.com/love_blog/post.php/1207
How more i search in
On Sat, Aug 7, 2010 at 3:31 PM, Loui Chang louipc@gmail.com wrote:
On Sat 07 Aug 2010 01:26 +0200, Guus Snijders wrote:
HTH, HAND
What?
HTH[1] HAND[2]
[1] http://www.acronymfinder.com/HtH.html
[2] http://www.acronymfinder.com/HAND.html
On Sat, Aug 7, 2010 at 9:04 PM, Gary Wright wrigg...@gmail.com wrote:
On Sat, Aug 7, 2010 at 3:31 PM, Loui Chang louipc@gmail.com wrote:
On Sat 07 Aug 2010 01:26 +0200, Guus Snijders wrote:
HTH, HAND
What?
HTH[1] HAND[2]
[1] http://www.acronymfinder.com/HtH.html
[2]
On Sat 07 Aug 2010 20:04 -0600, Gary Wright wrote:
On Sat, Aug 7, 2010 at 3:31 PM, Loui Chang louipc@gmail.com wrote:
On Sat 07 Aug 2010 01:26 +0200, Guus Snijders wrote:
HTH, HAND
What?
HTH[1] HAND[2]
[1] http://www.acronymfinder.com/HtH.html
[2]
On 04-08-10 06:51, Attila wrote:
At Dienstag, 3. August 2010 22:35 Heiko Baums wrote:
[...]
Before i saw this feature with the warning in zypper i would say here
yes too but now i found this very useful because in the case of gui
apps or the gui itself it is not even clear for me what for
Am Wed, 04 Aug 2010 07:14 +0200
schrieb Attila vodoo0...@sonnenkinder.org:
Only for the stats: In the case of updating packages Yast, and im
suprised that you use this more than zypper, don't touch changed
config files because opensuse, and every other rpm basesd
distribution, do the same as
Hi,
On Wednesday 04 Aug 2010 at 06:22 Andreas Radke wrote:
You seem to want to use a distribution made safe for less skilled
users. Why do you keep wasting our time suggesting to make Arch
something it's not meant to be???
I don't think that David necessarily does want this, and I hope no one
Am Wed, 4 Aug 2010 09:22:41 +0100
schrieb Peter Lewis p...@muddygoat.org:
WARNING: Constructive part of the post!! :-)
If you think you need a list of packages to remember where you
should interact, go on and create one your own.
Absolutely, why not? If someone really wants to implement
On Wed, Aug 4, 2010 at 04:07, Andreas Radke a.ra...@arcor.de wrote:
Am Wed, 4 Aug 2010 09:22:41 +0100
schrieb Peter Lewis p...@muddygoat.org:
WARNING: Constructive part of the post!! :-)
If you think you need a list of packages to remember where you
should interact, go on and create one
On 08/02/2010 11:59 PM, Nicolas D wrote:
On Tuesday 03 August 2010 06:52:45 J. W. Birdsong wrote:
Great point; but we could at least mention **Restart Dovecot with
#/etc/rc.d/dovecot restart** (or some such msg) in the dovecot.install
file.Because we know EVERYONE reads the pacman msg(s)
On Tue, 03 Aug 2010 01:00:09 -0500
David C. Rankin drankina...@suddenlinkmail.com wrote:
Well sometimes the stupid ones among us don't always catch
that dovecot is being updated when it is one of 73+ updates that take
place. But we 'do' always catch the failure to copy to sent --
later
On Tue, Aug 3, 2010 at 08:52, Dieter Plaetinck die...@plaetinck.be wrote:
On Tue, 03 Aug 2010 01:00:09 -0500
David C. Rankin drankina...@suddenlinkmail.com wrote:
Well sometimes the stupid ones among us don't always catch
that dovecot is being updated when it is one of 73+ updates that
On Tue, 2010-08-03 at 01:00 -0500, David C. Rankin wrote:
Well sometimes the stupid ones among us don't always catch
that dovecot is
being updated when it is one of 73+ updates that take place. But we
'do' always
catch the failure to copy to sent -- later :p
Seriously,
On Mon, 2010-08-02 at 22:39 -0600, Tavian Barnes wrote:
Imagine the story with a different daemon: SSH. You ssh into your
box, su, and pacman -Syu. Halfway through the upgrade, openssh gets
updated, which automatically restarts the server, which SIGHUPs
pacman, which is left in an
On Tuesday 03 Aug 2010 at 09:28 Magnus Therning wrote:
No useless little 1-line notes only ment for braindead users.. i
only want to see what i need to see.
I doubt I'm as knowledgeable on Linux systems as you, so I'd rather
like seeing a bit more messages than you need to see.
I have to
On 3 August 2010 03:04, Jan de Groot j...@jgc.homeip.net wrote:
On Mon, 2010-08-02 at 22:39 -0600, Tavian Barnes wrote:
Imagine the story with a different daemon: SSH. You ssh into your
box, su, and pacman -Syu. Halfway through the upgrade, openssh gets
updated, which automatically restarts
At Dienstag, 3. August 2010 06:39 Tavian Barnes wrote:
Because of KISS? Pacman is a package manager, not a system administration
tool.
This has nothing to do with package manager or not because dpkg or rpm can do
this without a problem.
Imagine the story with a different daemon: SSH. You
At Dienstag, 3. August 2010 08:00 David C. Rankin wrote:
Well sometimes the stupid ones among us don't always catch that
dovecot is
being updated when it is one of 73+ updates that take place. But we 'do'
always
catch the failure to copy to sent -- later :p
If the count of updates
At Dienstag, 3. August 2010 11:14 Peter Lewis wrote:
I have to admit that the recent dovecot update caught me out too for a few
minutes, until I realised that I'd had no new email for an eerie amount of
time.
This is not nice no question but how will you solve changes in the config file
Okay, i recognized that i wrote too much under this little thread so set it on
read if this is too much for you.-)
The best compromise what i have seen is what zypper (package management tool
for
opensuse) do in a case if libs or a daemon get changed.
After upgrading in such a case you get a
Am Tue, 03 Aug 2010 21:40:20 +0200
schrieb Attila vodoo0...@sonnenkinder.org:
Okay, i recognized that i wrote too much under this little thread so
set it on read if this is too much for you.-)
...
I must admit, that I didn't read this completely.
It's so simple and every Linux user should
On Tue, Aug 03, 2010 at 10:35:02PM +0200, Heiko Baums wrote:
It's so simple and every Linux user should or must know this. If a
daemon or any other software is updated it must be restarted either to
use the new version or to get it working if the running version broken
by the update. And the
On 03-08-2010 21:35, Heiko Baums wrote:
Am Tue, 03 Aug 2010 21:40:20 +0200
schrieb Attilavodoo0...@sonnenkinder.org:
It's so simple and every Linux user should or must know this. If a
daemon or any other software is updated it must be restarted either to
use the new version or to get it working
Am Tue, 3 Aug 2010 22:48:48 +0200
schrieb f...@kokkinizita.net:
Well, that depends. If a user is upgrading a package X explicitly then
he/she is probably anticipating the consequences, and has prepared for
them. If X is updated as a side effect that could be different, and a
warning would be
On 08/03/2010 04:14 AM, Peter Lewis wrote:
With a particular package, you've no idea which category this falls into.
Sure, you could apply the safest approach of always restarting everything
that's upgraded, but that's not always practical. IMO it would be nice to have
short indicators when
At Dienstag, 3. August 2010 22:35 Heiko Baums wrote:
That's a common and necessary task of a Linux admin which doesn't need
and in my opinion shouldn't be done by the package manager, because the
package manager can't decide which config files I need or want to
adjust and when I can and want
Am Wed, 04 Aug 2010 00:06:53 -0500
schrieb David C. Rankin drankina...@suddenlinkmail.com:
On 08/03/2010 04:14 AM, Peter Lewis wrote:
With a particular package, you've no idea which category this falls
into. Sure, you could apply the safest approach of always
restarting everything that's
At Dienstag, 3. August 2010 22:59 Mario Figueiredo wrote:
An argument can be made that this approach makes a rolling release less
attractive to users who have invested heavily in the supported
repositories. I heard this much just recently from a former Arch user;
The possibility of an an
At Dienstag, 3. August 2010 23:50 Heiko Baums wrote:
I hadn't had any post-update maintenance nightmares yet. Well, not
nightmares. I want to know what is done and what happens on my system.
Otherwise I would recommend a different distro. But to be honest I had
a lot more post-update
Guys,
Sending mail from my local server resulted in errors could not copy sent mail
to 'sent' on servername? Checking the mail logs, I found this:
snip
Aug 2 17:15:03 nirvana dovecot: imap-login: Fatal: Dovecot version mismatch:
Master is v1.2.12, login is v1.2.13 (if you don't care, set
On 2 August 2010 22:00, David C. Rankin drankina...@suddenlinkmail.com wrote:
Guys,
Sending mail from my local server resulted in errors could not copy
sent mail to 'sent' on servername? Checking the mail logs, I found this:
snip
Aug 2 17:15:03 nirvana dovecot: imap-login: Fatal:
On 08/02/10 at 10:39pm, Tavian Barnes wrote:
On 2 August 2010 22:00, David C. Rankin drankina...@suddenlinkmail.com
wrote:
Guys,
Sending mail from my local server resulted in errors could not copy
sent mail to 'sent' on servername? Checking the mail logs, I found this:
snip
On Tuesday 03 August 2010 06:52:45 J. W. Birdsong wrote:
Great point; but we could at least mention **Restart Dovecot with
#/etc/rc.d/dovecot restart** (or some such msg) in the dovecot.install
file.Because we know EVERYONE reads the pacman msg(s) after an
install. Regardless I think
You can restart openssh without being kicked off.
Tavian Barnes taviana...@gmail.com wrote:
On 2 August 2010 22:00, David C. Rankin drankina...@suddenlinkmail.com wrote:
Guys,
Sending mail from my local server resulted in errors could not copy
sent mail to 'sent' on servername?
On Mon, 2010-08-02 at 23:00 -0500, David C. Rankin wrote:
Guys,
Sending mail from my local server resulted in errors could not copy
sent mail
to 'sent' on servername? Checking the mail logs, I found this:
snip
Aug 2 17:15:03 nirvana dovecot: imap-login: Fatal: Dovecot version
On 08/02/2010 11:39 PM, Tavian Barnes wrote:
Because of KISS? Pacman is a package manager, not a system administration tool.
Imagine the story with a different daemon: SSH. You ssh into your
box, su, and pacman -Syu. Halfway through the upgrade, openssh gets
updated, which automatically
38 matches
Mail list logo
