MobileRead Forums - View Single Post

KristianR · 03-30-2016, 01:08 PM

Hi there,

I gained telent access to my Kobo Glo HD as described here in several places using a preconfigured KoboRoot.tgz with the following contents:
rcS2

Code:

#!/bin/sh
mkdir -p /dev/pts
mount -t devpts devpts /dev/pts
/bin/busybox inetd

inetd.conf

Code:

# <service_name> <sock_type> <proto> <flags> <user> <server_path> <args>
#ftp	stream	tcp	nowait	root	/usr/sbin/tcpd		in.ftpd
#telnet	stream	tcp	nowait	root	/usr/sbin/telnetd	telnetd -l /bin/login

21 stream tcp nowait root /bin/busybox ftpd -w -S
23 stream tcp nowait root /bin/busybox telnetd -l /bin/login -i

inittab

Code:

# This is run first except when booting in single-user mode.
::sysinit:/etc/init.d/rcS
::respawn:/sbin/getty -L ttymxc0 115200 vt100
::ctrlaltdel:/sbin/reboot
::shutdown:/bin/umount -a -r
::restart:/sbin/init

::sysinit:/etc/init.d/rcS2
::respawn:/bin/busybox inetd

Everything seems to be working fine at first but after a while the Kobo crashes. What I noticed is that if I call

Code:

ps

there are a lot of inetd-processes showing. Repeatedly calling

Code:

free

I can see how free memory decreases while the number of inetd-processes rises.
As a workaround calling

Code:

pkill -f inetd

removes these processes without any obvious negative effect. But I don't like this "solution".

Does anyone else have this phenomenon of increasing number of inetd-processes?
Does anyone have a solution to avoid this problem? Are the above files correct for the Kobo Glo HD or is there something different for the Glo HD?

Kind regards
KristianR

03-30-2016, 01:08 PM	#1
KristianR Member Posts: 17 Karma: 10 Join Date: Feb 2016 Device: none	Too many instances of inetd Hi there, I gained telent access to my Kobo Glo HD as described here in several places using a preconfigured KoboRoot.tgz with the following contents: rcS2 Code: #!/bin/sh mkdir -p /dev/pts mount -t devpts devpts /dev/pts /bin/busybox inetd inetd.conf Code: # <service_name> <sock_type> <proto> <flags> <user> <server_path> <args> #ftp stream tcp nowait root /usr/sbin/tcpd in.ftpd #telnet stream tcp nowait root /usr/sbin/telnetd telnetd -l /bin/login 21 stream tcp nowait root /bin/busybox ftpd -w -S 23 stream tcp nowait root /bin/busybox telnetd -l /bin/login -i inittab Code: # This is run first except when booting in single-user mode. ::sysinit:/etc/init.d/rcS ::respawn:/sbin/getty -L ttymxc0 115200 vt100 ::ctrlaltdel:/sbin/reboot ::shutdown:/bin/umount -a -r ::restart:/sbin/init ::sysinit:/etc/init.d/rcS2 ::respawn:/bin/busybox inetd Everything seems to be working fine at first but after a while the Kobo crashes. What I noticed is that if I call Code: ps there are a lot of inetd-processes showing. Repeatedly calling Code: free I can see how free memory decreases while the number of inetd-processes rises. As a workaround calling Code: pkill -f inetd removes these processes without any obvious negative effect. But I don't like this "solution". Does anyone else have this phenomenon of increasing number of inetd-processes? Does anyone have a solution to avoid this problem? Are the above files correct for the Kobo Glo HD or is there something different for the Glo HD? Kind regards KristianR