Hi The actual ser2net package doesnt have an init script nor has it a good default config file. So i decided to write it on my own and to update that ebuild. What i did: - Added an init script. - Added a conf.d File - Created a new "default" configuration File. - changed the ebuild to install all these files. Files i created: - Added ser2net-2.3-r1.ebuild - Added files/initd-ser2net - Added files/confd-ser2net - Added files/config-ser2net Decisions i made (but which are possibly wrong): - The ser2net utility doesn't create any pid file. And using "start-stop-daemon --make-pidfile" also doesn't work because ser2net forks from it's main process. For this reason i decided to start ser2net "manualy" and to grep out the pid of its process. This works very well here but i couldn't test it on other machines. - The default configuration opens one telnetable port (3001) which is connected to /dev/ttyS0. Other examples (which i thought could be usefull) are also included but commented out. I saw this behavior on a few other Packages and thought this is a good behavior. Btw. this is my first ebuild modification. So even if i read the docs conecerning creating ebuild or init scripts, it could have made some mistakes a pro wouldn't make. So please be fair on your comments!
Created attachment 105521 [details] The new updated ser2net ebuild based on the ser2net-2.3 ebuild
Created attachment 105522 [details] The newly added files/confd-ser2net
Created attachment 105523 [details] The newly added files/config-ser2net (default configuration)
Created attachment 105524 [details] The newly added files/initd-ser2net
Created attachment 106049 [details] Newly updated ser2net ebuild based on ser2net-2.3 ebuild As i saw today, the original ser2net ebuild has been fixed (autotools fix by flameeyes), so i decided to update also my r1 Version. This makes the old ebuild obsolete.
Any chance you will find the time to check my improvements? If not, Could someone other do it? I would really like to see my enhancements upstream.
ser2net-2.5 incl. init-script in CVS now. I didn't used your sample-config though.
