Refracta Development, Scripts, etc.
Post a reply
fsmithred

- fsmithred
- Posts: 2101
- Joined: Wed Mar 09, 2011 9:13 pm

## Re: systemd

Tue Feb 18, 2014 9:20 pm

Found the iso I made with systemd. This was the first wheezy build of refracta 7. The release was developed on the third build. (i.e. wiped it all out and started over twice.)

Code:
  `[email protected]
  :~$ cat [slash]etc/issue
  Refracta-7.00-1 (Debian Wheezy 2011-05-12)
  [email protected]
  :~$ uname -r
  2.6.38-2-686
  [email protected]
  :~$ cat /proc/cmdline
  quiet nomodeset init=/bin/systemd initrd=/live/initrd.img boot=live ip=frommedia noxautoconfig nosudo noautologin nouser union=aufs BOOT_IMAGE=/live/vmlinuz
  `

Check to see what ssh is doing, stop it and check again. In a terminal, active (running) and failed show up in green and red, respectively.

Code:
  `[email protected]
  :~$ systemctl status ssh.service
  ssh.service - LSB: OpenBSD Secure Shell server
  Loaded: loaded ([slash]etc/init.d/ssh)
  Active: active (running) since Tue, 18 Feb 2014 16:05:45 -0500; 1s ago
  Process: 1347 ExecStop=[slash]etc/init.d/ssh stop (code=exited, status=0/SUCCESS)
  Process: 1394 ExecStart=[slash]etc/init.d/ssh start (code=exited, status=0/SUCCESS)
  Main PID: 1400 (sshd)
  CGroup: name=systemd:/system/ssh.service
  └ 1400 /usr/sbin/sshd
  [email protected]
  :~$ sudo systemctl stop ssh.service
  [email protected]
  :~$ systemctl status ssh.service
  ssh.service - LSB: OpenBSD Secure Shell server
  Loaded: loaded ([slash]etc/init.d/ssh)
  Active: failed since Tue, 18 Feb 2014 16:09:56 -0500; 4s ago
  Process: 1507 ExecStop=[slash]etc/init.d/ssh stop (code=exited, status=0/SUCCESS)
  Process: 1394 ExecStart=[slash]etc/init.d/ssh start (code=exited, status=0/SUCCESS)
  Main PID: 1400 (code=exited, status=255)
  CGroup: name=systemd:/system/ssh.service
  `

nadir

- nadir
- Posts: 1160
- Joined: Wed Mar 09, 2011 4:18 am
- Location: here

## Re: systemd

Wed Feb 19, 2014 9:01 am

So it is

Code:
  `systemctl`

which is needed (not that sure if ? is needed here, seems obvious the answer will be "yes" ...),
at least for usual tasks (what i do).
That is good info
No shitting, i didn't know, and couldn't figure it out (didn't search that long).
Also thanks for "cat /proc/cmdline". Never heard of it.
golinux

- golinux
- Posts: 663
- Joined: Thu Nov 08, 2012 1:23 am

## Re: systemd

Tue Mar 04, 2014 6:41 pm

There has been an avalanche of discussion about systemd on the Debian email list. Here are a few responses:

> At least for Jessie as far as I understand all other inits are still planned
> to be packaged. So either stick with sysv + insserv or choose another one.
> The decision was just about *the default*.

> I would strongly consider a hybrid of the existing sysVinit and daemontools or
> runit -- runit being a reimplementation of daemontools that
> avoided the licensing issue and has a current maintainer.
> sysVinit would be in charge of system boot, and runit in charge of
> daemon supervision. A few simple modifications allows
> etc/init.d/ files to control the runit processes.
> Another interesting candidate is monit, which is similar in
> basis to runit or daemontools, but spends more effort on trying
> to monitor the results of the processes and send you alerts or
> restart them on misbehavior.

> Personally I'd just stay with sysvinit. I never understood what is so
> bad about it that it so desperately needs to be replaced. People will
> talk about boot times, but the occasional fsck is the real boot time
> killer. A few seconds difference between sysvinit, upstart, systemd,
> etc. doesn't mean much to me, so I'm content to leave things alone.
> Of course, the more systemd becomes accepted, the more likely it may be
> that sysvinit becomes unsupported (either in Debian or upstream). So
> that should be considered when choosing and alternative to systemd.

Something for refracta devs to digest . . .
Post a reply
Jump to:

Powered by phpBB © phpBB Group.

phpBB Mobile / SEO by Artodia.