Sponsored Content
Full Discussion: "PANIC CPU" ERROR MESSAGE
Operating Systems Solaris "PANIC CPU" ERROR MESSAGE Post 302522320 by feg on Saturday 14th of May 2011 10:56:20 AM
Old 05-14-2011
No i created structure and restored only root, var and usr , i didn't touch /opt . the system panic 15 min after the boot
 

8 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

"syntax error at line 21 :'done' unexpected." error message"

I am trying to run the script bellow but its given me "syntax error at line 20 :'done' unexpected." error message" can someone check to see if the script is ok? and correct me pls. Today is my first day with scripting. Gurus should pls help out #!/bin/ksh # Purpose: Check to see if file... (3 Replies)
Discussion started by: ibroxy
3 Replies

2. Debian

Debian: doubt in "top" %CPU and "sar" output

Hi All, I am running my application on a dual cpu debian linux 3.0 (2.4.19 kernel). For my application: <sar -U ALL> CPU %user %nice %system %idle ... 10:58:04 0 153.10 0.00 38.76 0.00 10:58:04 1 3.88 0.00 4.26 ... (0 Replies)
Discussion started by: jaduks
0 Replies

3. UNIX for Dummies Questions & Answers

suppressing an error message using the "ls" command

hi I'm new here so my question maybe be retarded or out of place: Is there a way to suppress the "No such file or directory" error message when using the "ls" command ? thanks (5 Replies)
Discussion started by: basher400
5 Replies

4. UNIX for Advanced & Expert Users

mailx error message -- "me": not a group

Hi all, When I tried to use mailx like mailx -s "test" someone@somedomain.com < myfile , mailx replies with "me": not a group. Mail did get sent though. So how to deal with this "me": not a group response. I guess it is because some property was not set properly. Because mailx worked well... (0 Replies)
Discussion started by: qiulang
0 Replies

5. Forum Support Area for Unregistered Users & Account Problems

Cannot register due to "spam" error message

Hi all, I am trying to register but it seems my IP address is being seen or black listed as a spam address. I get the following message: "Registration denied. Sorry, The UNIX and Linux Forums runs an active policy of not allowing spammers. Please contact us via by posting in this forum if... (0 Replies)
Discussion started by: codenjanod
0 Replies

6. SCO

"PANIC: k_trap" error

hi I've virtualized physical SCO 5.0.6 on ESX 4 according to: Blog du DS45: HOWTO SCO P2V in the real life SCO starts with the network, but during shutdown I'm getting this message: PANIC: k_trap. My /etc/default/boot: # cat /etc/default/boot #ScoAdminInit BOOTMNT {RO RW NO} RO... (4 Replies)
Discussion started by: ccc
4 Replies

7. UNIX for Dummies Questions & Answers

ls command gives "Not a directory" error message

The operating system is Solaris. There is a perl interpreter that is located at /opt/perl5.10.0/perl. when i give ls -ltr /opt/perl5.10.0/perl I get an error message saying that "/opt/perl5.10.0/perl Not a directory" At the next instant when i give the same command it lists the properties of... (5 Replies)
Discussion started by: sreeharshasn
5 Replies

8. UNIX for Dummies Questions & Answers

Unix "look" Command "File too large" Error Message

I am trying to find lines in a text file larger than 3 Gb that start with a given string. My command looks like this: $ look "string" "/home/patrick/filename.txt" However, this gives me the following message: "look: /home/patrick/filename.txt: File too large" So, I have two... (14 Replies)
Discussion started by: shishong
14 Replies
SYSTEMD-FSTAB-GENERATOR(8)				      systemd-fstab-generator					SYSTEMD-FSTAB-GENERATOR(8)

