[systemd-devel] How do you set the machine's domain name with systemd?

2013-02-10 Thread Adam Nielsen
Hi all, I have just switched my Arch Linux machine to systemd and it mostly works, but I'm encountering a few issues. For one, all my NFS mounts are failing, and it seems to be because I have granted permission via domain name, and since switching to systemd my machine no longer has a domain

Re: [systemd-devel] How do you set the machine's domain name with systemd?

2013-02-12 Thread Adam Nielsen
Use hostnamectl, assuming your systemd version is new enough: http://www.freedesktop.org/software/systemd/man/hostnamectl.html Thanks for the suggestion, but unfortunately this doesn't seem to work: $ hostnamectl set-hostname korath.my.domain.com $ cat /etc/hostname korathmydomaincom $ pacma

[systemd-devel] Unable to get service to wait for a mount before starting

2024-10-28 Thread Adam Nielsen
Hi all, I'm having some problems getting a systemd unit to start during system boot. Can anyone advise what I'm doing wrong? The service starts fine if I run `systemctl start myservice`, the issue is that it fails to start during boot. The service runs off a network share, so if it starts too e

Re: [systemd-devel] Unable to get service to wait for a mount before starting

2024-10-29 Thread Adam Nielsen
> > I tried using RequiresMountsFor=/mnt/share however again, if it runs too > > early in the boot process the mount is not there and the unit fails to > > start, and is not retried (logs just say "Job myservice.service/start > > failed with result 'dependency'.") > > RequiresMountsFor only works

Re: [systemd-devel] Unable to get service to wait for a mount before starting

2024-11-10 Thread Adam Nielsen
> network-online.target by itself does absolutely nothing. You are > expected to have some service that is ordered > Before=network-online.target and actually waits until network is online. > Standard network management applications that asynchronously configure > interfaces (NetworkManager, sy

Re: [systemd-devel] Unable to get service to wait for a mount before starting

2024-11-10 Thread Adam Nielsen
I'm replying to all three messages in one to avoid spamming the list: On Tue, 29 Oct 2024 21:39:12 +0300 Andrei Borzenkov wrote: > > server:/path /mnt/server/path nfs4 > > x-gvfs-hide,noauto,x-systemd.automount,timeo=15,soft,proto=tcp 0 0 > > /mnt/server/path/subfolder /mnt/share none > > bind

Re: [systemd-devel] DHCPServer SendOption 121 classless static route

2024-11-20 Thread Adam Nielsen
> How would I go about sending the DHCP server option 121 - classless static > route? > > https://datatracker.ietf.org/doc/html/rfc3442 > > The datatypes for SendOption are uint8, uint16, uint32, ipv4address, > ipv6address, and string. > > I tried a few different types and combinations. They eit

[systemd-devel] systemd-networkd-wait-online doesn't wait for DNS

2024-12-08 Thread Adam Nielsen
Hi all, Is there a way to tell the systemd-networkd-wait-online service to wait until DNS is working before continuing? I have an issue where I need an NFS share mounted during boot, but the automount process is failing because the "mount" command can't resolve the hostname of the server during b

Re: [systemd-devel] systemd-networkd-wait-online doesn't wait for DNS

2024-12-08 Thread Adam Nielsen
> > Is there a way to tell the systemd-networkd-wait-online service to wait > > until DNS is working before continuing? > > There is not, so I built a small tool for this: > https://forge.km6g.us/km6g/wait-for-dns > > It doesn't just wait for a DNS resolver to be configured, it waits for a nam

Re: [systemd-devel] systemd-networkd: IPv6 prefix delegation disabled by ipv6forwarding=true

2025-01-13 Thread Adam Nielsen
> The IPv6 is a /48. > > I have the IPv4 all working well. > > But the IPv6 configuration I cannot figure out. I have a similar set up and have this working. > [Network] > Address=2001x:x::x::1 You are specifying a /24 for IPv4, but nothing for IPv6. I'd suggest adding a /64 if you want to de

Re: [systemd-devel] systemd-resolved : How to change permanently to 127.0.0.54

2024-12-23 Thread Adam Nielsen
> My DNS servers are currently manually specified in > /etc/systemd/network/10-ens.network as follows: > > [Match] > Name=en* > [Network] > DHCP=ipv4 > DNS=first-server-ip-goes-here > DNS=second-server-ip-goes-here > DNS=third-server-ip-goes-here > [DHCPv4] > UseDNS=false > UseNTP=false > [IPv6Acc

Re: [systemd-devel] systemd-resolved : How to change permanently to 127.0.0.54

2024-12-23 Thread Adam Nielsen
> Thanks Daniel, that has been my work-around, a systemd timer checking > for 127.0.0.53 and doing a sed on /etc/resolv.conf > > So I came here looking for a more "official" work-around, e.g. some > config file param I missed. > > But it looks like there isn't, so I guess I'll just leave my > wor