If you put it in systemd, it won't hold up login. I can often ssh into
systems before the whole boot finishes. I don't remember if the login: on
the console was affected.
I did Solaris 10 until about 5 years ago. They replaced SysV init with SMF
which did dependency checking, etc. Crucially, they kept support SysV init
scripts and slowly converted from them to the SMF XML formats. Your 3rd
party init scripts kept working. Since my S99 scripts never broke, I never
had to convert them. It also took Sun until ~ 10.3 to get them working
Systemd doesn't care about backward compatibility so stuff will break.
Worse, some stuff, like rc.local has partial support (that they don't care
about) and it will usually work like the docs say.
I've hit issues with service vs systemctl. Ex: service mysql start vs
systemctl start mysql. Service might *always* exit with status 3
regardless of success/failure. My shell scripts that depended on 0/not 0
had to be changed.
That said, I've found systemd easier than SMF, especially if you abandon
the old ways.
On Tue, Aug 8, 2017 at 12:11 PM, Jerry Feldman <gaf.li...@gmail.com> wrote:
> +1 for me also. When things like this change, we must also change with it.
> On 08/08/2017 12:08 PM, Dan Garthwaite wrote:
> +1 Tom. Not to detract in any way from his answer - he is spot on and
> everyone should learn systemd if they are using systemd.
> If it isn't a daemon and just something that's gotta be done once after a
> power outage I've used CRON's @REBOOT. Especially for non-root users.
> gnhlug-discuss mailing
> Jerry Feldman <gaf.li...@gmail.com> <gaf.li...@gmail.com>
> Boston Linux and Unix http://www.blu.org
> PGP key id:B7F14F2F
> PGP Key fingerprint: D937 A424 4836 E052 2E1B 8DC6 24D7 000F B7F1 4F2F
> gnhlug-discuss mailing list
gnhlug-discuss mailing list