A friend suggested just to accept the crashes and to restart the application
by a trivial loop, so I have some
( while :; do nm-applet
iiig_log lost nm-applet ## log entries from my GSM scripts
sleep 5## problem high-frequency
looping
I believe that
CRDA: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 'iw'
('iw' not found) is essential.
Cf. also the expired #1387119 with the same error message on a German
installation of Lubuntu 14.10.
--
You received this bug notification because you are a member of Ubuntu
A first line saying that I often restart NM by nm-applet seems to have
been removed from my expanded report, below heading.
Crashes seem to be accompanied with
(nm-applet:6848): GLib-CRITICAL **: Source ID 107 was not found when
attempting to remove it
as in
Public bug reported:
Sometimes I don't find any way to get it back without restarting.
(I don't like restarting because then I must re-open
at least 5 LXTerminal tabs I use in every session.)
Sometimes I even can't use WvDial anymore after certain
NetworkManager crashes, Invalid dial command,
my (rsyslog) logs *are* rotatated now. I found that /usr/sbin/anacron is
a symbolic link to /bin/true as in bug #1254614 and renamed
/usr/sbin/anacron.distrib found with bug #1254614 into
/usr/sbin/anacron. As opposed to there, this has not been undone so far.
I find the symlink in some saved
Now I have guessed (at bug 1254614) that the developers have disabled
rotating and cron jobs for live sessions *intentionally*. (And I am
sorry and annoyed about all my typos above, still wondering how I could
avoid them without a preview function here.)
--
You received this bug notification
@#5: no, bug #13854564 produces an error on `# logrotate
/etc/logrotate.conf`, while the same command works properly as expected
here.
I have now seen (guessed) that /etc/cron.daily/logrotate is not run
(status file's mtime is from running logrotate manually),
/etc/cron.daily/apport is not run
@Vinny: I have /etc/logrotate.conf as of 2014-01-22 containing:
# use the syslog group by default, since this is the owning group
# of /var/log/syslog.
su root syslog
Yet according to `find / -user syslog' and `find / -group syslog', I
have no files with owning group syslog, I have log files
Public bug reported:
(Expected: auth.log, kern.log, syslog rotated daily/weakly according
to /etd/..., actually: no rotation even after weeks; and manual forcing
may fail.)
Being concerned about the amount of GBs that a Lubuntu persistent
installation on a USB flash drive may write per day, I
weekly indeed supported extremely weakly
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to logrotate in Ubuntu.
https://bugs.launchpad.net/bugs/1385537
Title:
logrotate does not rotate logs (rsyslog)
Status in “logrotate”
aha, #1385537
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to logrotate in Ubuntu.
https://bugs.launchpad.net/bugs/1258202
Title:
recent group permissions change on /var/log cause logrotate errors
Status in “logrotate”
… and #1278193, sorry
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to logrotate in Ubuntu.
https://bugs.launchpad.net/bugs/1258202
Title:
recent group permissions change on /var/log cause logrotate errors
Status in
cf. #1258202 and #1278193 about owning group, here:
$ ls -ld /var/log
drwxrwxr-x 1 root fuse 4096 Okt 25 02:16 /var/log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to logrotate in Ubuntu.
13 matches
Mail list logo
