Re: Many systemd units do not start anymore

Am 07.02.24 um 13:07 schrieb Christoph Pleger: Hello, Am Mittwoch, dem 07.02.2024 um 12:27 +0100 schrieb Michael Biebl: Am 07.02.24 um 11:32 schrieb Christoph Pleger: Hello, systemd-time-wait-sync.service is running but has not completed. I wonder if that is https://bugs.debian.org/cgi-bin

Re: Many systemd units do not start anymore

Am 07.02.24 um 11:32 schrieb Christoph Pleger: Hello, systemd-time-wait-sync.service is running but has not completed. I wonder if that is https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940840 https://github.com/systemd/systemd/issues/14061 Which NTP service do you use? I am using

Re: Many systemd units do not start anymore

Am 05.02.24 um 21:38 schrieb Michael Biebl: This is the output of systemctl list-jobs : JOB UNIT TYPE  STATE 102 autofs.service   start waiting 82  mlocate.timer    start waiting 80  e2scrub_all.timer

Re: Many systemd units do not start anymore

This is the output of systemctl list-jobs : JOB UNIT TYPE STATE 102 autofs.service start waiting 82 mlocate.timerstart waiting 80 e2scrub_all.timerstart waiting 117 cron.service

Re: Stop packagekitd from downloading updates

In case of GNOME, you might try the following gsettings set org.gnome.software download-updates false (gnome-software used packagekitd internally) OpenPGP_signature.asc Description: OpenPGP digital signature

Re: Help ! No syslog anymore

Am 13.11.23 um 10:13 schrieb Bhasker C V: I forgot to answer the question on why I am doing this I am experimenting on a no-log system where there is no writes what-so-ever to /var/log (except for mails) or systemd journal (currently kept volatile) /tmp/ is tmpfs mounted Attached is the

Re: Help ! No syslog anymore

Am 12.11.23 um 08:18 schrieb Bhasker C V: Hi, I have tried removing PrivateTmp=no in the rsyslog service file and it still doesnt work I assume you mean PrivateTmp=yes? I  have removed the service file which I had created too. I found that when I run the daemon manually, it works well.

Re: Help ! No syslog anymore

The service file you posted is not a good idea. Please remove it again. If moving the log file out of /tmp is not an option, please run systemctl edit rsyslog.service and disable PrivateTmp via [Service] PrivateTmp=no OpenPGP_signature.asc Description: OpenPGP digital signature

Re: Bookworm: NetworkManager

I want NetworkManager to not over write /etc/resolv.conf According to the docs if dns=none is set it will not touch /etc/resolv.conf This should work, and this does work here. If not, please do file a bug report. OpenPGP_signature.asc Description: OpenPGP digital signature

Re: Bookworm: NetworkManager

Is /etc/resolv.conf a real file or a symlink? If the latter, where does it point to? Michael OpenPGP_signature.asc Description: OpenPGP digital signature

Re: Installing Gnome Desktop on Bookworm Cloud Image Fails due to netdev GID

Hi Shawn, this sounds like a bug in the cloud images. Not quite sure, why they need the netdev (system) group, but if that user is created by them, they should do so as a system user. Could you please inform the cloud image maintainers? https://wiki.debian.org/Teams/Cloud

Re: 60-serial.rules, broken

Not sure if it's fixed in Bookworm already. The upstream fix went in at v253. Bookworm is at 252.6 which doesn't exist as a tag in the upstream repo so I cannot check if the fix was backported. stable/point releases can be found in the systemd-stable repository. See

Re: Syslog/Rsyslog/Systemctl issue

Are you using SELinux or AppApparmor ? Have you tried disabling it? OpenPGP_signature Description: OpenPGP digital signature

Re: usrmerge problem on docker with upgrade

What you said about overlayfs is true and usrmerge is imho giving a rather clear error message. That said, I thought the best practice for docker containers is to throw them away and rebuild them and that upgrading containers is frowned upon? If you build / pull a new bookworm docker

Re: How to configure (aka deal with) /tmp in the best way?

while the OP had an entry for /tmp in teir /etc/fstab. Wow! AFAICT, i did not create any systemd files nor ran a generator or such. Apart from listing units, i did not interfere ... wait ... i recall using the systemctl edit command once So, what likely happened is: - You had an fstab entry