NAME
systemd-fstab-generator - Unit generator for /etc/fstab SYNOPSIS
/lib/systemd/system-generators/systemd-fstab-generator DESCRIPTION
systemd-fstab-generator is a generator that translates /etc/fstab (see fstab(5) for details) into native systemd units early at boot and when configuration of the system manager is reloaded. This will instantiate mount and swap units as necessary. The passno field is treated like a simple boolean, and the ordering information is discarded. However, if the root file system is checked, it is checked before all the other file systems. See systemd.mount(5) and systemd.swap(5) for more information about special /etc/fstab mount options this generator understands. One special topic is handling of symbolic links. Historical init implementations supported symlinks in /etc/fstab. Because mount units will refuse mounts where the target is a symbolic link, this generator will resolve any symlinks as far as possible when processing /etc/fstab in order to enhance backwards compatibility. If a symlink target does not exist at the time that this generator runs, it is assumed that the symlink target is the final target of the mount. systemd-fstab-generator implements systemd.generator(7). KERNEL COMMAND LINE
systemd-fstab-generator understands the following kernel command line parameters: fstab=, rd.fstab= Takes a boolean argument. Defaults to "yes". If "no", causes the generator to ignore any mounts or swap devices configured in /etc/fstab. rd.fstab= is honored only by the initial RAM disk (initrd) while fstab= is honored by both the main system and the initrd. root= Takes the root filesystem to mount in the initrd. root= is honored by the initrd. rootfstype= Takes the root filesystem type that will be passed to the mount command. rootfstype= is honored by the initrd. rootflags= Takes the root filesystem mount options to use. rootflags= is honored by the initrd. mount.usr= Takes the /usr filesystem to be mounted by the initrd. If mount.usrfstype= or mount.usrflags= is set, then mount.usr= will default to the value set in root=. Otherwise, this parameter defaults to the /usr entry found in /etc/fstab on the root filesystem. mount.usr= is honored by the initrd. mount.usrfstype= Takes the /usr filesystem type that will be passed to the mount command. If mount.usr= or mount.usrflags= is set, then mount.usrfstype= will default to the value set in rootfstype=. Otherwise, this value will be read from the /usr entry in /etc/fstab on the root filesystem. mount.usrfstype= is honored by the initrd. mount.usrflags= Takes the /usr filesystem mount options to use. If mount.usr= or mount.usrfstype= is set, then mount.usrflags= will default to the value set in rootflags=. Otherwise, this value will be read from the /usr entry in /etc/fstab on the root filesystem. mount.usrflags= is honored by the initrd. systemd.volatile= Controls whether the system shall boot up in volatile mode. Takes a boolean argument or the special value state. If false (the default), this generator makes no changes to the mount tree and the system is booted up in normal mode. If true the generator ensures systemd-volatile-root.service(8) is run as part of the initial RAM disk ("initrd"). This service changes the mount table before transitioning to the host system, so that a volatile memory file system ("tmpfs") is used as root directory, with only /usr mounted into it from the configured root file system, in read-only mode. This way the system operates in fully stateless mode, with all configuration and state reset at boot and lost at shutdown, as /etc and /var will be served from the (initially unpopulated) volatile memory file system. If set to state the generator will leave the root directory mount point unaltered, however will mount a "tmpfs" file system to /var. In this mode the normal system configuration (i.e. the contents of "/etc") is in effect (and may be modified during system runtime), however the system state (i.e. the contents of "/var") is reset at boot and lost at shutdown. Note that in none of these modes the root directory, /etc, /var or any other resources stored in the root file system are physically removed. It's thus safe to boot a system that is normally operated in non-volatile mode temporarily into volatile mode, without losing data. Note that enabling this setting will only work correctly on operating systems that can boot up with only /usr mounted, and are able to automatically populate /etc, and also /var in case of "systemd.volatile=yes". SEE ALSO
systemd(1), fstab(5), systemd.mount(5), systemd.swap(5), systemd-cryptsetup-generator(8), kernel-command-line(7) systemd 237 SYSTEMD-FSTAB-GENERATOR(8)
All times are GMT -4. The time now is 01:57 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy