Slackware 14.1 Goes Into Beta, Brings New Packages

[gens]

maybe is true[i haven't tracked every possible usecase scenario], but as far i used it, works as expected. of course for me a batery backed 4+ drives RAID 10/60 is a must and for my apps i normally add to all ext4 fs in fstab commit=1[1 seconds forced sync] that i guess helps to get it closer to 100% and a good backup policy per commit blocks through automated rsync helps in case the shit hit the fan

http://lwn.net/Articles/270891/

in short, as i understand, things not 512b aligned will wait a while to write fully (will wait in disk cache)
this was in 2k8 anyway (maybe was fixed, idk)

this brings up a fun thought
what if the last couple bytes of a hashed file were not written over by the change
i know plain text could still be read, but could a hashed file ?


anyway you got battery backed RAID so wth.
just a tip, check your raid hardware against the red hat bug database
RAID is known to be buggy


on the systemd lists you have been writing;
you still did not say anything that cant be done easy in userspace or hasn't been done in the kernel for a long time already
(and can thus be done in userspace easy thanks to "everything is a file" philosophy)

so relax, have some tee then look at the big picture

[Ramiliez]

1.) you should be using old script compat mode, because networkmanager+systemd allow deferred connections, i have wifi and other types of slow connections and a pure systemd system never wait for network. either waybe more specific
4.) is nice to have integrated tools especially in ARM/mips and helps a bit with the fact that not every distro ship the same cron daemon
5.) well for me in rPI is wicked fast and so far not much bigger than regular syslog files, again smells like rant be more specific
6.) no systemd start all services in parallel and defer some services until its dependecy is up(or kill the whole dep tree) but never stops, be more specific it seems maybe is your installation that is giving you issue but is hard to figure it out without more info

http://pastebin.sabayon.org/pastie/13384 i cant boot to desktop with 3.11 kernel older 3.10 is working.
The issue with journald we already discussed the problem is journald binary storage logrotate doesnt work no backup and random deletion of logs when you restrict log size.
Theres not a big need for fast boot since there are bigger problems which prevent short boot times just look at dmesg

[finalzone]

http://pastebin.sabayon.org/pastie/13384 i cant boot to desktop with 3.11 kernel older 3.10 is working.
The issue with journald we already discussed the problem is journald binary storage logrotate doesnt work no backup and random deletion of logs when you restrict log size.
Theres not a big need for fast boot since there are bigger problems which prevent short boot times just look at dmesg

Could you show your journald.conf and your logrotate.conf? What is the size limit you set? Sometime the issue could be triggered by your own setting.

[Ramiliez]

Could you show your journald.conf and your logrotate.conf? What is the size limit you set? Sometime the issue could be triggered by your own setting.

http://pastebin.ca/2457050

Sorry but those moronic pastebins were cutting my dmesg
im using defaults i cannot afford to lose logs right now

[hoohoo]

i think the base problem is systemd attack a problem that most regular can't perceive because most distros have very dedicated packagers, Desktop Enviroments are really good at hidding the problem and ISV have tackled the issue with very bastardic hacks to make things works in most distros.

...

7.) syslog is a royal pain in the ass to use from C/C++ without a bunch of layers[mostly DE's] since every distro out there find entertaining to modify default socket path/log paths and to put the sweet caramel touch you have like 4 types of syslog servers + stderr that not always points to the distro log path but to the default <-- in the end many devs just make their own log files and dump them somewhere in /var

...

int facility = command_line_options.facility;
openlog("MYPROGRAM", LOG_PID|LOG_NDELAY, facility);
// ...
syslog(LOG_DEBUG, "%s", "Some people think this code is a royal pain in the ass!");
// ..
closelog();

This ^^^ is simple stuff.

The UNIX way, if I may be so pedantic, is to be configurable. If you compare Ubuntu to, say, Suse, well the logs are named differently. That's nothing to do with C++, it's to do with your syslog daemon config file.

You can change the syslog daemon's config if you want.