Re: usrmerge

On Sat, Oct 01, 2022 at 11:06:55AM +0100, billium wrote: Since the last update to my debian testing I am unable to install anything or upgrade. Setting up usrmerge (31) ... FATAL ERROR: Both /lib/x86_64-linux-gnu/libc.so.6 and /usr/lib/x86_64-linux-gnu/libc.so.6 exist. How did you arrive in

Re: *Now* what is starting ssh-agent?

Can you post the output of systemd-cgls OpenPGP_signature Description: OpenPGP digital signature

Re: network-manager-gnome - no primary & secondary dns possible?

Am 16.10.21 um 09:27 schrieb dude: Hello, on latest Debian 11 + MATE Desktop (it is software simplicity at it's best :) why is it not possible to set primary & secondary dns via network-manager-gnome? (only "additional dns") It is possible. Choose Method: Automatic (DHCP) addresses only

Re: exim update not responding to update-rc.d

Am 07.05.21 um 02:12 schrieb Michael Biebl: exim4 is unfortunately still SysV-only and doesn't ship a native systemd .service file. So the correct command is "update-rc.d exim4 disable" For the curious: you can run "systemctl disable exim4" as well. This will just run the

Re: exim update not responding to update-rc.d

exim4 is unfortunately still SysV-only and doesn't ship a native systemd .service file. So the correct command is "update-rc.d exim4 disable" "update-rc.d exim4 remove" will remove the symlinks in /etc/rc?.d/ but on the next package update, they will be recreated. So if you want to make this a

HEADSUP: systemd now defaults to cgroupsv2

Hi, with systemd 247.2-2, the default cgroup hierarchy has been switched to unified (i.e. cgroupv2). If you want to read more about the benefits of cgroupv2 vs cgroupv1, I would suggest [1]. In Debian, all major container tools should support cgroupv2. My special thanks go to Ryutaroh

Re: Re: Mounting /dev/shm noexec

Also related https://github.com/systemd/systemd/pull/17238#discussion_r499375614 signature.asc Description: OpenPGP digital signature

Heads up: persistent journal has been enabled in systemd

Hi, with today's upload of systemd 244.1-2 I finally enabled persistent journal by default [1]. It has been a long requested feature. The package will create a directory /var/log/journal on upgrades and new installs, which enables persistent journal in so called auto mode. If you decide, that

Re: systemd-container login as root no longer possible?

Hi https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830255 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731656 might be related. Does it help if you add pts/0 to /etc/securetty inside your buster container? Would be great if you can report back if that fixes your issue. If you want to use

Re: Unreliable systemd user service

Hi > Why is there no "the graphical session is ready" > systemd target? There is, incidentally it is named graphical-session.target :-) See man systemd.special Unfortunately, no display/session manager is hooked up yet to manage the lifetime of that target, so you can't make use of that target

Re: systemd+anacron breaks cron jobs

Am 05.12.18 um 11:35 schrieb Kamil Jońca: > So I cannot drop (ana)cron :) EOT With your specific set of requirements, you are most likely best served by cron (and anacron if your system is not continuously running). I still don't understand why you need to start your backup task as user

Re: systemd+anacron breaks cron jobs

Am 05.12.18 um 11:04 schrieb Kamil Jońca: > But 'enable-linger' starts my ALL services, which is not what I want. > I want to start only timers. Since you can only have one systemd --user instance, this is not possible. You can't have a systemd --user instance which is started during boot with

Re: systemd+anacron breaks cron jobs

Am 05.12.18 um 10:49 schrieb Michael Biebl: > Am 05.12.18 um 10:47 schrieb Kamil Jońca: >> How can I: >> 1. start services only with graphical login and > > You can't. At least not yet. Use ~/.config/autostart Some work has already been done to support graphical-

Re: systemd+anacron breaks cron jobs

Am 05.12.18 um 10:47 schrieb Kamil Jońca: > Michael Biebl writes: > >> Am 05.12.18 um 10:04 schrieb Kamil Jońca: >>> Michael Biebl writes: >> >>>>> which in turn, can break ALL your "user" units) >>>> >>>> I'd b

Re: systemd+anacron breaks cron jobs

