Ubuntu – Revert to upstart

systemd is a system and session manager for Linux, compatible with SysV and LSB init scripts. systemd provides aggressive parallelization capabilities, uses socket and D-Bus activation for starting services, offers on-demand starting of daemons, keeps track of processes using Linux cgroups, supports snapshotting and restoring of the system state, maintains mount and automount points and implements an elaborate transactional dependency-based service control logic.

It is a alternate boot manager which manages user session and we suspect the files under /run/systemd/session probably could be session file. You can leave the latest session file and delete the rest.

Since it is only 200MB, you can take a copy of the files to some other directory and you can use the same if something goes wrong

Hope this helps!

The scip upstart job:

This thing really looks like somebody (you?) tried to create a new Upstart configuration file by copying an existing one and then forgot about it half-way through. The following lines in /etc/sysctl.conf, along with the respawn limit unlimited setting in the Upstart job configuration, also make me wonder if somebody has intentionally created this job to avoid having to run sudo sysctl -p manually every time they update the /etc/sysctl.conf file:

# Updates for Gnu Radio
net.core.rmem_max = 1000000
net.core.wmem_max = 1000000
kernel.shmmax = 2147483648

Please check if the file is used by any process using dpkg --search /etc/init/scip.conf. If no matches are returned then you may safely remove the file, otherwise you may have just found the package in your system that is causing us trouble…

The massive upload problem:

I haven't heard of iptraf yet (but it looks cool so I'll take a closer look when there is time), so I'm just going to suggest a tool called iftop to you instead.

To get a clue about which program is uploading the data try this:

1. Install iftop: sudo apt-get install iftop
2. Run iftop with source port display enabled: sudo iftop -P -n -i wlan2
   The switch -P tells iftop to display the port number additionally to the source IP address, the -n switch tells it not to resolve host names and the -i wlan2 switch tells it which network interface it should listen to.
3. Determine the source IP address and port (first column) of some connection that you think might be at fault.
4. Run sudo ss --tcp --udp --all -p src '<ip address>:<port>' to find out which process is responsible for that connection.

If that doesn't help you could try using iftop or iptraf to check if maybe there is a lot of traffic coming from a connected device.