8 More Discussions You Might Find Interesting
1. Linux
Hello admins and gurus
I have a controversial topic: now we are investing in a new Linux OS that will hold our Sybase database. The server will virtualized on a VMware server hosted on SAN storage. Now the question is, when we install the database engine is it better - in terms of performance -... (1 Reply)
Discussion started by: abohmeed
1 Replies
2. Solaris
Dear all,
Kinda lame question but i'd like to hear your experiences and advice.
Question in short
-----------------
What permission should a mount point "ideally" have - i think it's root.
Ex:- /usr/app/ i'd set the app to be owned by root and within /usr/app i would create another... (1 Reply)
Discussion started by: ossupport55
1 Replies
3. Shell Programming and Scripting
Hey there.
I am a relative rookie when it comes to Linux/Unix Administration and have been learning to adapt my meager coding skill to working with shell scripts in the 'nix realms. I have done some exhausting searches for and found plenty of information on making scripts globally available but... (2 Replies)
Discussion started by: Tenuous
2 Replies
4. Solaris
What can I fix this issue? I have ran below commands but everything is same.:confused:
WARNING: Last shutdown is later than time on time-of-day chip: check date.
The / file system (/dev/rdsk/c1t0d0s0) is being checked
WARNING - unable to repair the / filesystem. Run fsck manually (fsck -F... (4 Replies)
Discussion started by: getrue
4 Replies
5. UNIX for Dummies Questions & Answers
Hi all,
i am trying to incorporate source control management in my project. We have about 50 - 60 shell scripts on 3 different machines dev, stag and production, but there is no source control.
All the files have to be located at specific locations on each machine for it to work
I want to... (4 Replies)
Discussion started by: chvs2000
4 Replies
6. UNIX for Advanced & Expert Users
Has anyone implemented or have suggestions on how to shutdown many remote unix/linux servers from a single script initiated from 1 server?
I need this to execute in parallel as time is not on my side. Our ups is sadly underrated and will die in approximately 15 minutes. (There is not... (10 Replies)
Discussion started by: jsw371
10 Replies
7. Shell Programming and Scripting
I am new to ksh scripts (still reading manuals). I need to write an application that reads a multi-line parameter file, builds sql on-the-fly, runs plsql and saves the output in a specific format for further processing. I am looking for anything on Best Practices for building such an... (1 Reply)
Discussion started by: mtravis
1 Replies
8. UNIX for Dummies Questions & Answers
Hi - I am new to this and was wondering if some of you can help me out. I am just starting to write scripts and need some guidelines on creating scripts. I'm calling them "Best Practices"...what should I do and not do when creating scripts.
All I know so far is that I should avoid putting... (5 Replies)
Discussion started by: toddjameslane
5 Replies
SYSTEMD-FSCK@.SERVICE(8) systemd-fsck@.service SYSTEMD-FSCK@.SERVICE(8)
NAME
systemd-fsck@.service, systemd-fsck-root.service, systemd-fsck - File system checker logic
SYNOPSIS
systemd-fsck@.service
systemd-fsck-root.service
/usr/lib/systemd/systemd-fsck
DESCRIPTION
systemd-fsck@.service is a service responsible for file system checks. It is instantiated for each device that requires a file system
check. systemd-fsck-root.service is responsible for file system checks on the root file system. The root file system check is performed
before the other file systems. Either service is enabled at boot if passno in /etc/fstab for the filesystem is set to a value greater than
zero.
systemd-fsck will forward file system checking progress to the console. If a file system check fails, emergency mode is activated, by
isolating to emergency.target.
KERNEL COMMAND LINE
systemd-fsck understands one kernel command line parameter:
fsck.mode=
One of "auto", "force", "skip". Controls the mode of operation. The default is "auto", and ensures that file system checks are done
when the file system checker deems them necessary. "force" unconditionally results in full file system checks. "skip" skips any file
system checks.
SEE ALSO
systemd(1), fsck(8), systemd-quotacheck.service(8)
systemd 208 SYSTEMD-FSCK@.SERVICE(8)