Am 05.12.18 um 10:04 schrieb Kamil Jońca: > Michael Biebl writes: >>> which in turn, can break ALL your "user" units) >> >> I'd be interested to know, what exactly you have in mind here. I'm not >> aware of such a breakage. > > For example:

Re: systemd+anacron breaks cron jobs

Am 05.12.18 um 08:54 schrieb Kamil Jońca: > "User" task aren't started until user logs in. (You should play with > enable-linger, I haven't read the full discussion, so I missed the part that you are apparently using a user crontab. Just curious: Why are you starting the backup task via a user

Re: systemd+anacron breaks cron jobs

Am 05.12.18 um 07:41 schrieb Michael Biebl: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864213#25 > If you drop /lib/udev/rules.d/60-anacron.rules my bet is that the > problem is gone. Btw, I'd go as far and say that you can safely drop anacron these days. A lot of Debian packa

Re: systemd+anacron breaks cron jobs

> On Mon, 03 Dec 2018, Kamil Jońca wrote: >> >> Dec 03 00:23:54 alfa systemd[1]: anacron.service: State 'stop-sigterm' >> >> timed out. Killing. >> > See, someone or some script told systemd to stop anacron (or maybe to >> > stop-and-start/restart it). THIS is causing the undesired behavior. >>

Re: Starting powertop --auto-tune from systemd

Am 10.03.2018 um 18:55 schrieb Rainer Dorsch: > [Please follow-up to debian-user] > > Hello, > > I run > > /usr/bin/powertop --auto-tune > > to optimize the power consumption of my system. Running it manually works > nicely. When I try to run from systemd, I see no effect :-/ > > I followed

Re: Bug#889144: systemd 237-1: problem starting dnsmasq

Am 07.02.2018 um 22:12 schrieb Jonathan de Boyne Pollard: > Michael Biebl: > >> If other services depend on dnsmasq, please keep >> https://www.lucas-nussbaum.net/blog/?p=877 in mind >> > Please do not.  It is an erroneous conclusion based upon a faulty > analysi

Re: Embarrassing security bug in systemd

Am 07.12.2017 um 15:37 schrieb Roberto C. Sánchez: > On Thu, Dec 07, 2017 at 03:03:44AM -0600, Dave Sherohman wrote: >> >> I no longer have any non-systemd machines handy to verify this on, but >> my memory is that I have *always* been able to use halt/poweroff/reboot >> commands from the console

Re: Embarrassing security bug in systemd

Am 06.12.2017 um 23:53 schrieb Michael Lange: > Hi, > > uh, I guess you ought to have used your time to check your machine and > read some docs instead of figuring out how to best insult the debian > developers ;) > (scnr) > > On 06 Dec 2017 22:52:17 +0100 > Urs Thuermann

Re: Thunderbird no longer opens links

Am 01.12.2017 um 15:40 schrieb to...@tuxteam.de: > On Fri, Dec 01, 2017 at 03:30:50PM +0100, solitone wrote: >> On 01/12/17 15:22, Jonathan Dowland wrote: >>> AppArmor is not enabled in current >>> stable [...] > >> I have stretch, and didn't requested it manually, but was installed >> with the

Re: Missing qt5-designer in Stretch

Am 14.11.2017 um 16:48 schrieb Marc Shapiro: > On 11/14/2017 12:18 AM, Christian Seiler wrote: >> Am 2017-11-14 08:05, schrieb Marc Shapiro: >>> Am I missing something, somewhere?  Or is qt5-designer not packaged >>> for Debian? >> >> Designer for Qt5 can be found in the qttools5-dev-tools package

Re: System becomes inaccessible after upgrade of libgl1-mesa-glx to version 17.2.2-1

Am 19.10.2017 um 21:09 schrieb Simon Pepping: > The solution seems simple: > > The following packages will be REMOVED: >   libglvnd0-nvidia > The following NEW packages will be installed: >   libglvnd0" > > But how do you do that with an inaccessible system? The system can be > booted in

Re: [Pkg-utopia-maintainers] network-manager-gnome - Ethernet - Security - 802.1x - Password can't be changed

Am 19.10.2017 um 14:39 schrieb Daniel: > Hello, > > I'm using debian 9 up to date. > > Desktop Environment: Gnome > > Scenario: Where I work we connect to the network with Ethernet and > 802.1x peap authentication. Each X days passwords expire and we need > to change it. > > Problem: When I

