On 2014-10-09 20:06, 70tas wrote:
>
> Ok, here are some things I do not like about systemd:
>
> 1. Check service:
> systemctl status sshd.service, responds with:
Yes, the response is more verbose. Different.
> 2. tail messages
>
> <<
> 2014-10-09T13:35:19.605295-04:00 dctvtasoss kernel: [690571.934502]
> IPv4: martian source 172.24.87.255 from 172.24.86.188, on dev e0a
> 2014-10-09T13:35:19.605310-04:00 dctvtasoss kernel: [690571.934508] ll
> header: 00000000: ff ff ff ff ff ff 00 0c 29 27 93 fb 08 00
That’s not related to systemd at all.
> My messages file is full of these… ‘martian source’? I would prefer
> Jupiter…
Google the explanation. Or ask in the networking forum. No, search it: it has been asked before.
It is nothing whatsoever to do with systemd, and is in fact decades older.
> 3. Tried to read binary message files… Good luck grepping them;
> haven’t figured that out yet.
And why are you using them? I don’t.
> 4. systemctl list-unit-files
> What are unit files?
well, similar to tree /etc/initd./.
> 5. cat /etc/fstab?
> Where are my mounts? Oh, systemd now handles mounts; I haven’t
> figured out the commands to list them yet.
And previous to systemd, some mounts were handled outside of fstab. Nothing new there.
> system. I wouldn’t have as much of an issue if:
> i. systemd remapped the original UX commands so I could still use
> what I knew
And it does.
> c. Why not keep the old crond and syslog? The binary log files and all
> the additional messages, which I don’t think matter, are painfull
Both are kept. What distribution are you using? Not openSUSE.
> d. Why can’t I continue using my trusty tools, like grep, etc. with
> systemd? Why do I need to use systemctl?
I use grep.
> e. Why isn’t there clear, concise documentation in the man pages for
> such a major change?
There is documentation. A lot of it. Probably more than with systemv. Maybe confusing.
>
> BTW, I like Vixie-Cron and Syslogng, why can’t I keep using them?
I don’t see why not.
cer@Telcontar:~> rpm -qi cron
Name : cron
Version : 4.2
Release : 50.1.2
Architecture: x86_64
Install Date: 2014-02-25T21:40:49 CET
Group : System/Daemons
Size : 181
License : BSD-3-Clause and GPL-2.0 and MIT
Signature : RSA/SHA256, 2013-09-28T02:59:52 CEST, Key ID b88b2fd43dbdc284
Source RPM : cronie-1.4.8-50.1.2.src.rpm
and:
Telcontar:~ # rcsyslog status
Usage: /sbin/rcsyslog {start|stop|status|try-restart|restart|force-reload|reload}
rsyslog.service - System Logging Service
Loaded: loaded (/usr/lib/systemd/system/rsyslog.service; enabled)
Active: active (running) since Sat 2014-10-04 23:40:54 CEST; 4 days ago
Process: 17167 ExecReload=/bin/kill -HUP $MAINPID (code=exited, status=0/SUCCESS)
Process: 20982 ExecStartPre=/usr/sbin/rsyslog-service-prepare (code=exited, status=0/SUCCESS)
Main PID: 20986 (rsyslogd)
CGroup: /system.slice/rsyslog.service
└─20986 /usr/sbin/rsyslogd -n
Telcontar:~ # rccron status
Checking for Cron: running
cron.service - Command Scheduler
Loaded: loaded (/usr/lib/systemd/system/cron.service; enabled)
Active: active (running) since Wed 2014-10-01 22:23:18 CEST; 1 weeks 0 days ago
Main PID: 3971 (cron)
CGroup: /system.slice/cron.service
└─3971 /usr/sbin/cron -n
Telcontar:~ #
You have several choices; here is a (reduced) list syslog-ng is there :
Telcontar:~ # zypper --no-refresh search --name syslog cron
Loading repository data...
Reading installed packages...
S | Name | Summary | Type
--+----------------------------------+----------------------------------------------------------+-----------
i | cron | Auxiliary package | package
| cronic | A cure for Cron's chronic email problem | package
i | cronie | Cron Daemon | package
| cronie-anacron | Utility for running regular jobs | package
| etckeeper-cron | The etckeeper cron function | package
| incron | Inotify Cron System | package
i | kcron | Cron job configuration tool | package
i | perl-Config-Crontab | Read/Write Vixie compatible crontab(5) files | package
i | perl-Unix-Syslog | Perl interface to the UNIX syslog(3) calls | package
i | rsyslog | The enhanced syslogd for Linux and Unix | package
| syslog-ng | The new-generation syslog-daemon | package
i | syslog-service | Syslog service files & scripts | package
| syslogd | The Syslog daemon | package
| vcron | TK-Interface for cron and at | package
Telcontar:~ #
>
> These are just some of my thoughts trying to make sense of systemd.
>
> I think if systemd did the following, it would be much more palatable to
> all:
>
> 1. Use text log files
They are used.
> 2. Use text configurations in /etc, like fstab, etc.
They are used.
> 3. Forget about trying to take over cron and syslog, or emulate them
They are used.
> 4. Either use the traditional command names for systemd commands, or at
> least provide a quick translation from old to new
They are provided.
> 5. Don’t preface all commands with systemctl…
>
> And now, the $64M question: Why have all the distro’s jumped to it?
> Why has SuSE thought fit to make such a drastic change so abruptly?
Because systemv could not be maintained/expanded, and the alternative was there, maintained, and growing.
Without creating a big SUSE team to create an alternative. Expensive.
> I just want the powers that be and make the
> decisions, to hear my pain points as a user and administrator.
They will not. As simple and clear as that.
For two reasons:
- They do not read these forums.
- They are tired of explaining all that, it is pointless to explain all that again, so probably many of them just filter out any post on that issue. The decision has been done, and will not be reverted, no matter how many ramblings.
http://www.youtube.com/watch?v=2io596_7U9o 
(smile)
Only if some group develops a viable alternative, then they may reconsider.
Yes, there are people trying. I read about someone trying on the OBS.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
