Opened 4 months ago

Last modified 4 days ago

#2308 new enhancement

[arm64] no java wrapper for arm64 available - provide basic systemd unit instead

Reported by: backup Owned by:
Priority: minor Milestone: undecided
Component: installer Version: 0.9.36
Keywords: arm64 wrapper runplain systemd Cc:
Parent Tickets:

Description

Raspberry Pi 3 Model B / 64bit support

On https://wrapper.tanukisoftware.com/doc/english/download.jsp#stable there seems to be no wrapper for arm64 available.
For this platform, and others who have no suitable wrapper we could provide a basic systemd unit, e.g. for starters

# /etc/systemd/system/i2p.service
[Unit]
Description=I2P Service
Requires= local-fs.target network.target time-sync.target network-online.target
After=    local-fs.target network.target time-sync.target network-online.target

[Service]
ExecStart=/home/i2puser/i2p/runplain.sh
#PIDFile=${I2PTEMP}/router.pid"
User=i2puser
Group=i2puser

[Install]
WantedBy=multi-user.target

The user/group and the path to runplain.sh have to be configured by the installer or we tell the user to edit the unit accordingly.

Thanks
backup

Subtickets (add)

Change History (4)

comment:1 Changed 4 months ago by zzz

see also #1840

comment:3 Changed 4 days ago by backup

Archarm / AArch64 has support too:
https://archlinuxarm.org/platforms/armv8/broadcom/raspberry-pi-3

This is a working example, also java is restarted by systemd on failure.
pkill required for the ExecStop?.
Maybe a simple start/stop/status can be included in runplain.sh instead.

# /etc/systemd/system/i2p.service
[Unit]
Description=I2P Service Plain
Requires= local-fs.target network.target time-sync.target network-online.target
After=    local-fs.target network.target time-sync.target network-online.target

[Service]
Type=forking
ExecStart=/home/i2puser/i2p/runplain.sh
ExecStop=pkill -F /tmp/router.pid
PIDFile=/tmp/router.pid
User=i2puser
Group=i2puser
TimeoutStartSec=60
Restart=always
RestartSec=60

[Install]
WantedBy=multi-user.target

comment:4 Changed 4 days ago by zzz

see also #1999

Note: See TracTickets for help on using tickets.