Re: ugly fonts in thunderbird after sid upgrade

Am 16.10.2017 um 22:50 schrieb Pétur Viljamson: > I have ugly fonts in thunderbird after updating my Debian sid today. It's the latest freetype upgrade causing this for users which use subpixel antialiasing. Thunderbird needs to be updated to cope with the changes in freetype 2.8.1 see

D-Bus (Re: systemd process(es) consuming CPU when laptop lid closed)

Am 17.10.2017 um 14:49 schrieb Jimmy Johnson: >>> path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; > Michael I found it interesting that I do not have a folder /org/ .hidden > or not and that's with kde5 desktop on Stretch. Those are D-Bus path names, not file names.

Re: systemd process(es) consuming CPU when laptop lid closed

Am 16.10.2017 um 02:56 schrieb Glen B: > On 10/15/2017 10:31 AM, Michael Biebl wrote: >> Am 14.10.2017 um 21:48 schrieb Glen B: >>>295 root 20 07448 4432 3992 R 41.2 0.9 0:54.81 >>> systemd-logind >>>298 message+ 20 06260

Re: systemd process(es) consuming CPU when laptop lid closed

Am 14.10.2017 um 21:48 schrieb Glen B: > 295 root 20 07448 4432 3992 R 41.2 0.9 0:54.81 > systemd-logind > 298 message+ 20 06260 3636 3268 S 17.6 0.7 0:17.12 dbus-daemon That looks like there is a huge amount of dbus messages sent. Can you run dbus-monitor

Re: Rescue mode when root account locked

Am 20.09.2017 um 13:46 schrieb solitone: > When I boot in rescue mode, I get this message: > > Cannot open access to console, the root account is locked. See > sulogin(8) man page for more details > > When I press Enter to continue, it continues bootup in normal graphical > mode. > > Would it

Re: hibernate uses a wrong UUID

Am 10.09.2017 um 17:36 schrieb Michael Biebl: > If you "make the swap partition bigger", you most likely changed the > UUID. That's exactly what Alexander described you need to check and > update if necessary. Running "mkswap" on an existing swap partition will

Re: hibernate uses a wrong UUID

Am 10.09.2017 um 16:51 schrieb Erwan David: > Le 09/10/17 à 16:47, Alexander V. Makartsev a écrit : >> You should not use "uswsusp" anymore on recent OS releases. Hibernate >> should work "out-of-the-box" assuming swap partition is big enough. >> Remove "uswsusp", double check "/etc/fstab" swap

Re: hibernate uses a wrong UUID

Am 09.09.2017 um 18:50 schrieb Pierre Frenkiel: > I have this in /etc/initramfs-tools/conf.d/resume >     RESUME=UUID=42b1dc3e-6206-4bd5-9eb4-76e97f94cd65 > which is actually the UUID of the swap partition. > > and after pm-hibernate and reboot, I find in syslog: >    PM: Checking hibernation

Re: systemd autocompletion does not work

Am 28.07.2017 um 06:14 schrieb Kamil Jońca: > /etc/dbus-1/system.d/: > > -rw-r--r-- 1 root root 3947 Apr 29 2014 org.freedesktop.systemd-shim.conf Purge the systemd-shim package. This file from systemd-shim is

Re: systemd autocompletion does not work

Am 27.07.2017 um 19:09 schrieb Kamil Jońca: > > 1. Box with debian sid, updated frequently > 2. Recently I realized that completion of systemd units does not work, > ie. > $sudo systemd restart gives me "@" sign only. > I noticed that, at the moment of pressing tab I got in /var/log/auth.log >

Re: systemd autocompletion does not work

Am 27.07.2017 um 22:20 schrieb Kamil Jońca: > Michael Biebl <bi...@debian.org> writes: > >> Am 27.07.2017 um 19:09 schrieb Kamil Jońca: >>> >>> 1. Box with debian sid, updated frequently >>> 2. Recently I realized that completion of systemd units doe

Re: Jessie to Stretch Upgrade: Enable Predictable Network Interface Names

Am 27.07.2017 um 20:21 schrieb Patrick Flaig: > Sure, this is the content: > > cat /tmp/foo/lib/systemd/network/99-default.link Thanks Patrick. So, it seems the udev maintainer scripts detected at virtualized environment which causes the following code to be triggered:

