@Oinks@lemmy.blahaj.zone avatar

Oinks

@Oinks@lemmy.blahaj.zone

she/they

This profile is from a federated server and may be incomplete. Browse more on the original instance.

Oinks,
@Oinks@lemmy.blahaj.zone avatar

『合コンに行ったらイケメン女子がきた』/“I Went to a Mixer and a Handsome Girl Showed Up” by Murakami

Official Pixiv ^JP^ | Official Twitter/X ^JP^ | Mangadex ^EN^ | Dynasty ^EN^

Oinks,
@Oinks@lemmy.blahaj.zone avatar

The GDPR conversation is hilarious. Sure they’re a US based company, but after 5 years of operation I would’ve expected them to have consulted a lawyer about this at some point. Forgetting (assuming it’s not “forgetting”) about the required documentation is not the worst thing in the world morally but it doesn’t exactly make them look competent either.

Oinks, (edited )
@Oinks@lemmy.blahaj.zone avatar

Does your script fork at some point (and might exit before the rsync job is completed)? Because then you need to use Type=forking instead of simple or oneshot, otherwise systemd will start trying to clean up child processes when the script exits.

Edit: Actually considering the time span involved Type=forking will not solve your issue because it will timeout, if this is the problem you need to change your script to not do that.

Oinks,
@Oinks@lemmy.blahaj.zone avatar

TimeoutStopSec applies to the ExecStop command, TimeoutStartSec would be the culprit here. I’m not sure why there would be a default timeout of specifically 1:39 minutes though.

Oinks, (edited )
@Oinks@lemmy.blahaj.zone avatar

Indeed, that all looks fairly innocuous. Just in case, you are sure that you didn’t just accidentially kill or killall rclone or bash?

Perhaps wrapping the script in might help debug where the offending signal is coming from.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • •
  • fightinggames
  • All magazines
    •