imagination I'm afraid. 😀
Ok, what I really mean is that it shouldn't be failing consistently.
> If I were you I'd be looking at how often it fails compared to how often
> it is run. Are there files left behind in /var/log for every invocation
> for example.
Ok, that is ha
On Fri, Oct 25, 2024 at 4:00 PM Andy Smith wrote:
> However, if popularity-contest experiences a problem during submit then
> it does leave behind a file named like /var/log/popularity-contest.12345
> (and possibly another with .gpg on the end) where "12345" was the
> pro
;m afraid. 😀
> I don't know how else I could look into why popularity-contest
> consistently fails.
If I were you I'd be looking at how often it fails compared to how often
it is run. Are there files left behind in /var/log for every invocation
for example.
I'd probably a
On 2024-10-25, Andy Smith wrote:
> On Fri, Oct 25, 2024 at 03:54:58PM -0300, Bruno Schneider wrote:
>> I noticed that I have hundreds of files whose names start with
>> "popularity-contest" in /var/log. They don't even seem to be logs.
>> They seem to be dat
Hi,
On Fri, Oct 25, 2024 at 03:54:58PM -0300, Bruno Schneider wrote:
> I noticed that I have hundreds of files whose names start with
> "popularity-contest" in /var/log. They don't even seem to be logs.
> They seem to be data that popularity-contest sends away.
popularity
I noticed that I have hundreds of files whose names start with
"popularity-contest" in /var/log. They don't even seem to be logs.
They seem to be data that popularity-contest sends away.
Has anyone else noticed this? Is this a bug? It seems they are in the
wrong place or, at l
ode 0755
$Umask 0022
#
# Where to place spool and state files
#
$WorkDirectory /var/spool/rsyslog
#
# Include all config files in /etc/rsyslog.d/
#
$IncludeConfig /etc/rsyslog.d/*.conf
###
RULES
###
#
# Log anything besides private authentication messages to a
atch to work
> properly.
rsyslogd.conf controls what logfiles rsyslogd would generate:
*.* -/var/log/syslog
auth,authpriv.* /var/log/auth.log
cron.* /var/log/cron.log
daemon.*,local7.* -/var/log/daemon.log
kern.* -/var/lo
On Tue, 21 Nov 2023, John Covici wrote:
> hmmm, I looked at the release notes, but it does not say how to
> restore the old behavior, it just says many files are no longer
> necessary and lists them. I am using logwatch and that program seems
> to be effected, I would be OK, if I could get logwat
eb John Covici:
> > > Hi. I am using bookworm with latest updates and /var/log/syslog is
> > > empty, even though rsyslog is runniing. I am also using logwatch and
> > > not getting at least some responses I should get such as fail2ban.
> > > These may be sepa
Am 21.11.2023 um 05:15:24 Uhr schrieb John Covici:
> hmmm, I looked at the release notes, but it does not say how to
> restore the old behavior, it just says many files are no longer
> necessary and lists them.
Please post you syslog configuration.
:35 -0500,
Christoph Brinkhaus wrote:
>
> [1 ]
> Am Mon, Nov 20, 2023 at 05:01:50PM -0500 schrieb John Covici:
> > Hi. I am using bookworm with latest updates and /var/log/syslog is
> > empty, even though rsyslog is runniing. I am also using logwatch and
> > not gettin
Am Mon, Nov 20, 2023 at 05:01:50PM -0500 schrieb John Covici:
> Hi. I am using bookworm with latest updates and /var/log/syslog is
> empty, even though rsyslog is runniing. I am also using logwatch and
> not getting at least some responses I should get such as fail2ban.
> These may
Hi. I am using bookworm with latest updates and /var/log/syslog is
empty, even though rsyslog is runniing. I am also using logwatch and
not getting at least some responses I should get such as fail2ban.
These may be separate problems, but any help on those would be
appreciated. I saw a previous
On Sat, Jul 15, 2023 at 1:09 PM David Mehler wrote:
>
> [...]
>
> "2. "I noticed that when I change UsePAM yes to UsePAM no then this
> issue is resolved."
>
> BINGO! I flipped that UsePAM setting to no and the problem has gone away.
If you need a datapoint about UsePAM... I've been setting it
On Sat 15 Jul 2023, at 17:52, David Mehler wrote:
[...]
> Regarding the original issue of the systemd upgrade and the invalid
> attributes [...] here is the output that I've got:
>
[...]
> Cannot set file attributes for '/var/log/journal', maybe due to
> incompati
d (on the ssh server machine)
also affected by authentication delays? This apparently suggests a
PAM issue."
In answer yes su on the ssh machine also has these delays. It is
looking like a pam issue.
"1. "I found that PAM was reading the file /var/log/btmp, which had
become
On Sat 15 Jul 2023, at 13:09, Gareth Evans wrote:
>
> 2. "I noticed that when I change UsePAM yes to UsePAM no then this
> issue is resolved."
>
> There may be security (or other) issues with (2).
See, for example:
https://unix.stackexchange.com/questions/673153/sshd-what-are-the-practical-e
u ssh from the other machine? Don't
forget to specify target port (with -p1234)
If PAM-related, then answers at the above link suggest:
1. "I found that PAM was reading the file /var/log/btmp, which had become huge
as a result of people trying to brute-force my server. This was lead
> On 12 Jul 2023, at 15:12, David Mehler wrote:
>
> Hello,
>
> I'm running Debian 12 on a vps. I just upgraded it and am now
> apparently running the latest systemd version 252.12-1. I saw an error
> about invalid attributes on /var/log/journal then it said ignorin
Hello,
I'm running Debian 12 on a vps. I just upgraded it and am now
apparently running the latest systemd version 252.12-1. I saw an error
about invalid attributes on /var/log/journal then it said ignoring.
I've seen others with this error but only in reference as far as I can
tell to
* 2022-04-21 10:08:04+0800, Henrik S. wrote:
> The dir /var/log/journal/ on my debian host increases quite quickly.
> why this happens? Do you know how to suppress it?
User can control log sizes with /etc/systemd/journald.conf file but
systemd manages them automatically quite intelligently
On Thu, Apr 21 2022 at 10:08:04 AM, Henrik S wrote:
> The dir /var/log/journal/ on my debian host increases quite quickly.
> why this happens? Do you know how to suppress it?
>
That's the storage for the logs maintained by journald. You can manage
these logs by editin
The dir /var/log/journal/ on my debian host increases quite quickly.
why this happens? Do you know how to suppress it?
Thanks.
On Mi, 29 sep 21, 07:05:37, pe...@easthope.ca wrote:
> From: Greg Wooledge
> Date: Tue, 28 Sep 2021 13:41:05 -0400
> > What does it look like?
> >
> > ls -ld / /var /var/log /var/log/journal
>
> root@joule:/# ls -ld / /var /var/log
> drwxr-xr-x 18 peter
t;> > > What does it look like?
>> > >
>> > > ls -ld / /var /var/log /var/log/journal
>> >
>> > root@joule:/# ls -ld / /var /var/log
>> > drwxr-xr-x 18 peter peter 4096 Sep 27 18:00 /
>> > drwxr-xr-x 11 root root 4096 Nov
On Wed, Sep 29, 2021 at 10:35:35PM -0500, David Wright wrote:
> Would it be sensible for the message to actually mention ownership,
> or can it apply to very different circumstances (beyond permissions,
> that is)? I've failed to find any other cause, but see a lot of
> people messing up their owne
; > Date: Tue, 28 Sep 2021 13:41:05 -0400
> > > > What does it look like?
> > > >
> > > > ls -ld / /var /var/log /var/log/journal
> > >
> > > root@joule:/# ls -ld / /var /var/log
> > > drwxr-xr-x 18 peter peter 4096 Sep 27 18:00 /
&g
On Wed 29 Sep 2021 at 16:46:14 (-0400), Greg Wooledge wrote:
> On Wed, Sep 29, 2021 at 07:05:37AM -0700, pe...@easthope.ca wrote:
> > From: Greg Wooledge
> > Date: Tue, 28 Sep 2021 13:41:05 -0400
> > > What does it look like?
> > >
> > &g
On Wed, 29 Sep 2021 08:01:00 -0700
pe...@easthope.ca wrote:
> root@joule:~# cat /etc/apt/sources.list
> #deb http://mirror.it.ubc.ca/debian/ bullseye main
> deb http://mirror.it.ubc.ca/debian/ bullseye main contrib non-free
> deb-src http://mirror.it.ubc.ca/debian/ bullseye main contrib non-fr
On Wed, Sep 29, 2021 at 02:35:10PM -0700, pe...@easthope.ca wrote:
> I can't explain why / was owned by me. According to the above it
> happened in the release upgrade two days ago.
No, that's not what that timestamp says. The timestamp in "ls -ld"
is the modification time (mtime) on the direct
-ld / /var /etc /usr /var/lib /var/log
drwxr-xr-x 18 peter peter 4096 Sep 27 18:00 /
drwxr-xr-x 132 root root 12288 Sep 29 09:34 /etc
drwxr-xr-x 14 root root 4096 Nov 11 2020 /usr
drwxr-xr-x 11 root root 4096 Nov 3 2020 /var
drwxr-xr-x 50 root root 4096 Sep 27 19:28 /var/lib
drw
On Wed, Sep 29, 2021 at 07:05:37AM -0700, pe...@easthope.ca wrote:
> From: Greg Wooledge
> Date: Tue, 28 Sep 2021 13:41:05 -0400
> > What does it look like?
> >
> > ls -ld / /var /var/log /var/log/journal
>
> root@joule:/# ls -ld / /var /var/log
> drwx
From: Nils
Date: Tue, 28 Sep 2021 17:16:30 +
> Are you sure you still need these journals?
I don't know.
> ... my way to work around it would be to just delete those logs.
Did that and rebooted. System behaviour is unchanged.
plymouth-label was the last package reported unconfigu
From: Greg Wooledge
Date: Tue, 28 Sep 2021 13:41:05 -0400
> What does it look like?
>
> ls -ld / /var /var/log /var/log/journal
root@joule:/# ls -ld / /var /var/log
drwxr-xr-x 18 peter peter 4096 Sep 27 18:00 /
drwxr-xr-x 11 root root 4096 Nov 3 2020 /var
drwxr-xr-x 10 r
same
post-inst scripts again, and produce the same errors again.
2) With systemd in a possibly messed-up state, rebooting is risky.
I would focus on fixing the underlying issue, starting with looking at
the things that it complained about.
ls -ld / /var /var/log /var/log/journal
On Tue, Sep 28, 2021 at 08:55:59AM -0700, pe...@easthope.ca wrote:
> Hi,
> Here the upgrade was completed except for the problem indicated in the
> following transcript.
>
> This page appears relevant.
> https://manpages.debian.org/stretch/systemd/systemd-journald.service.8.en.
On Tue, Sep 28, 2021 at 08:55:59AM -0700, pe...@easthope.ca wrote:
> Hi,
> Here the upgrade was completed except for the problem indicated in the
> following transcript.
>
> This page appears relevant.
> https://manpages.debian.org/stretch/systemd/systemd-journald.service.8.en.
Tuxifan
Am 28. September 2021 17:55:59 MESZ schrieb pe...@easthope.ca:
>Hi,
>Here the upgrade was completed except for the problem indicated in the
>following transcript.
>
>This page appears relevant.
>https://manpages.debian.org/stretch/systemd/systemd-journald.service.8.en.html
>
&
Hi,
Here the upgrade was completed except for the problem indicated in the
following transcript.
This page appears relevant.
https://manpages.debian.org/stretch/systemd/systemd-journald.service.8.en.html
/var/log/journal exists here.
The command "systemd-tmpfiles --create --prefix /va
I think this is some kind of parsing bug from the response from solr.
The number of pairs of errors returned is the same number of hits
received during the search. So if I do a search with 7 results turned
up, I get 7 pairs of errors.
Fixed with the following:
1) simplified config file by re
The bug I patched also threw a similar kind of error. See
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970692. But this
error is cropping up for every user on the system. A google search
turns up nothing on a uid other than '0'.
I don't know if this is another debian issue or a misconfig
I'm running debian bullseye. I've had issues running solr on debian in
the past due to some kind of bug. I was able to get solr working with
dovecot by upgrading the os.
After the upgrade, everything works perfectly fine and the search
feature in my client using solr now works. However, I get
Hi David
> Sent: Friday, June 04, 2021 at 10:27 AM
> From: "David Wright"
> To: debian-user@lists.debian.org
> Subject: Re: Unexplained freezes and crashes, nothing in /var/log/messages
>
> It's just a home-grown program that's started from .xsession.
>
On Fri 04 Jun 2021 at 02:05:52 (+0200), Stella Ashburne wrote:
>
> > Sent: Friday, June 04, 2021 at 5:12 AM
> > From: "David Wright"
> >
> > My own monitoring program logs the temperature (and battery)
> > every six seconds.
> >
> I'm curious: what's the name of your monitoring program? Is it ava
Hi David
> Sent: Friday, June 04, 2021 at 5:12 AM
> From: "David Wright"
> To: debian-user@lists.debian.org
> Subject: Re: Unexplained freezes and crashes, nothing in /var/log/messages
>
>
> My own monitoring program logs the temperature (and battery)
> every
On Thu 03 Jun 2021 at 18:34:41 (+0100), Tixy wrote:
> On Thu, 2021-06-03 at 12:19 -0400, Polyna-Maude Racicot-Summerside wrote:
> > On 2021-06-03 11:27 a.m., Marc Auslander wrote:
> > > On 6/3/2021 10:20 AM, Ottavio Caruso wrote:
> > > > On 03/06/2021 09:09, Polyna-Maude Racicot-Summerside wrote:
>
On Thu, 2021-06-03 at 12:19 -0400, Polyna-Maude Racicot-Summerside wrote:
> Hi,
>
> On 2021-06-03 11:27 a.m., Marc Auslander wrote:
> > On 6/3/2021 10:20 AM, Ottavio Caruso wrote:
> > > On 03/06/2021 09:09, Polyna-Maude Racicot-Summerside wrote:
> > > I check the temperature regularly with sensors
Hi,
On 2021-06-03 11:27 a.m., Marc Auslander wrote:
> On 6/3/2021 10:20 AM, Ottavio Caruso wrote:
>> On 03/06/2021 09:09, Polyna-Maude Racicot-Summerside wrote:
>> I check the temperature regularly with sensors and it's usually
>> between 42 and 52 C.
>>
>>
>> Problem is I can't check the temperat
On 6/3/2021 10:20 AM, Ottavio Caruso wrote:
On 03/06/2021 09:09, Polyna-Maude Racicot-Summerside wrote:
I check the temperature regularly with sensors and it's usually between
42 and 52 C.
Problem is I can't check the temperature while it's freezing.
You might run a background job that keep
Hi,
On 2021-06-03 4:17 a.m., Andrei POPESCU wrote:
> On Jo, 03 iun 21, 08:51:06, Ottavio Caruso wrote:
>>
>> $ sudo inxi -FzCDMm
>> System:
>> Host: e130 Kernel: 4.19.0-8-amd64 x86_64 bits: 64 Desktop: Cinnamon 4.4.8
>> Distro: LMDE 4 Debbie
>
> Can you reproduce the issue on Debian?
>
> Do
On Jo, 03 iun 21, 08:51:06, Ottavio Caruso wrote:
>
> $ sudo inxi -FzCDMm
> System:
> Host: e130 Kernel: 4.19.0-8-amd64 x86_64 bits: 64 Desktop: Cinnamon 4.4.8
> Distro: LMDE 4 Debbie
Can you reproduce the issue on Debian?
Do CapsLock / NumLed or similar LEDs react (provided there are any)?
When you say "it freeze".
How long have you waited before "pulling the plug" or considering other
way of powering off ?
Have you checked the temperature of your CPU after leaving it running
for a while. Laptop end up with lot of dirt inside and this is not good
for thermal conductivity. So they te
On Jo, 03 iun 21, 07:49:32, Ottavio Caruso wrote:
> Debian Buster here. My laptop is aging and has only 4BG Ram, however that
> should be sufficient for a couple of instances of Firefox (no streaming,
> etc) and an instance of Chromium.
>
> It has happened a few times in the last few days that the
e last few days that the system
> becomes irresponsive, the screen is frozen, I can't shut X down nor go
> into text mode. I can't hear any drive activity. The only way out is
> to shut the laptop from the power button and reboot. I then check in
> /var/log/messages and there i
Hello,
On Sun, Oct 11, 2020 at 02:41:37PM -0700, pe...@easthope.ca wrote:
> All of the files and most of the directories in /var/log/ are owned
> by root. These are the exceptions.
>
> root@joule:/var/log# ls -ld {c*,ex*,s*}/
> drwxr-xr-x 2 _chrony _chrony 4096 Jul
All of the files and most of the directories in /var/log/ are owned
by root. These are the exceptions.
root@joule:/var/log# ls -ld {c*,ex*,s*}/
drwxr-xr-x 2 _chrony _chrony 4096 Jul 22 2017 chrony/
drwxr-s--- 2 Debian-exim adm 4096 Oct 11 00:00 exim4/
drwxr-xr-x 2 stunnel4
On Monday, September 28, 2020 08:42:03 AM Richard Hector wrote:
> On 29/09/20 12:40 am, rhkra...@gmail.com wrote:
> > On Monday, September 28, 2020 01:28:01 AM Richard Hector wrote:
> >> On 26/09/20 2:47 pm, David Wright wrote:
> >> > If you make yourself a member of the adm group, you can read you
On Tue 29 Sep 2020 at 01:42:03 (+1300), Richard Hector wrote:
> On 29/09/20 12:40 am, rhkra...@gmail.com wrote:
> > On Monday, September 28, 2020 01:28:01 AM Richard Hector wrote:
> >> On 26/09/20 2:47 pm, David Wright wrote:
> >> > If you make yourself a member of the adm group, you can read your
On 29/09/20 12:40 am, rhkra...@gmail.com wrote:
> On Monday, September 28, 2020 01:28:01 AM Richard Hector wrote:
>> On 26/09/20 2:47 pm, David Wright wrote:
>> > If you make yourself a member of the adm group, you can read your logs
>> > as a normal user. You'd need to type into any terminal
>> >
On Monday, September 28, 2020 01:28:01 AM Richard Hector wrote:
> On 26/09/20 2:47 pm, David Wright wrote:
> > If you make yourself a member of the adm group, you can read your logs
> > as a normal user. You'd need to type into any terminal
> >
> > $ sudo addgroup myloginname adm
> >
> > replacin
On 26/09/20 2:47 pm, David Wright wrote:
> If you make yourself a member of the adm group, you can read your logs
> as a normal user. You'd need to type into any terminal
>
> $ sudo addgroup myloginname adm
>
> replacing myloginname as appropriate, but you will need to login again
> before the ad
-C can be useful if you do something like search for
> a string in a huge file and want to interrupt it because it's
> taking too long.
>
> > Greg, I was using less.
> > What I did was:- Open a terminal by ctrl + alt + F1
> > `cd /var/log` then `ls` and I could see bo
less.
>
> >You get out of less by pressing p
No, q, not p. You get out of less with q.
But Ctrl-C can be useful if you do something like search for
a string in a huge file and want to interrupt it because it's
taking too long.
> Greg, I was using less.
> What I did was:- Open
a terminal by ctrl + alt + F1
`cd /var/log` then `ls` and I could see boot.log amongst the list of files
then I did `sudo less boot.log` and got the list of start ups.
At this point I was stuck and asked the list for help.
I was such a fool because I did not look up the man page for less.
I we
On Fri, 25 Sep 2020 at 10:40, anthony gennard wrote:
>
>
>
> On Thu, 24 Sep 2020 at 10:11, anthony gennard wrote:
>
>> Thanks very much; it will take me some time to understand your advice. I
>> will revert as soon as I can.
>>
>> On Thu, 24 Sep 2020 at 15:03, Hans wrote:
>>
>>> Am Donnerstag,
On Thu, 24 Sep 2020 at 10:11, anthony gennard wrote:
> Thanks very much; it will take me some time to understand your advice. I
> will revert as soon as I can.
>
> On Thu, 24 Sep 2020 at 15:03, Hans wrote:
>
>> Am Donnerstag, 24. September 2020, 15:45:47 CEST schrieb Greg Wooledge:
>> I believe,
Thanks very much; it will take me some time to understand your advice. I
will revert as soon as I can.
On Thu, 24 Sep 2020 at 15:03, Hans wrote:
> Am Donnerstag, 24. September 2020, 15:45:47 CEST schrieb Greg Wooledge:
> I believe, the op wants to look it as easy as possible. So I suggest
> kwri
Am Donnerstag, 24. September 2020, 15:45:47 CEST schrieb Greg Wooledge:
I believe, the op wants to look it as easy as possible. So I suggest kwrite
(if he has plasma5 aka KDE installed).
You must got the correct rights. Either you start plasma as root, then you can
just start kwrite and open the
On 9/24/2020 10:59 AM, anthony gennard wrote:
I am looking at the contents of my boot log file; when trying to get out of
the very long file I thought Ctrl + c should do it - it does not and I
cannot
find any way. I wanted to try tail and head so see how they do. Can anyone
please help me.
Also
On Thu, Sep 24, 2020 at 09:59:57AM +0100, anthony gennard wrote:
> I am looking at the contents of my boot log file; when trying to get out of
> the very long file I thought Ctrl + c should do it - it does not and I
> cannot
> find any way. I wanted to try tail and head so see how they do. Can anyo
I am looking at the contents of my boot log file; when trying to get out of
the very long file I thought Ctrl + c should do it - it does not and I
cannot
find any way. I wanted to try tail and head so see how they do. Can anyone
please help me.
Also is there any simple way to print out the last ru
t; pass the output of that into the 'aptitude purge' command.
>>>
>>>> Try:
>>>>
>>>> $ aptitude purge $(grep "2020-07-23.*.install " /var/log/dpkg.log | awk
>>>> '{ print $4 }' | tr '\n' ' ')
>
command.
>>
>>> Try:
>>>
>>> $ aptitude purge $(grep "2020-07-23.*.install " /var/log/dpkg.log | awk
>>> '{ print $4 }' | tr '\n' ' ')
>>>
>>> and see what you get.
>>
>> Turns out that
The Wanderer writes:
> On 2020-07-27 at 10:37, The Wanderer wrote:
>
>> What you want to do instead is to run this exact latter command, and
>> pass the output of that into the 'aptitude purge' command.
>
>> Try:
>>
>> $ aptitude purge $(gre
Greg Wooledge writes:
> On Mon, Jul 27, 2020 at 07:42:31PM +, Rodolfo Medina wrote:
>> Must be so because
>>
>> $ zgrep "2018.*.install " /var/log/dpkg*
>>
>> gives no output and so with 2017, 2016 and 2015, whereas for 2019 and 2020
>> th
On Mon, Jul 27, 2020 at 07:42:31PM +, Rodolfo Medina wrote:
> Must be so because
>
> $ zgrep "2018.*.install " /var/log/dpkg*
>
> gives no output and so with 2017, 2016 and 2015, whereas for 2019 and 2020
> there is output...
You can use ls -l to see the dates
3-dev:i386
>> 1.2.0-3
>> dpkg.log:2020-07-23 08:07:13 status installed libiec61883-dev:i386 1.2.0-3
>>
>> In the output there isn't any `install' item... How come...?
>
> Most likely, because your oldest logs have been removed already.
Must be so because
On Mon, Jul 27, 2020 at 07:06:47PM +, Rodolfo Medina wrote:
> Just so simple. Now, I want to know when libiec61883-dev:i386 was installed
> into my system. To do so, I did:
>
> $ zgrep libiec61883-dev:i386 dpkg.log*
> dpkg.log:2020-07-23 08:07:12 status unpacked libiec61883-dev:i386 1.2.0-3
David Wright writes:
> I don't know why you'd want to learn bash scripting at
> root's command line, but if you insist, please add -s
> after the word aptitude.
No, certainly, my fault... I just did:
$ zgrep "2020-07-23.*.install " /var/log/dpkg.log* | awk
On 2020-07-27 at 10:37, The Wanderer wrote:
> What you want to do instead is to run this exact latter command, and
> pass the output of that into the 'aptitude purge' command.
> Try:
>
> $ aptitude purge $(grep "2020-07-23.*.install " /var/log/dpkg.
92 not upgraded.
> >> Need to get 0 B of archives. After unpacking 394 kB will be freed.
> >> Do you want to continue? [Y/n/?]
> >>
> >> , so it's also important that appendix `:i386'. Now, I want to remove all
> >> tha packages I installed on
On 2020-07-27 at 10:25, Rodolfo Medina wrote:
> The Wanderer writes:
>
>> On 2020-07-27 at 09:56, Rodolfo Medina wrote:
>>> Now, I want to remove all
>>> tha packages I installed on last july 23th. To do so, I do:
>>>
>>> $ grep "2015-
i386{u}
>> libsratom-0-0:i386{u}
>> 0 packages upgraded, 0 newly installed, 4 to remove and 192 not upgraded.
>> Need to get 0 B of archives. After unpacking 394 kB will be freed.
>> Do you want to continue? [Y/n/?]
>>
>> , so it's also important t
0 B of archives. After unpacking 394 kB will be freed.
> Do you want to continue? [Y/n/?]
>
> , so it's also important that appendix `:i386'. Now, I want to remove all tha
> packages I installed on last july 23th. To do so, I do:
>
> $ grep "2015-12-19.*.insta
true:
# aptitude purge liblilv-0-0:i386
The following packages will be REMOVED:
liblilv-0-0:i386{p} libserd-0-0:i386{u} libsord-0-0:i386{u}
libsratom-0-0:i386{u}
0 packages upgraded, 0 newly installed, 4 to remove and 192 not upgraded.
Need to get 0 B of archives. After unpacking 394 kB wi
On 2020-07-27 at 08:53, Rodolfo Medina wrote:
> The Wanderer writes:
>
>> On 2020-07-27 at 08:15, Rodolfo Medina wrote:
>>> Thanks to you all. Then, e.g.,
>>>
>>> 2020-07-23 08:02:37 install liblilv-0-0:i386 0.24.2~dfsg0-2
>>>
>>> means that liblilv-0-0 has been installed or not on 2020-07-
The Wanderer writes:
> On 2020-07-27 at 08:15, Rodolfo Medina wrote:
>
>> writes:
>>
>>> On Sat, Jul 25, 2020 at 10:54:56PM +0200, Sven Joachim wrote:
>>>
>>> [...]
>>>
It's mentioned in the dpkg manpage, search for the --log option
there.
>>>
>>> :-)
>>>
>>> Thanks, that puts it
On 2020-07-27 at 08:15, Rodolfo Medina wrote:
> writes:
>
>> On Sat, Jul 25, 2020 at 10:54:56PM +0200, Sven Joachim wrote:
>>
>> [...]
>>
>>> It's mentioned in the dpkg manpage, search for the --log option
>>> there.
>>
>> :-)
>>
>> Thanks, that puts it to rest.
>>
>> As always, if everythi
On Mon, Jul 27, 2020 at 12:15:37PM +, Rodolfo Medina wrote:
> Thanks to you all. Then, e.g.,
>
> 2020-07-23 08:02:37 install liblilv-0-0:i386 0.24.2~dfsg0-2
>
> means that liblilv-0-0 has been installed or not on 2020-07-23? From dpkg
> manpage, --log option, as I understand, the field wi
writes:
> On Sat, Jul 25, 2020 at 10:54:56PM +0200, Sven Joachim wrote:
>
> [...]
>
>> It's mentioned in the dpkg manpage, search for the --log option there.
>
> :-)
>
> Thanks, that puts it to rest.
>
> As always, if everything else fails, read the instructions.
Thanks to you all. Then, e.g.,
On Sat, Jul 25, 2020 at 10:54:56PM +0200, Sven Joachim wrote:
[...]
> It's mentioned in the dpkg manpage, search for the --log option there.
:-)
Thanks, that puts it to rest.
As always, if everything else fails, read the instructions.
Cheers
-- t
signature.asc
Description: Digital signature
On 2020-07-25 16:25 -0400, The Wanderer wrote:
> On 2020-07-25 at 16:02, to...@tuxteam.de wrote:
>
>> On Sat, Jul 25, 2020 at 07:47:01PM +, Rodolfo Medina wrote:
>>
>>> Hi all...
>>>
>>> Please what do those occurrences of `' mean in /var/lo
On Sat, Jul 25, 2020 at 04:25:50PM -0400, The Wanderer wrote:
> On 2020-07-25 at 16:02, to...@tuxteam.de wrote:
>
> > On Sat, Jul 25, 2020 at 07:47:01PM +, Rodolfo Medina wrote:
> >
> >> Hi all...
> >>
> >> Please what do those occurrences
On 2020-07-25 at 16:02, to...@tuxteam.de wrote:
> On Sat, Jul 25, 2020 at 07:47:01PM +, Rodolfo Medina wrote:
>
>> Hi all...
>>
>> Please what do those occurrences of `' mean in /var/log/dpgk.log just
>> on
>> the right next to some (and some not) o
On Sat, Jul 25, 2020 at 07:47:01PM +, Rodolfo Medina wrote:
> Hi all...
>
> Please what do those occurrences of `' mean in /var/log/dpgk.log just on
> the right next to some (and some not) of packages names?
You mean like this:
2019-10-18 17:09:25 install gcc-8-base:
Hi all...
Please what do those occurrences of `' mean in /var/log/dpgk.log just on
the right next to some (and some not) of packages names?
thanks for any help
cheers
rodolfo
Colleen Keegan
; >
> > In pursuing an attempt to put dovecot to work as a local server, I
> > find my /var/log/mail.err log is being spammed once for every
> > incoming email.
> >
> > The log looks like this:
> >
> > Dec 3 10:38:34 coyote spamc[6292]: connect to spamd on
On Thursday 03 December 2015 10:50:35 Gene Heskett wrote:
> Greetings all;
>
> I am using procmail for my MTA which also attempts to run the incoming
> stuff thru some filters, like spamc/spamd.
>
> In pursuing an attempt to put dovecot to work as a local server, I
> find my
1 - 100 of 460 matches
Mail list logo