Re: Jessie to Stretch Upgrade: Enable Predictable Network Interface Names

Am 27.07.2017 um 19:50 schrieb Patrick Flaig: > Oh my fault, 99-default.link is available, I checked the wrong folder. > The file is containing some text, saying that the machine is most likely a > virtualized guest. Can you paste the contents verbatim. -- Why is it that all of the

Re: systemd autocompletion does not work

Am 27.07.2017 um 19:09 schrieb Kamil Jońca: > > 1. Box with debian sid, updated frequently > 2. Recently I realized that completion of systemd units does not work, > ie. > $sudo systemd restart gives me "@" sign only. ... > What am I missing? The tool is called systemctl, not systemd.

Re: Jessie to Stretch Upgrade: Enable Predictable Network Interface Names

Am 27.07.2017 um 18:55 schrieb debian-li...@patschie.de: >> Am 27.07.2017 um 18:25 schrieb Michael Biebl <bi...@debian.org>: >> lsinitramfs /boot/initrd.img-$(uname -r) | grep 99-default.link >> lib/systemd/network/99-default.link > Missing Odd. Do you have that file

Re: Jessie to Stretch Upgrade: Enable Predictable Network Interface Names

Am 27.07.2017 um 18:04 schrieb debian-li...@patschie.de: > Hi Michael, > > I forgot to mention that I also recreated the initramfs: > after several tries just to update it, I deleted the initramfs and recreated > it completely. > But still the same effect. > > Is there a way to manually check

Re: Jessie to Stretch Upgrade: Enable Predictable Network Interface Names

Hi Patrick Am 27.07.2017 um 17:15 schrieb debian-li...@patschie.de: > Hi, > > I’m running into some troubles to enable the predictable network interface > names for a system upgraded from Jessie. > > What I figured out so far: > Setting net.ifnames=1 on the kernel command line doesn’t help and

Re: Hibernate in stretch

Am 18.07.2017 um 05:02 schrieb behrad eslami: > Hi > > Im installed stretch in thinkpad x260 and hibernate not work corrctly. > When poweron laptop, resume hibernated desktop and suddeny go to the > display manager and after login all application was closed > > Graphical enviroment: > i3 >

Re: systemd & postgresql - flooding system log

Am 15.07.2017 um 00:07 schrieb Don Armstrong: > This plugin is horribly designed, and runs su - $DBUSER -c [...] for its > functioning. Indeed. > It should instead just su $DBUSER -c [...]; or better yet, not actually > su to the database user, and instead run as a user which only has the >

Re: systemd & postgresql - flooding system log

Am 07.07.2017 um 16:03 schrieb Václav Ovsík: > Jul 7 15:42:35 rt2 systemd[1]: Started Session c4504 of user postgres. > Jul 7 15:42:35 rt2 systemd[1]: Started Session c4505 of user postgres. > Jul 7 15:42:35 rt2 systemd[1]: Started Session c4506 of user postgres. > Jul 7 15:42:35 rt2

Re: Superblock last write time is in the future.

Am 02.07.2017 um 17:49 schrieb Wellington Terumi Uemura: > Just to give a feedback, this doesn't work if you have a second OS like > Windows. Windows (since 7) works fine with UTC. There is a registry key you can set. -- Why is it that all of the instruments seeking intelligent life in the

Re: Stretch and network management

Am 28.06.2017 um 23:19 schrieb tony mollica: > Networkmanager out, wicdin. > > I purge both of these from the system an installed them one at a time, > network-manager first. It always connects to the wired interface but > won't act reliably with the wireless connection. I tried every which >

Re: no network after jessie -> stretch

Am 21.06.2017 um 17:53 schrieb D. R. Evans: > I just completed an upgrade to stretch on an i386 machine. > > There were no obvious showstopping errors during the install. I saw a few > "unable to delete directory; directory not empty" errors fly by, but nothing > that seemed dangerous, and the

Re: Superblock last write time is in the future.

Am 21.06.2017 um 07:43 schrieb Wellington Terumi Uemura: > RTC in local TZ: yes > > The bugreport show that this has been patched, anything else I could do > to stop running system check/clean every time I boot? I would set the system clock from LOCAL to UTC (see /etc/adjtime) -- Why is it

Re: gnome 3.22 unable to authenticate to google account

Am 13.05.2017 um 18:36 schrieb Michael Biebl: > I'll ask the release team to unblock webkit2gtk 2.14.7-1 This happened in the mean time: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862502 -- Why is it that all of the instruments seeking intelligent life in the universe are pointed a

Re: gnome 3.22 unable to authenticate to google account

Am 13.05.2017 um 00:54 schrieb andy: > hello - > > i recently upgraded my laptop from wheezy through jessie and straight > on to stretch. almost everything went much more smoothly than i had > hoped. the one glaring problem is that i am unable to re-add access to > my gmail account and google

Re: systemd: How to get suricata started at boot?

Am 03.05.2017 um 13:12 schrieb Hans: > Am Mittwoch, 3. Mai 2017, 12:38:39 CEST schrieb Dejan Jocic: >> On 03-05-17, Hans wrote: >>> Hello all, >>> > Hi Michael, high Dejan, > > this works! But I will let the bugreport open (unless, you think it can be > closed), because the maintainer might want

Re: systemd: How to get suricata started at boot?

Am 03.05.2017 um 11:11 schrieb Hans: > Hello all, > > I have installed suricata on my system, but it will not start at boot. > > When I manually start it, it is working well. > > As the document advises, I copied /lib/systemd/system/suricata.service to > /etc/systemd/system/suricata.service

Re: device name (symlink) stability

Am 25.04.2017 um 16:09 schrieb Vincent Lefevre: > Hi, > > On 2017-04-25 12:14:30 +0200, Michael Biebl wrote: >> Am 25.04.2017 um 10:53 schrieb Vincent Lefevre: > [...] >>> In particular, it is strange that all the symlinks point to sr0 >>> except cdrw, whi

Re: device name (symlink) stability

Hi Am 25.04.2017 um 10:53 schrieb Vincent Lefevre: > After a reboot of a Debian/unstable machine, I got: > > /dev/cdrw -> sr1 > > while it was > > /dev/cdrw -> sr0 [..] > Is it normal that the device names are not stable? > > In particular, it is strange that all the symlinks point to

Re: Tuning boot time of my server

Am 08.04.2017 um 21:15 schrieb Markus Grunwald: > Hello, > > just for sports, I tried to minimise the boot time of my server, which > is running systemd. I have one mayor blocker: > > % systemd-analyze blame > 10.746s srv-share-backup.mount > 10.258s nfs-kernel-server.service

Re: If Linux Is About Choice, Why Then ...

Am 05.04.2017 um 20:05 schrieb Dan Ritter: > On Wed, Apr 05, 2017 at 07:26:03PM +0200, Michael Biebl wrote: >> Am 05.04.2017 um 17:04 schrieb Dan Ritter: >>> On Wed, Apr 05, 2017 at 03:47:33PM +0100, Jonathan Dowland wrote: >>>> On Mon, Apr 03, 2017 at 05:06

Re: If Linux Is About Choice, Why Then ...

Am 05.04.2017 um 17:04 schrieb Dan Ritter: > On Wed, Apr 05, 2017 at 03:47:33PM +0100, Jonathan Dowland wrote: >> On Mon, Apr 03, 2017 at 05:06:22AM -0700, Rick Thomas wrote: >>> Aside from being insulting, this is just plain untrue. There are well over >>> 100,000 professional Linux sysadmins

Re: glade-gtk3?

Am 03.04.2017 um 17:18 schrieb Gene Heskett: > Greetings; > > My last question seemed to have been routed to /dev/null. > > Is there a time in the foreseeable future the complete glade-gtk2 version > 3.8.0 kit of gfx widgits might be updated to gtk3 compatibility? >

Re: upgraded config files in /lib/systemd/system

Am 05.03.2017 um 21:29 schrieb Michael Biebl: > Fwiw, systemctl edit (--full) foo.service can help you with that > > https://www.freedesktop.org/software/systemd/man/systemctl.html#edit%20NAME%E2%80%A6 > > This is new in stretch, jessie's systemctl doesn't have that yet. Just

Re: upgraded config files in /lib/systemd/system

Am 05.03.2017 um 20:47 schrieb Harald Dunkel: > On 02/28/17 15:23, Dominique Dumont wrote: > >> I don't understand why a change in /lib/systemd/system should trigger a >> conflict warning. > > > A unit file provided by the package maintainer might introduce new > dependencies, for example.

Re: X won't start after installing openbox

Am 27.02.2017 um 22:00 schrieb Sven Joachim: >> [38.828] (II) VESA(0): initializing int10 >> [38.829] (EE) VESA(0): Cannot read int vect > > And the vesa driver does not work either because it needs root rights > which the X server does no longer have. See >

Re: apt's cache, was Re: Debian/Stretch - network-manager ...

Am 08.02.2017 um 15:38 schrieb David Wright: > If you're worried about losing your .deb files, just copy > them (as a user) or move them (as root) anywhere else, > depending on how much storage you have. Using any of the -i > -n -u options will avoid unnecessary overwriting. Older deb files can

Re: Debian/Stretch: how to boot in text mode

Am 01.02.2017 um 21:21 schrieb Ennio-Sr: > Hi all! > > After upgrading to Stretch I'm unable to find a way to boot with no GUI. > I tried setting 'GRUB-GFXPAYLOAD_LINUX="text" in /etc/default/grub, > moving to 'K01gdm3' all 'S??gdm3' instances in /etc/rc?.d, but nothing > happens. > Any help,

Re: Is the "fjes" Kernel Module loaded on every system?

Am 24.01.2017 um 17:17 schrieb Jens Sauer: > Hey list, > > During my custom kernel configuration using "make localmodconfig" I noticed > that > the "fjes" driver was configured. > I wondered why this network driver was needed for my laptop, so I have done > some > research. > According this [1]

Re: shutdown fails to power off host

Am 18.01.2017 um 08:44 schrieb Joerg Desch: > Am Wed, 04 Jan 2017 22:59:46 -0800 schrieb Bob McGowan: > >> When I shutdown my desktop system, the screen displays messages from >> systemd (I presume), the last of which is "Reached target Shutdown". > > Just a thought... > > I'm running Debian

Re: Systemd: no error but "maintenance mode"

Am 10.01.2017 um 20:08 schrieb Steffen Dettmer: > On Sun, Jan 8, 2017 at 7:45 PM, Joe wrote: >>> What happened before: >>> I had issue with a Debian server SATA bus [1]. I noticed because >>> apt-get upgrade hung, because initramfs updater calls "sync" which >>> hang because

Re: systemd requires "plymouth" on server? (was: Systemd: no error but "maintenance mode")

Am 10.01.2017 um 00:43 schrieb deloptes: > Steffen Dettmer wrote: > >> I'd rather keep it as simple as possible > > you can still use sysvinit as init The shell scripts used by sysvinit are not simpler. More familiar maybe, but not simpler. -- Why is it that all of the instruments seeking

Re: Urgent help needed - Debian boot hangs

Am 06.01.2017 um 20:17 schrieb h...@hanswkraus.com: > I get now the Boot menu, but I don't see the DVD drive. > Any more tips for me? Since it's a bit late I will wait until tomorrow. If you can get into the grub menu, then go to the advanced options menu and select the recovery mode option.

Re: hotpluggable member of a bridge

Am 05.01.2017 um 10:29 schrieb to...@tuxteam.de: > and delegates to specialized subsystems. In a pinch you can just sneak > a complete shell script in an udev rule (and I'm guilty of having done > such a thing [2]), but doing this as "system architecture" might lead to > madness :-) > [2] Once,

Re: Preventing ACL on cdrom drive...

Am 23.12.2016 um 18:54 schrieb Nimrod: > Hi, > > sorry for this trivial question, but I really tried to find an answer on > the web without any result. > > This is the issue: on a computer at home (shared among relatives, each > with his/her own account), the first user that logs in after boot

Re: systemd automount - Parameter TimeoutIdleSec ignored?

Am 11.12.2016 um 18:04 schrieb Andreas Born: > Michael Biebl wrote: >> Am 08.12.2016 um 13:33 schrieb Andreas Born: >>> Hi all, >>> I need a device to be automatically mounted on access and unmounted when >>> being >>> idle. My /etc/fstab entry: >&g

systemd-journald fails to start due to corrupted /etc/machine-id (was: Re: systemd-journald fails)

Am 10.12.2016 um 13:38 schrieb Rainer Dorsch: > root@scw:~# cat /etc/machine-id 26da2c29c6a545fd9af95d29ca9b5a5a 6df > root@scw:~# > > Not sure how the 6df ended in /etc/machine-id, but after removing > that things seem to have settled: > I upgraded from a fresh jessie installation (image from

Re: systemd-journald fails

Am 04.12.2016 um 16:18 schrieb Rainer Dorsch: > The system is hosted at scaleway, i.e. it is not a Debian kernel, which > is running. What kernel is that? Can you check if all requirements as outlined in /usr/share/doc/systemd/README.gz are fulfilled? -- Why is it that all of the instruments

Re: systemd automount - Parameter TimeoutIdleSec ignored?

Am 08.12.2016 um 13:33 schrieb Andreas Born: > Hi all, > I need a device to be automatically mounted on access and unmounted when being > idle. My /etc/fstab entry: > > /dev/sdc1 /mnt/auto ext4 defaults,noauto,x-systemd.automount,\ > x-systemd.idle-timeout=10 0 0 > > Systemd correctly

Re: systemd and initial tmpfs mounts

Am 08.12.2016 um 13:32 schrieb Andreas Born: > Hi all, > > earlier in SysV there was /etc/default/tmpfs to configure the initial mounts > like /run, /run/lock, /dev/shm, /tmp and so on. Now with systemd there is > /lib/systemd/system/tmp.mount as unit file for /tmp, but where are the other >

Re: WiFi after initial install

wiki.archlinux.org/index.php/NetworkManager#Connect_to_network_with_secret_on_boot Am 5. Dezember 2016 16:31:41 MEZ, schrieb Mark Fletcher : >Hello the list! > >I have a Mini-ITX PC, a few months old, running KDE on Stretch. > >When I installed it, I used a Stretch netinst

Re: forcefsck inconsistency

Am 29.11.2016 um 08:40 schrieb Pierre Frenkiel: > For example, how do you explain the presence in syslog of 12 times > the same 12 lines? The lines you posted are not the same. They are for different mount points. -- Why is it that all of the instruments seeking intelligent life in the

Re: forcefsck inconsistency

Am 28.11.2016 um 19:35 schrieb Pierre Frenkiel: > It seems that one must not be too curious, as each time you dig too > deep, you find some kind of mystery. On the contrary, I think this is what makes Linux great. There might be things which are a mystery to you at first, but you are allowed to

Re: forcefsck inconsistency

Am 28.11.2016 um 15:10 schrieb Pierre Frenkiel: > On Mon, 28 Nov 2016, Michael Biebl wrote: > thank you for this usefull information, but some inconsistency remains: > > in /run/initramfs/fsck.log, I find: > > Log of fsck -C -a -V -t ext4 /dev/sda2 > Sat

Re: forcefsck inconsistency

Am 28.11.2016 um 14:11 schrieb Richard Hector: > On 26/11/16 22:03, Pierre Frenkiel wrote: >> According the tune2fs output, the check on / was actually done. >> I naïvely looked at syslog to find the checked devices, and I >> could not imagine >> that the fsck checks are reported

Re: A full /var partition destroyed 3 hours of my life!

[rsyslog maintainer speaking here] Am 15.11.2016 um 06:00 schrieb Borden Rhodes: > One of the culprits in my full /var partition was a 3 gig syslog file > which has only been getting bigger since January despite running > logrotate -f. I try to run it this time but I'm told that it can't I'd be

Re: Ensure service keeps running with systemd

Am 28.10.2016 um 00:50 schrieb Tobias Brink: > Hello! > > tl;dr: When a daemon exits "normally" (for example due to signal 15) >although it should not exit (because I did not call "systemctl >stop"), systemd does not consider it a failure. [..] > How do I tell systemd that it is

Re: Network manager not showing saved network connections

Am 24.10.2016 um 00:26 schrieb Michael Biebl: > Am 23.10.2016 um 23:30 schrieb Paul Seyfert: >> Deleting almost all connections (204 out of 214) in >> /etc/NetworkManager/system-connections/ and only keeping those few I am >> sure to use[2], I get a working state (all con

  1   2   3   4   5   6   >